Ok we have no chance to stop steam to autoupdate. For those who play online everytime you guys do an update we need to waith for server to update them as well. Ok no problem for official servers, and for those who play vanilla servers. But for some of the other is a big issue. Sometimes we have to waith 6 or even one day to have our favourite seever updated. This is frustrating. The last week was a hell with several updates and relative bug with connection problems. Now in game like rimworld ( one of my favorite) is heavly modded. Everytime an update is out it broke serveral if not thousond of different mods. This is not a problem at all, becouse you go to game option on steam, and put the previus version on, so job done, No problem, everybody happy. Someting happen on empyrium, and you are on deep water, becouse no betas are on the options, just a very limited and unsless choice of previus versions. So, is possible to have those beta in the option before you apply any update? this should be really apreciate.
While this issue hasn't affected me directly like it has others, I still agree that it's an issue. However, maintaining several versions can be a hassle for the devs as well. I do wonder how much work it is to simply allow two previous versions to be selected other than whatever is current. Personally, I'd allow it such that you have one major and one previous hotfix or patch behind. Each one rolling up as the current moves along. Example: we're currently on 1.8.14 So I'd also have 1.8.13 and 1.8 available. Or similar. If we roll up to 1.8.15, then 1.8.13 goes to 1.8.14. Then 1.8 will roll up to 1.9 by the time we hit 1.9.5 or similar. Or maybe just time based, and still allow a previous version to be selected; one either immediately by number or by about two weeks, and the other by a few months or by milestone patch or half (as described above). Basically, it'll allow servers to not have users locked out instantly upon update, and it'll allow others to stick with previous versions, either which support their custom scenario, or simply to wait while latest patch bugs get worked out. (And let's be real, every single update has come with a whole slew of pretty major bugs.) I know contrarians and apologists don't like to put much thought into things, so for them I must mention that obviously Eleon would provide no support for out of date versions. (Though that would otherwise go without saying.)
I agree with the suggestion, but people still blame the game devs if anything goes wrong when playing an old version. I've seen people complain about issues they are having in alpha 12 and demand that they get fixed. As a user I think every version should be available like it is in Minecraft. But if I were in the shoes of a developer I would have serious concerns over allowing older versions. For example I literally just got a complaint this morning because someone was trying to run an old version of my scenario. The fact that an older version can even be selected or played opens a can of worms that I don't blame developers for wanting to keep closed.
With a few lines of PowerShell code the server admins can keep their empyrion up to date (my choice for the last n years). Or they use the https://empyriononline.com/threads/tool-empyrion-server-auto-update-tools-v2-0-1-0.26031/ tool. So when a update came out the server updates automatical and all player can access the server.
