AWS Weapons On Back
Visible holstered weapons with position presets and inventory bridge adapters.
Installation
Requirements
- ox_lib and ox_inventory in the supplied default manifest.
- Set configs/config.lua to the selected framework and inventory. Other inventory adapters are included but need their own installed resources.
Startup order
This example selects one framework and target. Use the resources matching your configuration and start dependencies first.
ensure ox_lib
ensure qb-core
ensure ox_inventory
ensure aws-weapons-on-back
Setup steps
- The server-specific Rio-customweapons hard dependency is removed; supplied position presets remain local.
- Configure weapon models and positions for models that actually exist on your server.
- Do not enable an inventory bridge whose inventory resource is not installed.
Gameplay and usage
- Equip/holster configured weapons and check visible attachments.
- /wobtune is available when the tuner configuration permits it.
Configuration
- configs/config.lua: framework, useDefaultInventory, tuner and weapon positions.
- configs/rio_custom_weapons.lua contains position/model presets; its historical filename is retained.
Exports and integrations
aws-weapons-on-back.IsWeaponObject— seeaws-weapons-on-back/client/editable.luafor its arguments and client/server context.aws-weapons-on-back.RefreshWeaponsForJob— seeaws-weapons-on-back/client/editable.luafor its arguments and client/server context.
Troubleshooting
-
Test inventory refresh, job-specific positions and cleanup after death/reconnect.
-
Nil-safe bridge expressions were converted to ordinary Lua; verify the chosen adapter with real inventory metadata.
-
Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.
Package reference
| Manifest | Version |
|---|---|
fxmanifest.lua |
1.0.1 |
Database files
No standalone SQL file is included. Check the installation steps above for tables created by server code.
Configuration reference
aws-weapons-on-back/configs/config.lua:framework,useDefaultInventory,debug,tuner,policeJobs,pistolWeaponGroup,exit_attachments,positions,disabledWeapons,weaponPositions,weaponCustomPositions,weaponGroupPostions,weaponGroupJobPostions,weaponJobPositionsaws-weapons-on-back/configs/core_inv_config.lua:enableInvaws-weapons-on-back/configs/rio_custom_weapons.lua:weaponJobPositions,customWeaponModels
Frequently asked questions
Does this need Keymaster or an escrow key?
The Lua sources in this delivery package were readable in the static audit. No /assetpacks requirement is added by this package. Required framework, inventory and map resources still need to be installed separately.
Can I change the folder or database table names?
Keep the supplied folder names. Historical event, SQL and KVP identifiers are retained to protect existing integrations and saved data. Renaming a table or event requires a separate migration.
Why is an interface or item missing?
Check the startup order, selected framework/target adapter, inventory item definitions and the server/F8 console. The package does not install an entire framework or inventory for you.
Has this been tested on my server?
ZIP integrity, source readability, script syntax and manifest references were checked locally. Multiplayer gameplay, your framework version and integrations require a FiveM server acceptance test before a public release.