Quick Start

Quick Start
Minimal production installation for a new server.
Applies to: 
Nord Inventory v2.0.0
1. Install dependencies
Nord Inventory requires 
oxmysql.
ensure oxmysql
ensure nord_inventory
Start the selected framework before 
nord_inventory when the framework itself requires that order. Start resources that register Nord Inventory items after 
nord_inventory.
2. Import SQL
Import:
nord_inventory/sql/nord_inventory.sql
v2.0.0 also uses 
nord_inventory_snapshots, 
nord_inventory_forensics_alerts and 
nord_inventory_placed_items. Auto-SQL creates missing Operations tables with 
CREATE TABLE IF NOT EXISTS, but production servers should still import the supplied schema.
3. Select framework
config/core.lua:
Config.Framework = 'auto'
Supported values: 
auto, 
esx, 
qb, 
qbox, 
nord, 
standalone, 
custom.
4. Configure administrator access
Recommended ACE setup:
add_ace group.dev nord_inventory.dev allow
add_ace group.admin nord_inventory.admin allow
add_ace group.owner nord_inventory.owner allow
The default Admin Studio command is 
/norditems. Operations permissions are mapped through the same role bridge.
5. Choose language
Config.Locale = 'pt' -- pt | en
Config.LocaleFallback = 'en'
6. Review v2.0.0 Operations defaults
Check 
config/operations.lua before production. Important sections:
scan/result limits;
snapshot retention;
persistent placed items;
optional clothing bridge;
item/category movement policies.
All policy fields default to allow when omitted, so upgrading does not silently block old flows.
7. First verification
After startup confirm:
player inventory opens with 
TAB;
/norditems opens for an authorized user;
System Health reports no critical database/provider errors;
Operations opens for an admin;
create one manual snapshot and verify it appears;
run one Anti-Dupe scan and review the result;
give/remove a test item and confirm reconnect/restart persistence;
place a disposable persistent item and confirm it survives a resource restart;
equip/use a long weapon and confirm the back prop updates immediately;
trunk/glovebox sessions close when the vehicle is locked or leaves range.
8. Integrate other resources
Prefer the public exports documented in Developer API & Integrations. Do not rely on private events, NUI callbacks or direct writes to Nord Inventory tables.