/NerdRamble

So for example heavily modding Skyrim back in 2012, users had to use a custom scripting engine (SKSE) to unravel the game for coding hooks, then balance a mod list vs plugin list. Plugins were undesirable on 32-bit engines, since there was a hard limit of 256 possible. If your mod list topped 4GB, the game would stall due to memory limitations.

On XCOM EU:EW, we had to use a wrapper to inject graphical over-rides, and a fan-made launcher to splice any textures into the game. It was... fiddly. Then the Long War team came along and created an installer script which did it for you... and blew everyone's minds. XCOM 2 got greenlit and design influenced due to how sales were being driven by LW mod popularity on Nexus.

Apologies, that's just my tech jargon talking from years of dabbling on the Nexus.

In Steam's case, a mod always contains a plug-in, which the game recognises. It's what a launcher looks for and how publisher EULA's are kept to.

However, a mod can also be files or scripting you have applied manually, such as ENB wrappers & injectors, texture replacements or modified executables. It's only in the last few years that the Workshop 'subscribe & play' has been a mainstream thing.

right, I saw that. I was just giving my personal priorities if any of them turned out to be incompatible with each other.

also, are plugins different than mods? if so where/why would I get them?

Thanks, I will be testing these on a new campaign and merge to the main list if everything goes smoothly.

Once my mod list passed 200+ I had to start keeping a stable and an experimental list like this for my own sanity. Currently I'm on 381 plugins.

oh also uniform manager would be a great addition if it works.

I would love to see jetpacks, hand to hand, and children of the king make it.
strip weapon upgrades also seems really great.
cool stuff. yours is the first modpack i've seen that i'd actually consider using without tweaks.