We are making a auto update for our server. I was just wondering what the rules are for updating. All I know is that on forced wipe we wait for all 3 to have updated, but what about when its not forced? if only the client updates or if only the server or umod updates, what is the best practice to avoid many restarts? If only the server recieves a update, can we wait until scheduled restart to update the server? if both client/server updates, will umod have a update guaranteed?

Thanks,
Terror_nisse

Client updates only are unrelated to the server and therefore not related to Oxide either.

If the Rust server updates, you'll have to wait for a compatible Oxide build.

uMod builds do not exist yet, it isn't the same as Oxide.

Thanks for the reply!

I meant oxide. Sometimes when I update my client to fast it can tell me that the server needs to update as well. But as a general rule we always update after oxide updates and ignore what client does? I mean, aren't oxide delayed a little longer than normal sometimes, so people update their client and cant log back in, then until oxide is out?

Oxide updates are sometimes before, sometimes after, sometimes within minutes, sometimes longer; it all depends on the update and if someone was able to prep it before the game update. Clients being able to connect or not also depends on if the protocol changed in Rust.

Ok, so if you were to make a auto update system you would wait for both server/oxide (no order), but ignore client, except if its forced, then wait for all 3?

Oxide always comes after server, so you ignore client, wait for Oxide then update server+Oxide.