Skip to main content

What should your Rust server helper cover this weekend?

Before you leave for the weekend, ask your helper to work through the brief you will leave behind. They should be able to join the right Rust world, tell players what they confirmed and find the person who can deal with trouble. Name the hours they have agreed to cover so a volunteer evening does not become an all-weekend promise.

Fill in one weekend brief

Copy this example into the private staff space and replace its details. Use links to the current join post, event instructions and support contact. Ask each named person to confirm their part before you leave.

Fill in one weekend brief
BriefExample to replace
World and coverHarbour Solo. Kai covers Saturday, 18:00 to 21:00 UTC. Sunday has no cover.
Planned activityBuild night on Saturday at 19:00 UTC. Use the pinned event post.
Helper’s jobCheck joins, answer event questions and post confirmed updates in #updates.
Technical contactRowan handles server changes. If unavailable, use the host’s agreed support route and keep the ticket reference here.
When to contact the ownerPlayers cannot join, the world looks reset unexpectedly or a complaint concerns staff.
HandbackPost open reports, support tickets and the next decision here before Monday’s handback.

Try the brief while you can still help

Ask Kai to start from the brief using their own accounts. Have them open the public join post, connect to the named server and confirm they reached the expected world. They should also find the event post and the place for player updates without asking you for a link.

Then give a spoken practice scenario: ‘A player says the server is down.’ Kai should explain how they would try joining, check for an existing staff update or support ticket, and contact the named person. Keep this part an exercise; there is no need to stop the game or file a real ticket.

If Kai cannot open the support page with their own access, put a reachable person in that step. If nobody can make server changes during the gap, say that in the brief and leave technical work for the owner.

Practise one player update

Have Kai draft an update in the private staff space. For example: ‘I couldn’t join Harbour Solo at 20:10 UTC. Rowan is checking it. I’ll post again at 20:30 UTC.’ Name a contact only after they have taken the issue, and choose an update time Kai can keep. An unsuccessful join attempt alone does not tell them why the server is unavailable.

You are ready to leave when Kai can show the join result, find the contact and draft the update from the brief alone. Fix any missing link or access and repeat the affected step.

Move optional work away from the gap

Review planned events and changes together. If Kai can host build night as a player but cannot update plugins, keep build night and move the optional plugin work to a covered window. Tell players when messages outside the covered hours will be picked up.

At handback, Kai leaves the last confirmed result, links to any open report or ticket, and the next decision for the owner. ‘No open reports or tickets; Saturday event finished’ is enough when nothing needs follow-up. Review the remaining items together before closing the weekend thread.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details