Remove Arma directory from mod path on load and rename files after download #40
Conversation
* Add fix for mod paths to be relative to arma directory * lowercase mods files after workshop download
|
It's better to keep a virtual symlinked copy of the workshop item which is lowercased instead of touching the steam workshop files directly. If the original workshop files are changed any steam workshop updates later on will have problems. |
|
A symlinked copy of the workshop items would still require you to lowercase the files and if your adding that folder to Also the current workshop script doesn't even check for updates and redownloads from the workshop on each launch which would break the arma3 launch if there are uppercased files. |
|
Maybe because it doesn't check for updates, it would be better to delete the |
The symlinked version of the mod folder(s) should be kept separate from the originals. lndir is a great tool for making a 1:1 symlinked copy which can be lower cased without impacting the original files. It's fine if the original files are uppercase as long as the loaded symlink file is lowercase.
That depends on how you mount your volumes for persistence |
Mod paths are required to be under the arma3 directory with relative paths given to the executable. Linux is also case sensitive so we need to rename all mods downloaded lowercase or arma3 will fail to load.
See: Issue loading mods using HTML from launcher as I had this same issue.