Game mode: | Online private |
Type of issue: [SELECT ONE] Crash | Bug
Server type: [SELECT ONE] PvP | any
Region: [ Please enter your server region ] EU
Mods?: [ Are mods installed: Yes]
Edition: [ Select one: Steam | tested on Steam, guess all affected. ]
Bug Description:
A clear and concise description of what the bug is.
Upon a new mod version release client installs latest version of the mod, community server only accepts its installed one, leading to service outage if the 2 don’t match.
Installed Mods:
If you answered ‘Yes’ to using mods, please list all your active mods. Otherwise, skip or delete this section.
Any, all mods
Steps to Reproduce:
Please provide a step-by-step process of how the bug can be reproduced. Please be as detailed as possible; the more details, the easier it will be for us to find and fix the bug:
- Step 1 release version 0 of a mod and install it on a server
- Step 2 release version 1
- Step 3 try to connect and it will fail due to version mismatch
Proposed behavior 1: Client preserves version -1 of each mod (if it has that already) and accepts to connect to the server. If version -1 needs to be downloaded, client should ask for permission. If Funcom wants to preserve its bandwidth, version -1 should be downloaded from the community server and checked against the SHA256 string downloaded directly from Funcom or a digital signature.
This proposals would allow for insecure/compromised mod version revocation by simply releasing version +2.
Proposed behavior 2: server updates on the fly as soon as possible and restarts with a admin-selected delay. Default 10 minutes or so.