AWS Smoking
Cigarette packs with per-pack metadata, lighter checks and smoking interactions.
Installation
Requirements
- ox_lib and ox_inventory. AWS Notify is optional; the default library notification path remains available.
Startup order
This example selects one framework and target. Use the resources matching your configuration and start dependencies first.
ensure ox_lib
ensure ox_inventory
ensure aws-smoking
Setup steps
- Register cigarette_pack, cigarette and lighter with ox_inventory.
- Set the item client exports to aws-smoking.usePack and aws-smoking.useCigarette as documented by the source exports; do not consume those items a second time in your inventory definition.
- No SQL import is required; cigarettes remaining in each pack are stored in item metadata.
Gameplay and usage
- Use a pack to take a cigarette, then use the cigarette with a lighter.
Configuration
- config.lua: PackItem, CigaretteItem, LighterItem, PackCapacity and Smoke.
Exports and integrations
aws-smoking.usePack— seeaws-smoking/client/main.luafor its arguments and client/server context.aws-smoking.useCigarette— seeaws-smoking/client/main.luafor its arguments and client/server context.
Troubleshooting
-
Check pack metadata, last-cigarette removal, missing lighter and full inventory rollback.
-
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.0 |
Database files
No standalone SQL file is included. Check the installation steps above for tables created by server code.
Configuration reference
aws-smoking/config.lua:PackItem,CigaretteItem,LighterItem,PackCapacity,TakeFromPack,Smoke,Locale
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.