ESX Legacy

Drop the resources in

Drop one_inventory/, the fmLib release folder, and screenshot-basic into your resources/ folder.

Move the ESX patch into es_extended

The resource ships with a patch file at:

one_inventory/[INSTALLATION]/es_extended/one_inventory.lua

Copy that one_inventory.lua into your es_extended/ resource folder.

Register it in es_extended

Open es_extended/fxmanifest.lua and add:

server_script 'one_inventory.lua'

Start it from server.cfg

ensure es_extended
ensure fmLib
ensure screenshot-basic
ensure one_inventory

Grant yourself admin access

The admin panel and every admin action/command are gated behind a single ACE: one_inventory.admin. Grant it in server.cfg before booting, to a single identifier (recommended) or to a whole group:

# Full access: opens the admin panel AND can run every admin action/command.
# Grant to owners/devs by identifier (recommended) or to a trusted group.
add_ace identifier.license:abc123... one_inventory.admin allow
# or:  add_ace group.admin one_inventory.admin allow

Without one_inventory.admin the panel cannot be opened (/inventory:manage is permission-checked), so keep it to owners/devs. Per-group command permissions (who can run /giveitem etc.) are managed in-game in the panel's Permissions tab; out of the box the admin group is seeded with all commands. See the Setting Permissions guide for the full breakdown.

Start the server

Database tables are created automatically on first boot.

(Optional) Migrate from another inventory

Migrating from ox_inventory? Remove ensure ox_inventory from server.cfg first: one_inventory now answers as ox_inventory and detects your ox data from the database. Keep the old folder under another name (for example ox_inventory_old) if you also want its definitions imported. Migrating from qb-inventory? Keep it running. Then run /inventory:manage in-game and use the migration wizard to copy items, players, vehicles, and stashes over. See Migrate Inventory.

Remove the old inventory

Stop the server, remove the old inventory resource, then start the server again.