![]() Be sure to save your AML settings, etc.įind your XCOM 2 settings directory (usually My Documents\My Games\XCom2) and back it up somewhere, then delete it. #XCOM 2 WAR OF THE CHOSEN MODS NEXUS MOD#Also make sure that the mod directories listed in settings are correct, this tripped me up the first time. In the AML's settings, change the Game Dir to point to the XCom2.exe in the War of the Chosen subfolder, not the base XCOM2 folder or the exe in XCOM2\Binaries. Step by step instructions (I'm including them to not be a dick, but be careful if you didn't already know what you needed to do: it's easy to mess things up using the command prompt and the worst case scenario, while not necessarily catastrophic, will likely be annoying): Windows vets probably know where this is going already but the tl dr is "directory junction". WotC uses a different settings directory, but the relevant INI files have the same names and appear to work in the same way. The second problem is trickier: to tell the game what mods to use, the AML writes to certain INI files in the game's settings directory. You can do this in the AML's settings screen. The first one is easy: since the base game EXE and the WotC EXE have the same name, you just need to tell the AML to launch the XCom2.exe in the War of the Chosen\Binaries\Win64 subfolder rather than the one in the default location. This obviously isn't an ideal solution but for those of you lucky enough to be able to play and running unmanageably sized modlists like mine, maybe this will make things easier until the team has the time to update.īasically, there are two problems: the launcher doesn't know where the WotC executable is and it also doesn't know where the WotC config files are. FYI, I was able to get the current version to work with WotC: turns out all it apparently takes is some messing about with the Windows command prompt. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |