Skip to content

Conversation

@eduardogarre
Copy link

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).

The default behavior looks for mod folders inside the ArmA3 folder 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.
If the setting is not set inside the 'config.js' file, .modsPath value
will default to the value of .path (the path to your ArmA3 folder).
@eduardogarre
Copy link
Author

I've just found the previous PRs on this, I'll check all of that before coming up with a new PR. Sorry

@Dahlgren
Copy link
Owner

Dahlgren commented Sep 28, 2023

I think the main problem with it is cross platform support for Linux. #156 would solve most such scenarios though. The other option would be to throw an error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants