AWS Meth

Journey camper production with configured ingredients, timing and location rules.

Installation

Requirements

• qb-core, ox_inventory and ox_lib.

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-meth

Setup steps

1. Register every item named in Config.Items.
2. No dedicated SQL import is required. The server-specific rioguard exemption was removed from the portable package.

Gameplay and usage

1. Use the configured Journey vehicle and production seat in the allowed area; press the configured start control (E by default).

Configuration

• config.lua: VehicleModel, MinNorthY, TickMs, PassengerSeat, Items and production events.

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 ingredient consumption, output capacity, interruptions and server-side reward rules.

• If your anti-cheat flags valid particles, configure a narrow integration in your own anti-cheat; no blanket bypass is included.

• Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.

Package reference

Database files

No standalone SQL file is included. Check the installation steps above for tables created by server code.

Configuration reference

• aws-meth/config.lua: StartControl, VehicleModel, VehicleHash, MinNorthY, TickMs, PassengerSeat, Items, Events

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.