Skip to main content

Framework Detection

Set the framework mode in config.lua:

Config.Framework = 'auto' -- auto | esx | qb | qbox | nord | standalone

Auto-detection order

When set to auto, Nord checks resources in this order:

  1. qbx_core → Qbox
  2. qb-core → QBCore
  3. es_extended → ESX
  4. nord-core → Nord Core
  5. Nothing matched → standalone

Player identifiers

Nord uses a stable identifier appropriate to the active bridge:

Framework Identifier basis
QBCore citizenid
ESX player identifier
Qbox citizenid
Nord Core citizenid/identifier when available
Standalone fallback FiveM license: identifier, then first identifier

Jobs and restricted storage

Job access checks use the framework job name and numeric grade. Example:

jobs = {
    police = 0,
    sheriff = 2
}

A player must have a listed job and a grade greater than or equal to the configured minimum.

Hunger and thirst

  • QBCore: updates player metadata hunger/thirst.
  • ESX: uses esx_status:add for hunger/thirst.
  • Other modes: emits nord_inventory:server:consume so a custom framework can react.
  • Health/armor effects are applied by Nord on the client after server validation.

Forcing standalone mode

If you use a custom framework and want Nord to avoid detecting a supported framework:

Config.Framework = 'standalone'

You can then integrate your own status/identity systems around Nord's public exports and events.

Back to top