AWS Electrical Job
An electrical repair job with depot interaction, work vehicles, repair minigames, groups and progression.
Installation
Requirements
- ox_lib and oxmysql
- One supported core: QBCore, Qbox or ESX
- ox_target or qb-target for the configured interaction path
Startup order
This example selects one framework and target. Use the resources matching your configuration and start dependencies first.
ensure ox_lib
ensure oxmysql
ensure qb-core
ensure qb-target
ensure aws-electricaljob
Setup steps
- Back up your database and import aws_electrical.sql for the supplied progression schema.
- Configure depot/NPC locations, vehicle spawns and repair zones before inviting players.
- Review payment and XP values against your server economy. Keep debug switches disabled for public use.
Gameplay and usage
- Interact with the configured depot NPC, open the job panel, begin a shift and obtain a work vehicle.
- Complete a repair, verify XP/payment, then end the shift and check group cleanup.
Configuration
- config/sh_config.lua: Config.Framework, Config.Target and Config.VehicleKeys select integrations.
- Config.Party, Config.Job.Electrical and Config.Minigame control teams, job flow and repair challenges.
- config/levelExperience.lua sets progression and experience rewards.
- config/translations.lua selects language; config/sv_config.lua contains the server webhook setting.
Exports and integrations
aws-electricaljob.OpenPanel— seeaws-electricaljob/client/panel.luafor its arguments and client/server context.aws-electricaljob.OpenPanel— seeaws-electricaljob/client/zz_tablet.luafor its arguments and client/server context.
Troubleshooting
-
No depot prompt: check target startup and configured positions.
-
No XP persistence: verify the imported schema, player identifier and oxmysql logs.
-
Vehicle access problems: verify the selected vehicle-key provider.
-
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 |
2.2.0 |
Database files
aws-electricaljob/aws_electrical.sql
Configuration reference
aws-electricaljob/config/levelExperience.lua:LevelExperience,Jobaws-electricaljob/config/sh_config.lua:Framework,Target,VehicleKeys,PartyRadius,UsePanel,UseTaskHud,Party,StartByNPC,DefaultBlip,BlipSettings,Job,Debug,DebugNotify,DebugTargetPoly,EnableDebugPrints,Minigame,WhitelistedProps,ReplacePropsaws-electricaljob/config/sv_config.lua:Webhook
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.