#Xcom 2 mod launcher wotc mods#

#Xcom 2 mod launcher wotc mods#

Within these orders, mods are loaded alphabetically by their folder name. Order there determines whether workshop mods or local mods are loaded first! The game knows of the mod directories through a config array ModRootDirs in XComEngine.ini, and it turns out that the DLCs happen to be loaded after that, and then itвЂ™s mod directories. It is obvious that base-game config is loaded first. Mod directories ( XCOM 2/XCom2-WarOfTheChosen/XComGame/Mods/*/Config and workshop/content/268500/*/Config).DLC directories ( XCOM 2/XCom2-WarOfTheChosen/XComGame/DLC/*/Config).User directory ( Documents/My Games/XCOM 2 (WotC)/XComGame/Config).Config load order is important, and hereвЂ™s the Processed mod has any chance to textually match an original entry. Since single-value types use the last inserted entry, the config file processed last usually wins.Д«ut at the same time, if a certain approach relies on removing previous array entries, only the first Minor formatting differences such as white-space, indentation, capitalization and leading zeros are relevant for the removal of entries. They look for VarName, VarName, вЂ¦ keys, using the last inserted value, until one isnвЂ™t found. KVPs with different indices produce different keys.ДЄrrays look for the VarName key and insert all entries in order into the array. Static (fixed-size) arrays look for VarName, VarName, вЂ¦ keys and use the respective value inserted last.Primitive types use the value inserted last.How it precisely works depends on the kind of variable. Only after all config files have been loaded, config variables are imbued with the values from the config map. For base-game config files and files in the user directory ( Documents/My Games/XCOM 2 (WotC)/XComGame/Config), Key=Value