Switching to qs-inventory

This page covers the two ways servers arrive at qs-inventory 4.1: updating from qs-inventory 4.0, where every setting lived in config files, and moving from another inventory — ox_inventory, qb-inventory, the ESX default inventory or tgiann-inventory — with the built-in importer that brings your items, player inventories, stashes and trunks over.

Two inventories cannot run at the same time: both answer the same exports, open on the same key and save the same player column. Remove the old one from server.cfg before qs-inventory starts.

Updating From qs-inventory 4.0#

Version 4.1 moved every setting into the game. Everything 4.0 kept in config/, and where it lives now:

Switching to qs-inventory | Quasar Store

Back up
Export the database, and copy your old qs-inventory folder somewhere outside resources.
Replace the resource
Replace every file. Then put back what you had edited: shared/items.lua, shared/weapons.lua, server/custom/webhook/webhook.lua and any change under client/custom/ or server/custom/.
Do not run the SQL again
The SQL files drop the stash, trunk, glovebox and clothing tables. The new tables 4.1 needs are created by the resource on its own.

Grant access to the panels

bash

add_ace group.admin command.inventoryconfig allow
add_ace group.admin command.inventorycreator allow

Framework admins already have access.

Set your values again
Run refresh and restart, open /inventoryconfig, and copy across what you had changed in the old config: weights and slots, keys, vehicles, weapons, robbery rules. Use the search box (Ctrl+F) to find each one. Settings marked Restart need one more restart of the inventory.
Recreate your own benches and sell points
Only the shipped examples are added automatically. Benches and sell points you had written yourself are placed again in /inventorycreator, standing on the spot and pressing Here.

Inventory	Items	Player inventories	Stashes	Trunks and gloveboxes
`ox_inventory`	`data/items.lua`, pasted or read from its folder, with images	Yes	Shared and personal	Yes
`qb-inventory`	`qb-core/shared/items.lua`, pasted, with images	Not needed: QBCore players already use the same format	Yes, including qb-inventory 2.x	Yes, including qb-inventory 2.x
ESX default	The `items` table	Yes, with the weapon loadout	esx_addoninventory, and weapons from datastores	esx_inventoryhud trunks and gloveboxes
`tgiann-inventory`	`items/items.lua`, pasted, with images	Yes	Shared and personal	Yes

Piece	What happens
New items	Created as creator items: they show up in the Items tab and apply at once, with their image copied into `web/dist/images/` when qs-inventory does not have it yet.
Items qs-inventory already has	Skipped. Nothing in qs-inventory is ever overwritten.
Weapons in the item list	Left out and counted — add them in the Weapons tab. Weapons inside saved inventories are converted when qs-inventory knows the weapon.
`money · black_money · cash`	Not imported: money lives in the framework's accounts.
ox_inventory ammo	Mapped to `pistol_ammo`, `rifle_ammo`, `shotgun_ammo`, `snp_ammo`, `rpg_ammo` and `emp_ammo`; durability becomes quality and the serial is kept.
Stashes, trunks and gloveboxes	Only added where qs-inventory has nothing with that id; existing ones are left alone and counted as conflicts.
Player inventories	The previous value of each player is saved in `qs_inventory_import_backup` before it is rewritten. Items that do not fit in the slots, and unknown items, are counted in the result.

Before	In qs-inventory 4.1
Edit a config file and restart	`/inventoryconfig` — most changes apply the moment they are saved.
Shops, stashes and benches written in Lua	`/inventorycreator` — placed in game, with access by job or gang, a ped or prop and a blip.
Items and add-on weapons added in files	The Items and Weapons tabs of the creator, applied without a restart. The files still work.
Giving items by command	The Give tab, to several players at once. `/giveitem` still works.
One look for everybody	Each player picks a style in the style studio; the server sets the default.
Guessing where duplicated items come from	The Stats tab: every item created, which script gave it, who holds what, and anti-dupe alerts.

Updating From qs-inventory 4.0#

Switching to qs-inventory

Switching to qs-inventory

Updating From qs-inventory 4.0#

Back up

Replace the resource

Do not run the SQL again

Grant access to the panels

Set your values again

Recreate your own benches and sell points

From the very old qs-inventory tables#

Coming From Another Inventory#

Back up the database

Stop the old inventory

Empty the server

Analyse

Paste your item list

Import

What Changes for Your Staff and Players#

Checking It Worked#