
What to tell players when your Rust server goes down
As soon as you can confirm the player-facing problem, post it in the place your players already check. A message saying which Rust world is affected and when you’ll check in again gives players something to act on while you investigate.
Post the symptom you have confirmed
Name the affected world and describe what players see. If they can load into another one, name it explicitly. Give a time for your next message that you can keep even if you have nothing new to report. Anyone working on the server should know who is sending the updates.
Try ‘Harbour Solo is refusing new joins. Evening Builds is reachable. We’re checking Harbour Solo and will post another update here at 20:30 UTC.’ If it is still down then, say so and give the next check-in. Keep follow-ups together so a player who missed the first post can catch up.
Check from the player’s side before posting the all-clear
Ask someone on a normal game client to connect using the join method in your announcement. If they load into the world but can’t move or interact, keep the update open and post that joining has improved while play is still affected.
When the check passes, say which world is playable again and what players should do. For example, ‘Harbour Solo is open again. Rejoin using the usual address in #join-rust.’ Remove any pin that would lead late readers to the old outage message alone.