A player report system lets your community surface problems to admins without relying on Discord DMs or screenshots, and gives moderators a structured place to review and act on complaints.
Focused context for the admin workflow behind this page, written for server owners who need clarity before they act.
When a report comes in, admins can open the associated player profile immediately. Chat history, session data, PvP context, and prior moderation actions are all available in the same place, reducing investigation time.
A report queue keeps submitted complaints organized and visible to the whole moderation team. This is more reliable than tracking Discord messages and ensures no complaint is accidentally ignored.
With an in-panel report system connected via the Oxide/uMod bridge, players can submit reports directly from inside the game without leaving to a website or Discord. Each report is linked to the submitter's SteamID, the reported player, and a timestamp, giving moderators a structured starting point for the investigation.
A well-structured report workflow looks like this: player submits a report in-game, the report appears in the panel queue with the accused player's recent history pre-loaded, a moderator reviews the evidence and takes action via RCON, and the report is marked resolved with an internal note. RustCommander supports this flow so no report requires manual cross-referencing between tools.
Open RustCommander, add your first server, install the Oxide / uMod bridge, and keep RCON, players, maps, plugins, logs and VIP roles in one place.
Each page is part of the same product surface, so Google and admins can understand the full RustCommander structure.
