Update, many of the mods assume their start directory is inside the directory where the binary-specific executable is running.
For example, in my system, the program directory is 'World_of_Tanks', and the structure contains (not everything show for brevity)
- paths.xml
- python.log
- mods/
- res_mods/
- win32/
- win64/
- WorldOfTanks.exe
....
The Chat Filter mod is located in
- res_mods
- 1.6.1.1
- scripts
- client
- gui
- mods/
- mod_chat_filter.json
- mod_chat_filter.pyc
So, in the mod_chat_filter python code, in order for it to look for it's JSON configuration file, it's looking for paths.xml as
This resolves to:
Implying that the relative path of the current context must be in a sub-directory under World_of_Tanks (such as win32).
However, the Mac wrapper runs the program at the top-level directory named 'WorldOfTanks.exe', so one level about that is inside the 'Games' folder, which does not have a paths.xml file, therefore none of the configuration files that are referenced can be found.
In the mac wrapper, I am able to run the file using an alternative binary, so I tried running World_of_Tanks/win64/WorldOfTanks.exe (one level below), and it appears that most things are now working (except for the few things I modified to see if they would work right, which I'm not rolling back to see if they work right after moving them back to their stock setup).
This fixes 'many' things, but I'm still left with a few that appear to be 32-bit vs. 64-bit issues that can't be solved by changing directories.
Again, it appears that XVM does not (yet) support 64-bit, so this is a non-starter for the MAC which is now 64-bit only.