> ## 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 Anticheat: Detect Exploits in Your Roblox Game

> Trace monitors player movement and behavior server-side, flagging velocity hacks, teleport exploits, noclip, fling, and fly cheats with evidence replays.

Trace includes a built-in anticheat system that monitors player behavior in real time and flags suspicious activity for your staff to review. Every detection is backed by a recorded replay so your team always has evidence before taking action.

<Warning>
  Trace does not guarantee detection of all exploits. Roblox platform and engine updates may affect detection accuracy over time. Always treat detections as signals for review, not automatic proof of cheating.
</Warning>

## How Detection Works

All detection logic runs **server-side**. Clients have no ability to influence or manipulate detection results - Trace validates movement and behavior from the server's authoritative perspective. When a detection fires:

1. A **detection event** is recorded with the player's identity, the detection reason, and a precise timestamp.
2. A **replay** is captured, giving your staff a 3D recording of the moments surrounding the event.
3. **Staff are notified** in the admin panel and via any configured Discord webhooks.

Detection events appear in the **Detections** section of the admin panel. Each event links directly to its associated replay so reviewers can move from flag to evidence in one click.

## What Trace Detects

Trace monitors for five categories of exploitative behavior:

<CardGroup cols={2}>
  <Card title="Velocity" icon="gauge-high">
    Detects abnormal movement speeds that exceed what legitimate gameplay mechanics can produce.
  </Card>

  <Card title="Teleport" icon="bolt">
    Flags sudden, impossible position changes that indicate a player teleporting themselves without server authorization.
  </Card>

  <Card title="Noclip" icon="expand">
    Identifies movement through solid geometry - walls, floors, or other collidable surfaces.
  </Card>

  <Card title="Fling" icon="arrow-up-right-from-square">
    Detects when a player's character is launched at physics-defying velocities, often used to grief other players.
  </Card>

  <Card title="Fly" icon="plane">
    Flags sustained aerial movement that the game has not granted through an authorized server script.
  </Card>
</CardGroup>

## Protection Presets

Trace ships with three protection presets that control how aggressively the anticheat flags behavior. Configure your preset in **Settings → Protection** inside the admin panel, or by editing `TraceConfig` in `ServerScriptService`.

<CardGroup cols={3}>
  <Card title="Relaxed" icon="shield">
    Higher tolerance thresholds. Reduces false positives in games with complex or fast movement mechanics. Recommended for games with vehicles, parkour, or speed-boosted gameplay.
  </Card>

  <Card title="Balanced" icon="shield-halved">
    The default preset. A middle ground suitable for most Roblox experiences. Provides solid coverage without excessive false positives.
  </Card>

  <Card title="Strict" icon="shield-check">
    Lower thresholds for tighter enforcement. Best for games with predictable, controlled movement where exploiters are more easily distinguished from legitimate players.
  </Card>
</CardGroup>

## Movement Exceptions

Some legitimate game mechanics naturally produce movement that Trace's anticheat could misread as cheating - teleport pads, launch pads, vehicles, scripted flight sequences, and portals are common examples.

<Note>
  Use the **Movement Exceptions API** to mark intentional movement as trusted so it does not trigger detections. Any movement initiated by a trusted server script is excluded from anticheat validation. See the Movement Exceptions API reference for implementation details.
</Note>

Example use cases for movement exceptions:

* **Portals** - instant position changes that look like unauthorized teleports
* **Launch pads** - high-velocity launches that exceed the velocity check threshold
* **Vehicles** - speeds above what a walking player can achieve
* **Scripted flight** - granted flight sequences that would otherwise trigger the fly detection

Registering these mechanics correctly keeps your detection signal clean and meaningful.

## Detection Language

Trace uses calm, neutral language in all detection-related copy. Notifications and records use phrases like **"Detection recorded"** and **"Review required"** - never accusatory statements. This keeps the review process factual and gives your staff room to make the final judgment call.

## Review Flow

<Steps>
  <Step title="Detection fires">
    Trace records the event server-side and notifies staff in the admin panel.
  </Step>

  <Step title="Open Detections">
    Navigate to the **Detections** section of the admin panel to see the flagged event.
  </Step>

  <Step title="Review the Replay">
    Click the replay link attached to the detection to open the 3D evidence viewer with timeline controls.
  </Step>

  <Step title="Take Action">
    If the evidence supports it, issue a warn, kick, or ban directly from the player's profile. If it looks like a false positive, dismiss it and consider adding a movement exception.
  </Step>
</Steps>