Troubleshooting

Installation problems

Confirm the archive was extracted once, the resource folder contains fxmanifest.lua, and it lives directly inside a configured resources path. Your server.cfg must use the folder name exactly.

ensure ox_lib
ensure oxmysql
ensure no_limit_script

Script won't start

Check for a typo in ensure, a missing fxmanifest.lua, a nested archive folder, or a dependency starting after the resource. Stop and restart the affected resource after correcting the issue, then confirm a successful startup line in the console.

Missing dependencies

Install every dependency named by the product README, use a supported version, and start it first. Do not substitute a fork or legacy package unless the resource documentation explicitly supports it.

SQL errors

Import the included SQL into the active framework database, not a local test database. Confirm the database adapter connection, table prefix expectations, and migration order. Duplicate-table messages may mean the schema already exists; compare the existing table structure before deleting or re-importing anything.

Framework detection issues

Set framework detection to the documented mode when automatic detection cannot distinguish your setup. Ensure only one supported framework bridge is active, and remove stale bridge resources from the startup order.

OxLib issues

Start ox_lib before the dependent resource and install the version required by its release notes. If a UI, callback, or locale error appears, update the dependency and verify its resource name has not been changed.

ESX issues

Make sure es_extended starts before the script and that configured jobs, accounts, and items exist in your current ESX installation. Check whether your ESX version uses imports or legacy shared-object initialization, then use the resource version documented for it.

QBCore issues

Start qb-core before the resource, verify shared definitions match configuration values exactly, and check for duplicate or outdated core resources. Item and job names are case-sensitive where the framework treats them that way.

QBox issues

Use the QBox bridge or configuration mode stated by the product. Avoid combining QBox with obsolete QBCore compatibility resources unless the product specifically supports the combination.

Standalone issues

Standalone mode still requires every listed dependency. Configure identifiers, notifications, inventory hooks, and permissions exactly as the standalone guide requires rather than copying framework-specific values.

Resource conflicts

Disable one overlapping script at a time to isolate duplicate commands, key mappings, UI focus handlers, database table ownership, or event names. Never edit another resource's internal files as a first response; use documented configuration or integration points.

Performance problems

Turn off debug mode, verify the latest compatible release is installed, and profile the server under normal load. Review loops, UI refresh rates, database polling, and overlapping resources before reducing gameplay functionality.

Console errors

Copy the complete first error, including the resource name and line number. Search the configured resource name, confirm the referenced file exists, and compare the installed version against the support requirements before opening a ticket.

Common fixes

• Restart dependencies before restarting the affected resource.
• Restore a clean configuration and reapply changes one at a time.
• Update the framework bridge and resource to mutually supported versions.
• Re-import only documented database migrations after creating a backup.
• Clear a stale server cache only when the product guide or support team recommends it.

Diagnostic checklist

• Product name and installed version
• Server artifact and framework version
• Exact resource and dependency names
• Full first console error and relevant client F8 error
• Steps that reliably reproduce the issue
• Recent update, configuration, or database changes

Debug mode

Enable debug mode only long enough to reproduce the issue, then restart the resource and collect the added log lines. Remove sensitive identifiers, webhooks, tokens, and connection strings before sharing logs.

Config.Debug = true
-- Reproduce the issue, save relevant output, then disable it again.
Config.Debug = false

Logging

Use the server console and resource-provided logs as the source of truth. Include timestamps and the first associated error. Avoid screenshots when text logs can be copied: searchable text helps support identify known failures much faster.

Contact support

Open a request through the official Discord support channel. State what you expected, what happened, what you already tried, and attach sanitized logs. Do not send license keys, Tebex credentials, database passwords, or webhook URLs.