How to Debug a FiveM Script: A Playbook

Read the console like a structured log, not a wall of text

The F8 client console and the server console are two different logs for two different sides of the resource — an error raised on the client will never appear in the server console, and vice versa. The first triage question is always which console printed it, because that alone tells you whether to start reading client-side or server-side code.

Console output is also channel-tagged at the source (messages are commonly prefixed with the origin, like a script or resource name in brackets), which is often the fastest way to identify the true origin of a message even when its text doesn't name the resource directly.

Reading a Lua stack trace

A generic, illustrative example of the shape you'll see: a line naming a file path inside a resource, a line number, and a message such as attempt to index a nil value (global 'Config'). The actionable part is almost always that file-and-line pair closest to the actual message — it pinpoints exactly where execution failed, even when the resource that surfaced the symptom isn't the one actually at fault.

The message itself tells you what kind of mistake it is: "attempt to index a nil value" naming Config generally means something that was supposed to set up that value — often a shared script — either never ran or ran after the file that needed it, which is a start-order question as much as a code question.

Isolating client vs. server, and one resource vs. several

A bug affecting one player but not others points at something client-local; a bug affecting everyone at once points at the server. A bug appearing immediately on join narrows further than one that only appears after a specific interaction. Where the architecture allows it, testing with only server scripts active versus only client scripts active can binary-search which side actually owns the fault. When more than one resource might be involved, this shades into a conflict-diagnosis problem rather than a straightforward debugging one — our guide to diagnosing FiveM script conflicts covers the bisection method for that case in full.

txAdmin as a debugging log, not just a dashboard

txAdmin ships bundled with FXServer — no separate download required — and its Live Console keeps a searchable log history across restarts, alongside a Server Activity log covering connections, disconnections, and custom commands. The practical use for debugging: when a bug is intermittent, search that history for the same error text and check whether it correlates with restarts, specific players, or specific times, instead of relying on memory for whether "it happened last night too."

Common error signatures and what they actually mean

• attempt to call a nil value (global/field 'X') — code tried to call something that doesn't exist yet at that point. Almost always a load-order problem (see our start-order guide) or a typo in an export or global name.
• attempt to index a nil value (X) — code tried to read a property of something that doesn't exist yet. Commonly a config table or framework object read before it was populated.
• bad argument #N to 'function' — a native or function received the wrong type. Check what's actually being passed against what the function expects.
• Couldn't find resource X — server.cfg (or a dependency) names a resource that isn't installed, or is nested or misnamed. See our installation guide.
• You lack the required entitlement — per the official asset escrow documentation, this means an escrowed resource's license check failed on this server. It's an account or purchase issue, not a code bug.
• A resource that starts clean but does nothing in-game — usually a client script that never actually loaded (check that client_scripts in the manifest matches the real files) or an event/keybind being silently intercepted by another resource — see our conflicts guide.