
Write a staff conduct agreement your Rust players can use
Publish the standard players can hold staff to. Give the staff team a companion note explaining what to do when their duties conflict with their own play.
Put the promise where players already read the rules
A public entry for Fox Hollow could read ‘Staff play by the same rules as everyone else. We use staff tools only for agreed duties. Report staff conduct through this private route. Another lead will take the case when the usual contact was involved.’ Make the reporting route available to someone who cannot join the game.
Write the matching actions in the staff space
The private wording puts an owner against each promise without posting case evidence or staff-only access details.
| Situation | Staff agreement |
|---|---|
| A moderator sees a report about their usual team. | Pass it to an uninvolved lead and keep the report in the private case space. |
| A staff tool is needed to run a named event. | Write down which action the event permits and whether someone has to log the use. |
| A player complains about a person assigned to receive reports. | Give the player the backup route and tell the backup lead to acknowledge receipt. |
Test the agreement before asking people to sign up
Ask a regular player to find the report destination and explain what staff may do during a casual game. Ask two moderators to read the same event exception and say what they would write down after applying it. If players can understand the promise but staff cannot agree on the action, keep the public line clear and add an example to the staff note.
Get current staff to accept the same standard, including the owner when they play. Put the date and next review beside the agreement so an event exception cannot turn into a permanent staff privilege without anybody noticing.