Adding a custom weapon to a Qbox server
Qbox uses ox_inventory for items, so a weapon set up for ox works unchanged. The differences that do exist, and exactly where they are.
Qbox came out of QBCore but took ox_inventory with it, which makes weapon setup closer to an ox server than to a classic QBCore one. That trips people up in both directions.

#Items go through ox_inventory
There is no shared/items.lua to edit. The weapon is declared in ox_inventory's data/weapons.lua exactly as it would be on any ox server, and the image goes in web/images named after the item in lowercase.
['WEAPON_YOURITEM'] = {
label = 'Your Weapon',
weight = 1000,
durability = 0.03,
ammoname = 'ammo-9',
},#The resource half is unchanged
Streaming the model, declaring the metadata in the manifest and getting the load order right work the same on Qbox as anywhere else. A weapon pack that works on an ESX server works here; only the item registration differs.
- Drop the resource into resources and ensure it in server.cfg, before ox_inventory
- Paste the weapons.lua entry into ox_inventory
- Copy the PNG into ox_inventory/web/images, lowercase
- Restart ox_inventory as well as the weapon resource
Questions
Do QBCore weapon packs work on Qbox?
Do I need to restart the whole server?
Is the ammo item named the same as on QBCore?
Ready to pick a map?
Twelve themes on three base map styles, $8 each, instant download.
Relevant to what you just read
The tool for this
Twenty theme pairs for ox_lib and ox_inventory From $15, built in the browser, exported as a drop-in resource.