Context before punishment
Kicks, bans, and warnings are easier to justify when moderators can review player history, chat lines, sessions, and related activity in one place.
Rust moderation tools help admins review player behavior, investigate reports, check context, and take action without guessing.
Focused context for the admin workflow behind this page, written for server owners who need clarity before they act.
Kicks, bans, and warnings are easier to justify when moderators can review player history, chat lines, sessions, and related activity in one place.
A moderation team needs more than private notes in Discord. Shared logs and consistent player context reduce repeated investigations and help new moderators understand what happened.
Ad-hoc moderation — reacting to reports in Discord, running RCON manually, keeping ban notes in a Google Sheet — works until the server grows. A structured workflow with a shared panel means any moderator can pick up an open report and have all the context they need without asking for a summary.
When each moderator uses different tools and keeps separate notes, moderation decisions become inconsistent. Shared logs and common player profiles keep the team aligned, so players are less likely to receive different outcomes for the same behavior.
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.