-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lower case characters on mods downloaded from the Workhop #178
Comments
You can use the Ideally mod authors should package their mods with Linux support in mind as things such as native extensions needs to have matching call in sqf code for the |
Thank you @Dahlgren Won't this break the updates? I know, ideally people should have this restriction in mind, but I've found about 1/3 of the mods have upper case characters, so they probably never experienced the issue. |
Anything that makes changes to workshop files outside of steamcmd will cause issues on next invocation of steamcmd as the metadata and actual files will be out of sync. For our (Anrop's) server infrastructure we have a mirror of Steam Workshop which is then mapped to proper lowercase folders and files via |
I don't know exactly how we do it in my team but we have a repository synced with ArmA3Sync that doesn't update automatically with Steam Workshop. Every mod that goes in there is checked and modified if needed so it works properly on the server, and we usually don't rush into updates until we're sure nothing will break. There we don't use your panel (or any panel at all), the missions and mods are uploaded via ssh and just 2 or 3 people have access. Old school... I don't know if it would be possible to implement a solution like yours but within the steam-workshop-mods-status branch. Maybe if the mods were loaded from within a mirror folder, not the original where they're downloaded, it might work. I've tried creating a mirror of the entire steam folder with ciopfs and then changing the "path-to-main-steam-folder" on config.js, but (of course) it didn't work. I guess might be possible to do something alike if I could choose from where are the mods loading into the panel. |
It would be possible with the changes made in the |
I'm sorry but I thing you're like 1000 light-years ahead of me on this. I can manage a server but I lack a lot of knowledge necessary to solve this issue. Let me check if I'm following correctly; the changes made on the virtual-server branch, when/if merged into the workshop-mods-status branch, would allow to modify this branch in order to get the mods from a mirror directory, allowing to keep them synced via workshop API but avoiding the uppercase problem? |
Correct, it allows for each (running) server to make adjustments to things such as keys folder or to lower case addons folder and pbo files without changing the (source) mods |
Nice! But that version hasn't got the Workshop integration, right? Is there any chance the virtual-server gets merged with the workshop-mods-status branch? |
Just a quick update on how I've solved this issue (temporally). Maybe it can be useful to someone else.
Then, i've added this other script here: /home/arma3/Steam/steamapps/workshop/content/107410/majuscules.sh
Every time I run "python3 firstscript.py" arma server and all mods are checked and updated (if needed), all files and folders turned into lowercase and symlinks added to the game directory. It's not as easy as adding the mods via the panel but it gets de job done. |
I'm opening a couple of issues with two separate things I've found. Sorry about the spam!
After downloading a lot of mods from the Workwhop using the steam-workshop-mods-status branch some of them are not usable because they contain upper case characters. This is happening on Linux because of a known limitation in Linux servers (https://community.bistudio.com/wiki/Arma_3:_Dedicated_Server#Case_sensitivity_.26_Mods).
I don't know if it's possible to circumvent that issue with a solution like the one described at the link (using ciopfs). A lot of the mods I'm using contain upper case characters, and if I can't solve this issue I will need to revert to the main branch and keep updating everything manually. Maybe somebody else has found a way of using the steam-workshop-mods-status branch on Linux solving this on the server side. Any help would be really appreciated.
When using the main branch I just uploaded the mods and renamed everything with this script:
Thank you!
The text was updated successfully, but these errors were encountered: