AWS DEVELOPMENT / DOCUMENTATION

Your server. Our expertise.

Everything you need to install, configure and build.

Installation notes

Use the exact folder, SQL file, dependency and startup order shown for your downloaded package. Some resources contain FXAP-protected runtime files, so their guides cover only the source and configuration that can be inspected.

AWS Weapons On Back

Displays supported carried weapons on the player model and synchronizes their state. Weapon positions and inventory/framework adapters are configurable.

Requirements

The manifest directly requires ox_lib, ox_inventory, and Rio-customweapons. Start those before exit-weapons-on-back. The framework default is QBCore. Adapter files also include ESX and several inventory bridges, but the manifest still declares ox_inventory as a dependency.

ensure ox_lib
ensure ox_inventory
ensure Rio-customweapons
ensure exit-weapons-on-back

Keep the folder name exit-weapons-on-back; dependencies and events use that identifier.

Configure

Edit configs/config.lua:

config.framework: qb, esx, or standalone
config.useDefaultInventory: automatic inventory selection
config.policeJobs: law-enforcement job names
config.positions: bone, offset, and rotation for weapon slots and ped models
config.tuner: enables the in-game position tool; keep it disabled in production

configs/core_inv_config.lua selects Core Inventory slots. The weapon mapping is in configs/rio_custom_weapons.lua.

Test

Start the resource, equip a supported weapon, holster it, and check its attachment. Use /wobtune only while adjusting positions, then turn the tuner off.

If a weapon is missing, verify the item/model in Rio-customweapons, the inventory adapter, and startup order. The client display file is FXAP-protected in this copy; use the supplied configuration and adapters for supported changes.