Moderator Commands

Overview

Moderators should use read-heavy commands and escalate owner-only actions.

Command Reference

/whoson

• Command name: /whoson
• What it does: Shows players currently online on a server.
• Parameters: server
• Required permissions: Moderator-approved access
• Example: /whoson server:"US Main"
• Notes: Use in incident reports to verify scope.

/stats player

• Command name: /stats player
• What it does: Displays tracked PvP stats for a player.
• Parameters: optional player name
• Required permissions: Moderator-approved access
• Example: /stats player player:"ExampleGamertag"
• Notes: Include server context in moderation notes.

/player search

• Command name: /player search
• What it does: Finds linked Discord user by gamertag.
• Parameters: gamertag
• Required permissions: Moderator-approved access
• Example: /player search gamertag:"ExampleGamertag"
• Notes: Use before escalating account-link disputes.

/dcfeed list

• Command name: /dcfeed list
• What it does: Shows kill feed channel mappings.
• Parameters: none
• Required permissions: Manage Server if restricted
• Example: /dcfeed list
• Notes: Useful when feeds appear silent.

/dcplayerfeed list

• Command name: /dcplayerfeed list
• What it does: Shows join and leave feed channel mappings.
• Parameters: none
• Required permissions: Manage Server if restricted
• Example: /dcplayerfeed list
• Notes: Verify this before reporting feed outages.

/events

• Command name: /events
• What it does: Shows event feed settings for a server.
• Parameters: server
• Required permissions: Manage Server if delegated
• Example: /events server:"US Main"
• Notes: Escalate event policy changes to admins.

Operational Notes

• Moderators should not run premium or wipe commands.
• Require server name and timestamp in every escalation.
• Keep moderation runbooks aligned with owner policy.