Closed eduardogarre closed 1 year ago
I've just found the previous PRs on this, I'll check all of that before coming up with a new PR. Sorry
I think the main problem with it is cross platform support for Linux. https://github.com/Dahlgren/arma-server-web-admin/pull/156 would solve most such scenarios though. The other option would be to throw an error.
Currently, the default behavior of the application looks for mod files exclusively inside the Game folder path, by using the value inside config.path. With this commit I add an optional setting inside 'config.js', named .modsPath, which allows you to set a different path to your mods folder.
With the value of .modsPath set to a valid folder, the application will look for your mod files exclusively inside that alternative route.
In order to preserve compatibility with the previous behavior, if the config.modsPath value is empty of undefine inside the 'config.js' file, config.modsPath value will default to the value of config.path (the path to your ArmA3 folder).