Skip to main content

Database & Persistence

Item definition precedence

Nord uses one deterministic rule:

  1. If a row exists in nord_inventory_custom_items for an item name, that DB row owns the definition.
  2. Only when no DB row exists does Nord fall back to shared/items.lua / shared/weapons.lua.

A disabled DB row is still authoritative and blocks file fallback.

Restart behavior

Resource/server startup is read-only for item definitions. It does not seed/replace/delete DB item definitions from the Lua reference registry.

This prevents an Admin Studio edit from disappearing after:

restart nord_inventory

Main storage table

nord_inventory_storage stores inventory content keyed by inv_key, with type, owner, slots, max weight and serialized item data.

Version history

nord_inventory_item_versions stores item definition versions for custom/database changes.

Transaction history

nord_inventory_transactions stores inventory/admin transaction records using unique transaction IDs.

Player preferences

nord_inventory_preferences persists Personal Studio settings.

Vehicle registry

  • nord_inventory_vehicle_categories
  • nord_inventory_vehicle_models

These store category defaults, model overrides, glovebox settings and addon trunk placement data.

Back to top