Skip to main content

Troubleshooting Playbook

Use this page for the fastest diagnostic path. The dedicated Error Reference & Diagnostics page lists individual messages/codes.

Inventory does not start

  1. Confirm oxmysql is installed and started first.
  2. Confirm database credentials/connectivity.
  3. Check for the first Lua/SQL error in the console, not only later cascade errors.
  4. Confirm the resource folder is named nord_inventory.
  5. A healthy boot ends with Nord Inventory started successfully.

Admin Studio says access denied

Check:

add_ace group.admin nord_inventory.admin allow

and:

Config.AdminAce = 'nord_inventory.admin'

If using the server-only license fallback, verify server/config.lua and restart the resource after changes.

External item does not use

Verify all four Admin Studio fields:

Handler: External export
Resource name: exact resource folder name
Export name: exact export name
Execution side: Client or Server matching the actual export

Then confirm the target resource is started and the export does not return false.

Invalid inventory request.

This is a generic fallback notification. It does not identify the root cause by itself.

For external-use issues, first check:

  • stale Admin Studio definition;
  • wrong execution side;
  • wrong export/resource name;
  • mixed Nord Inventory files after a partial update;
  • the first related server/client console error.

External export ... rejected the item use.

The external export returned false. Inspect the resource's validation path and only return false when you intentionally want Nord to cancel the use.

Cannot index a funcref

Nord Inventory supports Cfx function references passed across resources. Seeing this error usually means an old/mixed shared/utils.lua or server/core/inventory.lua is still running.

Replace the complete Nord Inventory folder and restart both Nord and the registering resource.

Item comes back after deletion

On current builds, deleting a base item should create a row in:

nord_inventory_disabled_reference_items

If it reappears after restart, verify the table exists and check database errors during the delete/disable action.

Runtime item registration fails

Common reasons:

database_authoritative
reference_disabled
invalid_export

Do not bypass these protections. Decide which resource/system should own the item definition.

Trunk does not open

Check lock state, distance, no-trunk classification, interaction provider and addon placement data. NPC trunk rules may also intentionally block ambient vehicles.

Item has no hand prop

External-use items intentionally skip Nord props. For internal-use items, verify the prop/fallback configuration and worldModel.

Ammo/magazine item has no hand prop

This is intentional. Ammo reload visuals use the equipped weapon flow instead.

Back to top