AWS Fragmentation

A vehicle chopping system with contracts, a tablet interface, group play, item rewards and progression.

Installation

Requirements

• oxmysql
• One supported core: QBCore, Qbox or ESX
• The inventory, target, notification, minigame and dispatch providers enabled in config.lua

Startup order

This example selects one framework and target. Use the resources matching your configuration and start dependencies first.

ensure oxmysql
ensure qb-core
ensure aws-fragmentation

Setup steps

1. Back up your database and import database.sql.
2. Register chop_tablet, screwdriverset, chop_scanner, jammer and the material rewards enabled in your configuration. Use the schema required by your inventory.
3. Configure the usable chop_tablet item to call the client export aws-fragmentation.chop_tablet when your inventory requires an explicit export.
4. Review Config.RequiredItems and Config.BossNPC. The shipped boss NPC can be disabled, making the tablet the normal entry point.

Gameplay and usage

1. Use the configured tablet, select a contract and complete its vehicle/parts flow.
2. Verify material rewards, XP, group membership and dispatch behavior on a test server.

Configuration

• config.lua: Config.Framework, NotifySystem and DispatchSystem select providers.
• Config.MissionSystem, Groups and Locations define contracts, group rules and work locations.
• Config.Parts, FinalReward, Market, XPSystem and Skills control rewards and progression.
• Config.PreventOwnedVehicles, MinimumPolice, Cooldown and dispatch chance configure gameplay restrictions.

Exports and integrations

• aws-fragmentation.chop_tablet — see aws-fragmentation/client/main.lua for its arguments and client/server context.
• aws-fragmentation.jammer — see aws-fragmentation/client/main.lua for its arguments and client/server context.

Troubleshooting

• If the tablet does not open, verify the exact item name and client export binding.

• If a vehicle is rejected, review ownership, class, contract and police-count rules.

• If progress is lost, inspect database.sql tables and player identifiers.

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

Package reference

Database files

• aws-fragmentation/database.sql

Configuration reference

• aws-fragmentation/config.lua: Locale, Framework, NotifySystem, UseTarget, DispatchEnabled, DispatchChance, PreventOwnedVehicles, MinimumPolice, Cooldown, DispatchSystem, RequiredItems, AdminList, Logs, BossNPC, Minigame, HackerMinigame, Groups, MissionSystem

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.