By design you're not supposed to care about that folder, if the mod system is designed correctly the user shouldn't need to poke at the mod files (hint: XCOM2's isn't). It might also work if you put the mods in the workshop folder but whoever thought it was a good idea to have that folder named '268500' rather than XCom2 should be programming lavatory cleaning drones I have this folder on my steam version of XCom2 and everything inside is working as intended. See above : you can just create the Mods folder and it will work correctly. Having LW2 installed locally would ensure any mod subscribed on steam would be loaded after which is usually required for those to work correctly. However this can actually be useful for a mod like LW2 since as a large scale mod that can be further modified by other mods, it must be loaded before those mod-mods and the stupid steam launcher doesn't allow you to configure the load order of your mods. I guess it's a way to manipulate users into believing steam mods work better than non-steam ones.

You can also join the steam bandwagon but installing mods the proper way have advantages such as preventing auto-updates from messing with your current campaign with absolutely no way to opt out.īe aware thought that XCom2 uses some weird load order forcing every steam mod to be loaded after local mods, and thus possibly overwriting them. Just create the 'Mods' folder as a sub-folder of your XComGame folder (the one from your screenshot) and put your Nexus mod there. Steam will default to a messy system of installing into an obscure folder named with only numbers and will create a mess of other numbers-only folders for each mod. I think you have to create that folder first because it's not created by the steam installer.

Busaguy82 wrote:According to the file description on Nexus Mods, I should have a folder marked 'Mods' somewhere here? Any help will be appreciated.

Download steam workshop mods 2017