Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Not expecting the OP to know. This is more of a WTF post. One of many about this new 2K launcher I think.
Shurely the launcher should only be modifying XComModOptions.ini in the user's My Games directory (i.e. copy DefaultModOptions.ini, modify the copy and write it to user directory) and not the supposed-to-be-a-blank-slate DefaultModOptions.ini?
Isn't that why those user-specific configuration files are there in the first place?
I know there is that silly bug with ModLauncherWPF.exe appending and not replacing changed lists of mods to *ModOptions.ini but this error's even more of a mess up than that.
Anyway, top marks to Gearhammer for working this out. Less than that for the people who were involved in this new launcher.
The game has a nasty habit of using the config in your save game directory to overwrite your new config. If you have saved a game, perhaps even started one with no mods active then it's using THAT set of config files for reference and not your new ones. This also is the cause of the mod ghosting issue, where you delete or change mods and they still show up in game.
Documents/My Game/XCom2 War of the Chosen/XcomGame/config/XcomModOptions.ini
This is the offending file most likely. It can be deleted or edited. When you restart the game it will be regenerated using the DefaultModOptions.ini from the WOTC config files. Keep in mind, this is not the config the new launcher is saving.( It is saving that config it in the wrong place.) I hope that is better clarity. I never post. But I LOVE this game.
When you toggle mods on and off in the launcher, it saves that information in that file for reference by both the launcher and the game .exe file. XcomModOptions.ini in your my games directory supercedes it. That is why, when you load a save game, it knows if your missing any mods that were part of the ecosystem when you saved that game. That file will take priority, before the default files. That would also explain why some people had little trouble with the launcher. The error is present, but because they are loading their saved game directory config files they won't notice immediately. Especially, if they haven't changed any mods recently.
Likely, it was a simple error on the part of the programmer of the launcher. Xcom 2's directery structure is a little unique. You would need to know that there are two standalone games wrapped up in there, that draw from their own config files. Perhaps the launcher.ini can be edited to point the WOTC version to the correct path for saving that file with a simple edit or two. I haven't experimented with it yet, as I am limited in my technical skill.
I have not played Xcom WOTC for about a year...
Just loaded it up, a number of my mods are broken
See the following Guide to run workshop mods with updated 2k Launchers:
https://steamcommunity.com/sharedfiles/filedetails/?id=2207129226