Common Errors

/waypointdebug Throws A Nil Value Error#

attempt to call a nil value

Cause: the command calls DebugPrint(...), which is not defined anywhere in the resource, so it errors instead of printing.

Solution: add this near the top of client.lua:

local function DebugPrint(msg) print(msg) end

Nothing Is Drawn On Foot#

Cause: Config.OnlyInVehicles = true.

Solution: set it to false to draw the waypoint while walking too.

The 3D Marker Isn't Visible From Far Away#

Cause: this is a game limitation, not a bug. The game only draws marker shapes from a few hundred metres.

Solution: nothing to fix. The icon is what you see at distance — that is exactly why the marker cannot be the waypoint on its own.

The Route Is Short Or Has No Arrows#

Cause: the destination is beyond the route's maximum distance (4000 m, or 3000 m in light mode), or routeRange is set too low.

Solution: raise routeRange, or accept that very distant destinations only get the icon and marker.

Run /waypointdebug to see how many arrow positions were considered and how many were discarded by each guard. Since every guard can only remove arrows, the highest counter is the culprit.

The Waypoint Disappears When I Get Close#

Cause: hideRadius is set to something other than 0.

Solution: this is intentional behaviour — set it to 0 to never hide the waypoint.

An Export Waypoint Ignores My Icon#

Cause: icon cannot be overridden per waypoint.

Solution: this is expected. There is a single icon texture, taken from the player's active profile. Use color, shape, beam or the route fields to differentiate a scripted waypoint instead.

Player Settings Are Lost#

Cause: the player's state lives locally on their client, not on your server.

Solution: this is by design — profiles are per player, per machine. There is nothing to restore server-side, and no database is involved.

A New Shape Doesn't Render#

Cause: the shape was added on only one side.

Solution: icons, marker shapes and route shapes must be declared in both Lua and JavaScript:

A Style Value Has No Effect#

Cause: the value is outside its valid range, so it was clamped.

Solution: check the range in the styling reference. Out-of-range values never throw an error — they are simply pulled back to the limit.

The Route Takes The Wrong Turn#

Cause: Config.PerformanceMode = true disables the query that asks the game for real driving distances.

Solution: set it to false to use the accurate preset. It is the most expensive query in the resource, but it is what makes the route follow the correct turn at a junction instead of pointing straight at the destination.