AWS Advanced Drug Dealing
A configurable street-selling system with NPC interactions, item pricing, delivery options and dispatch hooks.
Installation
Requirements
- QBCore or ESX. Qbox uses the supplied QB bridge and needs its qb-core compatibility path.
- The inventory containing the configured sale/delivery items
- The selected progress/notification/dispatch resources
Startup order
This example selects one framework and target. Use the resources matching your configuration and start dependencies first.
ensure qb-core
ensure aws-selling
Setup steps
- config.lua defaults to Config.Framework = qb. Select the intended adapter before installation.
- Register every item in Config.Drugs and the enabled Config.Delivery flow in your inventory.
- No custom SQL installer is included. Edit the included bridge files when integrating a custom inventory or dispatch provider.
Gameplay and usage
- Use /kosetut, approach a permitted NPC and test an enabled sale item.
- Check item removal, payment, declined transactions and the configured delivery entry flow.
Configuration
- config.lua: Config.CommandName defaults to kosetut; Config.MinimumPolice and BlacklistedJobs restrict selling.
- Config.Drugs contains sale items, prices and chances. Config.PaymentType selects the payout account.
- Config.DynamicDemand, TimeMultipliers, Zones and Delivery control the economy and activity flow.
- Config.DispatchSystem and CallPoliceChance control alerts; Config.NotifyType and ProgressBarType select feedback.
- Config.Webhook is disabled by default. Configure your own server webhook only if logging is needed.
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
-
Selling will not begin: verify item names, police-count/job rules and allowed zone.
-
Dispatch or progress is missing: inspect the selected bridge in bridge/client/.
-
Incorrect item/payment changes: inspect bridge/server/ for the active framework.
-
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-selling/config.lua:Locales,Framework,Lang,Debug,NotifyType,ProgressBarType,Webhook,CommandName,MinimumPolice,RequiredItem,InteractDistance,Animation,HandshakeAnimation,Drugs,BlacklistedJobs,DispatchSystem,CallPoliceChance,DynamicDemand
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.