AWSAWS DOCUMENTATION38 source-matched resource guides
Documentation/Gameplay/AWS Weed
Gameplay2 min readUpdated 2026-10-15
AWS Weed cover
AWS resource illustration

AWS Weed

Cannabis collection, processing and rolling-paper production steps.

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

Setup steps

  1. Register cannabis, marijuana, joint and rolling_paper (or aws_weed_rolling_paper).
  2. No dedicated SQL import is required. Adjust field/processing locations to your server.

Gameplay and usage

  1. Collect at the configured field, process cannabis and use rolling paper with marijuana to make joints.

Configuration

  • config.lua: CircleZones, CollectDuration, ProcessDuration, RollDuration and plant respawn values.

Exports and integrations

  • aws-weed.useRollingPaper — see aws-weed/client/weed.lua for its arguments and client/server context.
  • aws-weed.startRoll — see aws-weed/client/weed.lua for its arguments and client/server context.

Troubleshooting

  • Test full inventories and confirm consumed ingredients are restored if adding the output fails.

  • Validate collection/processing distance and repeat-event delays.

  • 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-weed/config.lua: PickupDistance, CollectDuration, ProcessDuration, RollDuration, MaxWeedPlants, WeedRespawnAfterPicks, WeedRespawnDelay, Props, Anims, CircleZones, 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.