AWS Cocaine
Configurable collection and multi-step processing of cocaine products.
Installation
Requirements
- qb-core, ox_inventory, qb-target and PolyZone.
Startup order
This example selects one framework and target. Use the resources matching your configuration and start dependencies first.
ensure qb-core
ensure ox_inventory
ensure PolyZone
ensure qb-target
ensure aws-cocaine
Setup steps
- Register coca_leaf, coke, bakingsoda, coke_small_brick and coke_brick in your inventory.
- No dedicated SQL import is required by this package.
- Review lab entrance/exit and field/processing coordinates in config.lua before opening the job.
Gameplay and usage
- Gather leaves at the configured field, enter the lab, then process powder and bricks at their respective stations.
Configuration
- config.lua: CollectDuration, ProcessDuration, PackDuration, CircleZones, CokeLab and CokeProcessing.
- server/inventory.lua is the inventory adapter; webhook fields are blank by default.
Exports and integrations
No public callable export is declared with exports() in these source files. Use the documented commands or configuration; internal network events are not a trusted integration API.
Troubleshooting
-
Test inventory capacity and rollback when an output item cannot be added.
-
Validate interaction distance, processing delays and item balance on your server.
-
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-cocaine/config.lua:PickupDistance,CollectDuration,ProcessDuration,PackDuration,PropZOffset,Props,Anims,Delays,CircleZones,CokeLab,CokeProcessing,Webhooks
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.