VIPs tied to server operations
VIP access is easier to manage when it lives near player history and server administration. RustCommander keeps that workflow inside the same panel.
RustCommander gives server owners a focused place to manage VIP roles, group mapping, player assignments, expiry dates, and internal notes.
Focused context for the admin workflow behind this page, written for server owners who need clarity before they act.
VIP access is easier to manage when it lives near player history and server administration. RustCommander keeps that workflow inside the same panel.
Admins can record who has access, which group they belong to, when it expires, and any internal notes needed for support or renewals.
In Rust, VIP perks are delivered through permission group membership in Oxide or uMod. RustCommander lets server owners create VIP role categories and map them directly to the corresponding Oxide/uMod groups, so granting access from the panel immediately reflects in the game.
New server owners typically manage VIP sales via Discord DMs and manually run RCON commands to grant group access. RustCommander replaces this with a structured list of VIP holders, expiry dates, per-buyer notes, and one-click RCON grant actions — keeping VIP operations next to the rest of server administration.
Short answers for the search intents behind this workflow.
Most Rust VIP perks are handled through Oxide or uMod permission groups. A player is added to a group, and server plugins use that group to grant perks.
Yes. RustCommander keeps VIP assignments, expiry dates, role mapping, player notes, and group actions in the admin 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.
Each page is part of the same product surface, so Google and admins can understand the full RustCommander structure.