AWS Custom Weapons

Weapon metadata and name pack based on GGC Custom Weapons. Upstream weapon names remain in the item snippets and metadata. Preserve original credits and license terms when redistributing.

Contents and setup

The manifest loads metadata from metas/ and name helpers from cl_weaponNames.lua. This resource does not automatically register weapon items in your framework inventory. Add matching item and weapon definitions from the examples below, then start this resource before scripts that use the custom weapons.

ensure ox_lib
ensure Rio-customweapons

Keep the folder name Rio-customweapons because dependent resources may use that exact name.

Add items

The complete QBCore item, weapon, and damage snippets are retained below. Copy only the sections that match your framework and inventory; do not paste duplicate keys. Item image filenames must match files installed in the inventory. For ox_inventory, define items and weapon data in its corresponding data files instead of copying QBCore-only fields unchanged.

Restart the inventory/core and this resource, then verify each weapon and component in a private session. If a weapon name does not resolve, compare the item name, metadata weapon name, and registered weapon hash.

Upstream source

The included examples identify GGC Custom Weapons. Review the upstream license before republishing any assets or snippets.

Weapon snippets

The resource README keeps the complete QBCore item, weapon, component and damage examples. Use only entries present in your downloaded files, check your inventory's expected schema, and avoid duplicate item keys.