Player moderation

Build the decision from identity and history, record useful context, then use the least disruptive action that resolves the situation.

Start with the correct player

Open the live player list or player directory and confirm the current identity before acting. Steam profile enrichment, aliases and session context can help distinguish similarly named players, but administrators should still verify the live server relationship.

Review the full context

• Current online state and recent sessions.
• Known aliases and linked external identity details.
• Existing notes and watchlist state.
• Active and previous ban information.
• Recent map or activity context available to your role.

A note should record observable facts, relevant time and the rule or operational reason. Avoid speculation and avoid storing unrelated personal information.

Choose an appropriate action

Use a private message when clarification is enough. Use a kick to end the current session when immediate removal is needed but a persistent block is not justified. Use a ban only under the workspace's moderation policy, with a clear reason and appropriate duration.

Watchlists and notes

A watchlist is a prompt for closer review, not evidence by itself. Pair it with a concise note that explains why the status exists and what a future administrator should verify. Remove outdated watchlist state when the reason no longer applies.

Shared ban lists and team policy

When shared ban-list features are enabled for a workspace, establish ownership and review rules before importing or publishing decisions. External list membership should never replace your own verification and appeal process.

A recommended moderation sequence

1. Identify the correct live player.
2. Review current and historical context.
3. Check the relevant community rule.
4. Choose the minimum effective action.
5. Write a factual reason or note.
6. Confirm the reported operation result.
7. Review or expire temporary state when due.