> ## Documentation Index
> Fetch the complete documentation index at: https://pure.saauf.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Trace Moderation: Warn, Kick, and Ban Roblox Players

> Use Trace to warn, kick, and ban players from your Roblox experience. Bans use the Roblox Ban API and support alternate account restrictions.

Trace gives your staff a structured set of moderation tools to handle disruptive players fairly and consistently. Every action is confirmed before execution, logged in the audit trail, and scoped to your team's role hierarchy - so no one can overstep their authority.

<Warning>
  You cannot moderate players who are at or above your own role level. The moderation hierarchy is enforced server-side - if you try to act on a player with an equal or higher role, the action will be blocked regardless of how you submit it.
</Warning>

## Core Actions

Player profiles in the admin panel present moderation actions in a consistent order: **Ban → Warn → Kick**. All destructive actions require an explicit confirmation step - they never execute on the first click.

### Warn

A formal warning places a record on the player's history without removing them from the game.

* Opens a dedicated, opaque form with a **Reason** field
* The warning is recorded in the player's moderation history
* Visible to any staff member who opens that player's profile later
* Logged in the Audit Logs with the issuing staff member's identity and timestamp

### Kick

Kicking removes the player from the current server session immediately.

* Requires an explicit **confirmation** before the kick is sent
* Logged server-side with reason and issuing staff member
* Does not affect the player's ability to rejoin - use a ban for longer enforcement

### Ban

Banning prevents the player from accessing your experience. Trace uses the Roblox `Players:BanAsync` API under the hood.

<Note>
  `Players.BanningEnabled` must be turned **on** in your Roblox Studio game settings before publishing. If it is not enabled, ban calls will fail silently and players will not be restricted. Enable it under **Game Settings → Security** in Studio.
</Note>

Ban options include:

| Option                     | Details                                                                                                             |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Reason**                 | Required free-text field shown to the player on rejection                                                           |
| **Duration**               | Custom duration in minutes, hours, or days; clamped to values valid for the Roblox Ban API                          |
| **Permanent**              | Toggle for an indefinite ban with no expiry                                                                         |
| **Ban alternate accounts** | Maps directly to the Roblox Ban API's alternate account behavior, restricting linked accounts at the platform level |

### Unban

Lifting a ban uses the Roblox `Players:UnbanAsync` API and removes the restriction immediately. You can unban from the **Moderation / Bans** section or directly from a player's profile if you search for them by username.

## Moderation Hierarchy

Staff members can only manage players who sit at a **lower role level** than themselves. This applies to all three core actions and to assigning or removing roles.

```text theme={null}
Experience Owner  (level 1000)
  └─ Admin         (level 400)
       └─ Manager  (level 300)
            └─ Senior Moderator (level 200)
                 └─ Moderator   (level 100)
                      └─ Reviewer (level 50)
                           └─ Player (level 0)
```

A Moderator (100) can warn or kick a Player (0) but cannot act on a Senior Moderator (200) or anyone at level 100 or above.

All hierarchy validation runs server-side - client-side checks are a convenience, not the enforcement layer.

## Audit Logs

Every moderation action - warn, kick, ban, and unban - is written to the **Logs** section of the admin panel. Each entry records:

* The action type
* The target player
* The issuing staff member
* The reason provided
* The exact timestamp

This gives your team a full, tamper-resistant audit trail for every decision.

## Trace CMD Shortcuts

For speed, use **Trace CMD** (press the quote key **\`**) to issue moderation actions without opening the full panel.

```text theme={null}
ban <username> <reason> <duration>
warn <username> <reason>
kick <username> <reason>
unban <username>
fly <username>
unfly <username>
```

Trace CMD provides **syntax-aware completion** as you type. Shorthand values resolve automatically:

```text theme={null}
ban Saauf Exploiting p
```

Here `p` resolves to `Permanent` before you confirm. Duration shorthands include `p` (Permanent), and numeric values followed by `d` (days), `h` (hours), or `m` (minutes).

## Player-Submitted Help Requests

Players can contact your moderation team in-game by typing `/help` or `!help` in chat. When a report is submitted:

* Staff receive a **notification** in the admin panel
* The notification includes the player's username and their message
* A **Teleport** button lets you jump directly to the reporting player's location on the server
* The report is logged under the **Reports** section for follow-up

This keeps your team responsive to players who need assistance without requiring an external ticketing system.