search

X2CommunityCore / xcom2-launcher

The Alternative Mod Launcher (AML) is a replacement for the default game launchers from XCOM 2 and XCOM Chimera Squad.
GNU General Public License v3.0
347 stars 51 forks source link

AML searches "Config\Config\" for local mod config files #241

Closed Triquetra closed 2 years ago

Triquetra commented 3 years ago

For local mods, the config window seems to look in the wrong folder "Config\Config\" instead of "Config\". My main concern here is that the local mod folder is not being parsed correctly during game launch. 2020-11-24 20_53_10-XCOM Alternative Mod Launcher 1 4 1

RevZero commented 3 years ago

That is kind of weird, but you need to be more specific. What is the path to your local mod folder? Please provide all related information. Name of the mod, path to the mod / folder names etc. Also attach aml.log and settings.json.

Triquetra commented 3 years ago

AML.log

settings.json.txt

I've tried a couple of different paths with the same results. The current path, which is reflected in settings.json, is "C:\Games\Steam\steamapps\common\XCOM 2 War of the Chosen SDK\XComGame\Mods"

The name of the mod is zzzMyConfig. It's just a local mod that I'm using to hold my ini config changes. So, the zzzMyConfig folder is located in in the path previously mentioned.

RevZero commented 3 years ago

Is the XComContent.ini supposed to be in \Config\Config\XComContent.ini or should it be \Config\XComContent.ini? Do you still get the error if you move the file one folder down?

RevZero commented 3 years ago

OK, so I did some tests and I can confirm that this is a bug. It happens, when the mod folder name contains the word Config. When getting the relative ini directories, AML assumes that the first occurrence of Config (starting from the mod folder) is the config folder, which is wrong in this case.

Workaround: Rename the mod folder.