The Trace Lua API is exposed as _G.Trace on the server after the Trace loader initializes. You can use it to authorize intentional player movement so the anticheat system does not flag it as cheating, register persistent movement zones, and add slash commands to Trace Chat. All calls must originate from trusted server scripts - client scripts have no access to this API.
Resolving the API
If your script runs after Trace has already initialized, access the API directly:
If your script may run concurrently with Trace initialization, wait for it to become available:
_G.Trace is only populated after Trace has fully initialized on the server. Scripts that run
immediately at game start should use the wait-loop pattern above to avoid receiving nil.
Security model
All API functions must be called from trusted server scripts only. Client scripts cannot call this API - any attempt by a client to grant itself a movement exception is treated as a violation by the anticheat system, not as a legitimate request.
API surface
The following functions are available on _G.Trace. Click the linked pages for full parameter documentation.
Each method page contains full parameter documentation, return value descriptions, and copy-ready
code examples. Use the sidebar or the links in the table above to navigate to the page you need.