> ## 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.

# Anticheat Protection Presets: Relaxed, Balanced, Strict

> Choose from Relaxed, Balanced, or Strict anticheat thresholds in Trace to match your game's movement style and reduce false positives.

Trace's anticheat engine uses configurable sensitivity thresholds to decide when player behavior should trigger a detection. Because every experience has different movement mechanics, a single set of thresholds won't work for everyone. Protection presets give you a fast, tested starting point - choose the one that fits your game and fine-tune from there.

## The Three Presets

<CardGroup cols={3}>
  <Card title="Relaxed" icon="gauge-simple-low">
    More lenient thresholds across all check types. Best for experiences with fast movement, custom physics, speed boosts, or other mechanics that legitimately push players beyond standard Roblox movement limits. Reduces false positives at the cost of catching fewer genuine cheaters.
  </Card>

  <Card title="Balanced" icon="gauge" color="#1f6feb">
    **Recommended default.** Standard thresholds tuned for the majority of Roblox experiences. Provides a solid baseline that catches common exploits without generating excessive false positives in normal gameplay.
  </Card>

  <Card title="Strict" icon="gauge-simple-high">
    The tightest thresholds available. Best for experiences where all movement is predictable and tightly controlled - such as turn-based games, simulators, or experiences where players should never deviate from scripted paths. Maximum detection sensitivity.
  </Card>
</CardGroup>

<Tip>
  Start with **Balanced** and publish. After your team has played a few sessions, review any false-positive reports in the Detections log. If legitimate players are being flagged, switch to Relaxed. If your experience has highly controlled movement and you want more coverage, try Strict. Iterating from real data is more reliable than guessing upfront.
</Tip>

## Check Type Breakdown

The following table summarizes how each preset affects sensitivity for Trace's five core movement check types. **Higher sensitivity** means the check triggers at lower deviations from expected behavior; **lower sensitivity** means greater tolerance before a detection fires.

<Accordion title="View preset sensitivity by check type">
  | Check Type   | Relaxed                                                                                               | Balanced                                                                                          | Strict                                                                      |
  | ------------ | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
  | **Velocity** | Low sensitivity - tolerates high speeds common in racing or combat experiences                        | Medium sensitivity - flags speeds meaningfully above standard Humanoid WalkSpeed/JumpPower limits | High sensitivity - flags any speed above tightly controlled expected values |
  | **Teleport** | Low sensitivity - large position deltas allowed; suitable for experiences with built-in teleportation | Medium sensitivity - flags sudden large position changes not explained by network lag             | High sensitivity - flags even moderate unexplained position jumps           |
  | **Noclip**   | Low sensitivity - some geometry intersection tolerated                                                | Medium sensitivity - flags repeated geometry penetration patterns                                 | High sensitivity - flags any significant geometry intersection              |
  | **Fling**    | Low sensitivity - extreme velocity spikes must be sustained to trigger                                | Medium sensitivity - sustained abnormal force vectors trigger detection                           | High sensitivity - any anomalous force application triggers detection       |
  | **Fly**      | Low sensitivity - sustained airborne states must be prolonged to flag                                 | Medium sensitivity - flags players remaining airborne beyond expected jump arc durations          | High sensitivity - flags brief unexplained sustained airborne states        |
</Accordion>

## Changing Your Preset

You can change the active preset in two places:

* **`TraceConfig` in `ServerScriptService`** - set the preset before publishing so it takes effect on the next server start.
* **Settings → Protection** inside the admin panel - change it at any time while your experience is live.

<Note>
  Preset changes take effect on the **next server start**. Existing live servers continue running on the preset that was active when they started. To apply a new preset to all servers immediately, you will need to restart or migrate them through the Server Management panel.
</Note>

## Handling Persistent False Positives

If a specific game mechanic in your experience - such as a scripted dash, launch pad, or vehicle system - consistently triggers detections regardless of which preset you use, you can register it as an exception using the **Movement Exceptions API**. This tells Trace to suppress detections for defined player states or velocity windows without loosening thresholds globally.

See the [API Reference](/api/overview) for details on registering movement exceptions.