Troubleshooting

Most ARS script issues come down to a handful of causes. Work through this page before anything else — it fixes the majority of setup problems we see.

First: read the consoles

• The server console (or txAdmin live console) shows resource start failures, escrow errors, and server-side Lua errors.
• The F8 console in game shows client-side Lua errors.

Always scroll up to the first red error — later errors are usually consequences of the first one.

The resource does not start at all

• Make sure the resource folder name matches the name you ensure in server.cfg.
• Check that the resource appears in server.cfg after its dependencies:

ensure ox_lib
ensure ars_hud

• Look for a red error in the server console while the resource loads — the error tells you which file failed and why.

“No such export” or nil-value errors

This almost always means one of three things:

1. Start order — the resource calling the export starts before the resource providing it. Fix the ensure order so dependencies come first.
2. The providing resource failed to start — scroll the server console for its error and fix that first.
3. Name or casing mismatch — resource names are case-sensitive. ars_ambulance and ARS_Ambulance are not the same name.

Missing SQL tables or columns

If the server console shows database errors such as “Unknown column” or “Table … doesn’t exist”, the SQL file shipped with the script has not been imported. Import it into your server database before the first start, following the steps in the script’s Installation page.

Framework not detected

Many ARS scripts auto-detect your framework. If auto-detection fails or picks the wrong one, set the framework explicitly in the script’s config. For example, ARS Hud V3:

Config.Framework = 'qb'   -- QBCore
Config.Framework = 'qbx'  -- QBX (Qbox)
Config.Framework = 'esx'  -- ESX

See your script’s Configuration page in its docs section for the exact setting.

ox_lib issues

Most ARS scripts require ox_lib for locales, callbacks, and keybinds. If you see errors about a missing ox_lib export or lib function:

• Ensure ox_lib is in server.cfg and starts before every ARS resource.
• Update to a current ox_lib release — old versions can be missing newer functions.

Escrow or entitlement errors

These are purchase and key binding problems, not script bugs. See Purchases & Escrow for the checklist.

Still stuck?

Gather the console output and see Support for how to reach us.