Adding a weapon to ox_inventory

#Where the entry goes

Open ox_inventory/data/weapons.lua. It exports three tables — Weapons, Ammo and Components. Yours goes in Weapons, keyed by the uppercase weapon name exactly as it appears in weapons.meta.

return {
    Weapons = {
        ['WEAPON_MYGUN'] = {
            label = 'My Gun',
            weight = 1200,
            durability = 0.03,
            ammoname = 'ammo-9',
        },

        -- ... the weapons that were already here
    },
}

Add your entry inside the existing Weapons table rather than creating a second one. A duplicated table silently replaces the first, which is how people accidentally delete every stock weapon on their server.

#What each field does

• label — the name players see. This is the only field that is purely cosmetic.
• weight — grams. A pistol is around 1200, a rifle 3300, a machine gun 6000. It counts against the player's carry limit, so keep it proportionate to the rest of your list.
• durability — how much condition is lost per shot. 0.03 is a normal firearm; 0.1 suits melee weapons, which lose condition per swing rather than per bullet.
• ammoname — which ammo item feeds it: ammo-9, ammo-rifle, ammo-shotgun, ammo-sniper or ammo-rocket. Omit it entirely for melee and thrown weapons.
• throwable — set true for grenades and similar, and leave durability out.

#The item image

1. Render or export a transparent PNG of the weapon, 512x512 is plenty.
2. Name it exactly like the item key — WEAPON_MYGUN becomes WEAPON_MYGUN.png, the same uppercase naming ox_inventory’s own images use. On a Linux server the case must match.
3. Put it in ox_inventory/web/images/.
4. Restart ox_inventory, then hard-refresh the NUI in game (or restart the client) so the browser cache lets go of the old image list.

A question mark or blank square in the slot almost always means the filename does not match the item name. Wrong capitalisation (it works on Windows, then breaks on a Linux host), a .jpg extension, or a trailing space are the usual culprits — check the actual file on disk rather than trusting your memory of it.

#Checking it worked

Give yourself the weapon with your admin command and look at three things: it appears in the inventory grid, it shows the correct image, and the weight matches what you set. If it appears but weighs nothing, ox_inventory did not read your entry — you have almost certainly edited a copy of weapons.lua rather than the one the resource actually loads.