// 01
More than online players
Live player lists are useful, but moderation often depends on history. RustCommander keeps player records available after they leave the server.
Player intelligence
Rust player history that gives moderators real context.
RustCommander stores player records and activity context so admins can review who joined, what happened, and which actions make sense.
Rust player history
How RustCommander helps.
Focused context for the admin workflow behind this page, written for server owners who need clarity before they act.
// 02
Context before action
Player details combine identity, chat, combat, team, and related logs so moderators can make decisions with fewer blind spots.
// 03
SteamID lookup and player identity checks
RustCommander lets moderators search any SteamID and pull up every connection, session, chat line, and related action tied to that account. This is especially useful when a player returns under a different name or when an appeal requires historical verification.
// 04
Using player history to investigate reports
When a report comes in, moderators can open the accused player's profile and review recent activity without asking for screenshots or digging through Discord logs. The same panel that received the report has the player data needed to act on it.
FAQ
Questions admins ask first.
Short answers for the search intents behind this workflow.
What is Rust player history?
Rust player history is the record of a player across server sessions: SteamID, names, joins, leaves, chat, teams, combat context, reports, and moderation actions.
Why do moderators need player history?
Player history helps moderators check patterns before acting. Instead of judging only the current moment, they can review prior chat, sessions, reports, and actions tied to the same SteamID.
Run this workflow from the panel.
Open RustCommander, add your first server, install the Oxide / uMod bridge, and keep RCON, players, maps, plugins, logs and VIP roles in one place.
More workflows
Explore more RustCommander tools.
Each page is part of the same product surface, so Google and admins can understand the full RustCommander structure.