AWS Weapon Filter

An ox_inventory weapon-whitelist enforcement resource. The effective whitelist and security options are loaded from ox_inventory/data/weapon_whitelist.lua. The local config loader translates this data into weapon hashes and reads known weapons.

Requirements

• ox_inventory
• ox_lib
• A valid ox_inventory/data/weapon_whitelist.lua file; without it enforcement starts disabled
• Optional FiniAC integration referenced by the manifest

Configure

Create or edit ox_inventory/data/weapon_whitelist.lua to return a table:

return {
    enabled = true,
    allowed = {
        'WEAPON_PISTOL',
        'WEAPON_FLASHLIGHT',
    },
    security = {
        scanInterval = 750,
        logViolations = true,
        kickAfterViolations = 0,
        stripNpcWeapons = true,
        purgeInventory = false,
    },
}

Use weapon names exactly as they appear in ox_inventory/data/weapons.lua. Keep purgeInventory disabled until the list has been tested on staging; an incomplete whitelist may remove legitimate weapons. kickAfterViolations = 0 disables automatic kicks.

Start ox_lib and ox_inventory first, then ensure rio-weapon-filter. Test permitted, blocked, and custom weapons. Review logs before enabling kicks or inventory purging. Enforcement client/server files are FXAP-protected in this copy; configuration is the documented surface.