Skip to main content
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.
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.

​
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:

Velocity

Detects abnormal movement speeds that exceed what legitimate gameplay mechanics can produce.

Teleport

Flags sudden, impossible position changes that indicate a player teleporting themselves without server authorization.

Noclip

Identifies movement through solid geometry - walls, floors, or other collidable surfaces.

Fling

Detects when a player’s character is launched at physics-defying velocities, often used to grief other players.

Fly

Flags sustained aerial movement that the game has not granted through an authorized server script.

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

Relaxed

Higher tolerance thresholds. Reduces false positives in games with complex or fast movement mechanics. Recommended for games with vehicles, parkour, or speed-boosted gameplay.

Balanced

The default preset. A middle ground suitable for most Roblox experiences. Provides solid coverage without excessive false positives.

Strict

Lower thresholds for tighter enforcement. Best for games with predictable, controlled movement where exploiters are more easily distinguished from legitimate players.

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

1

Detection fires

Trace records the event server-side and notifies staff in the admin panel.
2

Open Detections

Navigate to the Detections section of the admin panel to see the flagged event.
3

Review the Replay

Click the replay link attached to the detection to open the 3D evidence viewer with timeline controls.
4

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.