Banning and kicking players in Rust should be an informed decision. A proper admin panel gives moderators player history, chat context, and a logged record of every action before and after the ban.
Focused context for the admin workflow behind this page, written for server owners who need clarity before they act.
A ban in Rust should come with context: who the player is, their prior sessions, chat history, and whether similar incidents were handled before. RustCommander keeps that context next to the RCON commands that issue the ban.
Tracking which players were banned, when, and by whom protects the server against appeals and future incidents. A persistent ban log is more reliable than Discord history and easier to search when patterns emerge across players.
Kicks are temporary and typically used for first offenses, lag issues, or warnings. Bans are permanent (or timed) and reserved for cheating, harassment, or repeated rule violations. Having player history in the same panel where bans are issued means moderators can make that judgment based on a record, not an impression from the current session.
Ban appeals often require proof of what happened and who made the decision. RustCommander keeps a searchable ban log with the acting moderator, reason, and timestamp attached to each entry. When a player disputes a ban, the relevant history is already organized and ready to review.
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.
