# How to review a ban appeal for your Rust server

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md)

Publish a private appeal route that works for someone who cannot join the game. Use it for bans your own staff issued. Confirm who imposed the restriction before deciding who can review it.

## Give the reviewer the original decision

Ask the player to share the server, their Steam ID and the appeal reason through that private route. Let another moderator review the appeal when someone else is available. On a solo server, reopen the evidence and read the player’s account before rechecking your first decision.

1. Find the restriction and confirm the account, affected server and recorded reason.
2. Read the rule that applied at the time and the evidence used to make the decision.
3. Compare the appeal with the evidence and record whether the restriction stays, changes or is removed.
4. Send the player the outcome privately and check that the restriction matches your decision.

## Line up the evidence before comparing stories

Suppose a player appealing a ban on Bracken says they were disconnected before a raid. The original case lists 20:16, but the clip has no time zone. A separate staff note identifies a name seen on screen. Ask for the full clip or an original timestamp with its time zone, and check whether records can tie the name to the account in the appeal.

| Information | What it establishes |
| --- | --- |
| The clip shows a breach at the east gate. | The incident happened. Relating it to a particular account needs additional evidence. |
| The report calls the timestamp local, and the original reviewer confirms the time zone. | Convert to the same reference as the join records before deciding which connection overlaps. |
| After conversion the account in the appeal left before the breach, and the staff note only has a display name. | The evidence does not support keeping this particular local ban. Record why the timing and identity evidence changed the result. |

## Give the player a reason they can understand

For example, “We removed the ban. The recording confirmed the raid but did not identify your account as one of the raiders. You can try joining again.” If you keep a temporary ban, tell the player which rule applied and when the ban ends, using a time zone.

Keep the reply about the decision and the player’s own account. Keep other reporters’ details in the private case notes.

## Check the decision on the affected world

If the appeal is upheld, apply the agreed reversal in the tool that actually enforces the ban. Ask the player to try the affected server and report the exact message if it still rejects them. A separate host or platform restriction can have a different owner. Keep the appeal open until you can explain the remaining result.

If you keep the ban, record its duration, scope and plain reason. Check a temporary decision uses the intended end time and that the player's reply says which world or worlds it covers.

## Sources

- [Facepunch: reporting in Rust](https://support.facepunchstudios.com/hc/en-us/articles/10640775389853-Reporting-in-Rust)
- [Discord guidance on private moderation appeals](https://discord.com/safety/transparency-in-moderation)

## Related resources

- [How to correct a moderation mistake on your Rust server](https://rustsc.com/learn/community/correct-a-rust-moderation-mistake/index.html.md)
- [Kick, ban or unban a player](https://rustsc.com/support/guides/manage-players/index.html.md)
- [Help a player in game](https://rustsc.com/support/guides/player-actions/index.html.md)

---

HTML version: https://rustsc.com/learn/community/run-a-rust-community-ban-appeal/
