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
ACE3 - RHS compatibility mods falsely displayed as optional mods #7753
Comments
fixed by #7859 |
nothing was actively done to fix this the optionals are signed (have a |
Well, strange, I checked again and the bug disappear My bad :) |
The problem still exists. I think it will be fixed if you sign the compatibility mod with an own key (each of them). |
Why does this matter? Who cares about the Arma Launcher? |
People who don't know much about ArmA 3 mods use the launcher to join the server. |
The issuse is when you try to run a public server. Random players cant join it because they use the arma launcher and dont know better. |
In case anyone encounters this bug, this issue still persists. |
Solved by #9294 |
1.98.146373 [stable] (current / newest version)
3.15.1 [stable] (current / newest version)
3.13.2 [stable] (current / newest version)
Description:
If only the ACE 3 mod is running on the server and you subscribed the RHS mods and the 'ACE 3 - RHS compatibility mods' (for RHS:USAF, for RHS:AFRF & for RHS:GREF), the compatibility mods are displayed as optional mods falsely.
Steps to reproduce:
Expected behavior:
The compatibily mods should not be displayed on the 'optional mods' list because RHS is not installed on the server
Where did the issue occur?
The problem occures in the ArmA 3 launcher where the required & optional mods are displayed when you want to join a server
Possible fix
Sign the three compatibility mods (add bikeys)
The text was updated successfully, but these errors were encountered: