Hi
Right now Rust is faced with a potential problem whenever there is a new patch out. Steam automatically updates the client, while the server needs manual interaction from its admin in order to do so. This results in an overlap between client updates and whenever a server admin gets around to logging onto the server, shutting it down and running the update.
My suggestion is crude and proboably requires refinement, but goes something like this:
Server polls update system periodically to check wether a new version is out, if it is then a timer begins in order to shut down the system and initiate the update. This can be preceded with messages if there are any logged in players, notifying of the update and that they proboably need to update the client (as I believe client updates are postponed if game is running).
How this can be achieved on the server is not something I have knowledge of, but may for example be a wrapper around the server software itself that launches the server. That way the wrapper can handle the polling for updates as well as stopping and restarting server after updating.
I am aware that updates can cause issues for mods. However, in my opinion that is less of an issue than players actually not being able to connect and play. Admins have to sort out the mods anyway during a manual upgrade job, so this should not be a massive difference in that regard while server availability would be improved.
I'm sure more players out there have viewpoints and feedback on this, so let it rip guys!
There are a couple instances that exist that describe what you're talking about. One such example I could locate was an Oxide plugin that checks for devblog updates, which will initiate a check for server updates. If an update is found the server will warn the users before restarting.
Link here
Ok, I didn't know about that mod. However, since I'm not currently running a server, another mod to fix an inherent game maintenance challenge is only going to help in those instances where the server admin has made an effort to locate and apply that mod.
My post was made from a player perspective, where it is immensely frustrating when I have a day off and am planning to relax and rust about, but I cannot since most servers apparently do not use this mod and are left in a state where my client refuses to connect to it. Thus I argue that an official built-in solution for the upgrade situation is still a valid suggestion
An option could be that the client can connect to earlier server versions where there aren't any breaking changes between the two perhaps? Assuming that not all updates cause incompatibilities between server/client, which would alleviate at least part of the occurrences
It wont work as the warning would have to come from the server side and as the clients are automatically updated when they load the game they will be unable to join the server till it updates and so wont be able to get any warning, its up to the server owner to decide whether or no they will advise players they are shutting down for game updates (if there are any on) when the server owner is aware of updates,
All servers will shut down for major updates anyway as they have to to install Steam/Oxide updates, most plugins can be installed when server is running (but that only effects modded servers)
Sorry, you need to Log In to post a reply to this thread.
