Staff Support Commands

Start by confirming the Discord member, linked gamertag, and Rust server. Check what happened before giving a replacement reward or changing access.

Manage Server gives access to staff player commands. A configured moderator role can also have access to selected command groups; a moderator role does not automatically unlock every admin command. See Moderator Roles.

Start with a check

What you need	Command or guide
Find a player's linked account	/player info user:@Player — Player Info
Review balance changes	/player logs user:@Player — Player Tools
Inspect stored rewards	/player inventory user:@Player — Player Bag Support
See online players on one Rust server	/whoson server:"US Main" — Online Players
Check recorded stats and hours	Player Stats
Review killfeed destinations	/dcfeed list — Killfeed and Alerts
Review event announcements	/events server:"US Main" — Event Feed Settings

Players can use commands such as /whoson and stats viewing too; they are not staff-only diagnostics. Staff /player commands still need staff access.

The /events panel contains buttons that save changes immediately. Opening a settings panel is not permission to click its toggles during an investigation.

For a private dashboard workflow, use Manage Server → Player Tools. Player Tools requires Premium. Discord's player info, logs, inventory, and stats-restoration commands are available without Premium.

Missing reward

1. Check the original reward or purchase response.
2. Inspect the full bag, including later pages and server labels.
3. Check whether the reward was already used, sold, gifted, or opened.
4. Verify the linked player and online requirements for delivery.
5. Only issue a replacement after confirming one is needed.

A live kit grant is not a stored bag entry. Do not use the bag's removal control as a refund; it permanently deletes a complete stored entry.

Use Giving Rewards, Taking Currency and XP, and Set Player Balances for their different effects. Adding money, taking money, and replacing a balance with an exact total are not interchangeable.

Changed gamertag

Check the player's current link first. Relinking attempts to carry saved stats forward using prior-link history.

If saved history remains under the old name, follow Restoring Player Stats. The restore moves history across this community's Rust servers and applies on command submission. It is not a way to recover wiped stats or another person's account.

Temporary restriction or early unban

Follow Temporary Bans and Early Unbans.

• /tempban requires Premium on the selected Rust server and permission for that command.
• /player unban uses permission for /player and removes one selected active restriction.
• A Game restriction, ORP restriction, and TP Home restriction are different choices.
• A queued game-ban request is not proof that the ban reached the game.

Choose the matching active ban from autocomplete when lifting it early, especially if the player has more than one restriction.

Keep support details private

Staff command replies can be visible in the Discord channel. Use an appropriate staff channel for account histories, bag details, ban reasons, and identity corrections.

Do not publish account IDs, private RaidLink codes, payment details, or unrelated player messages in a screenshot. Hiding a ban reason from the game announcement does not hide it from staff's Discord response.

When to escalate

Ask your owner or Helios support before proceeding when:

• The old gamertag is linked to someone else or account ownership is unclear.
• A stats restore reports a safety timeout.
• A payment, Premium renewal, or storefront order needs billing review.
• A proposed fix would wipe records, remove a server, transfer ownership, or affect many players.
• You cannot tell whether a previous action succeeded.

Record the server name, time, exact response, and the checks already completed. Do not repeat a destructive action to find out whether it worked.