AWS Miner Job

Mining job with ore extraction, pickaxes, progression, missions and a tablet.

Installation

Requirements

• ox_lib, oxmysql and the selected framework/inventory adapter.
• Included miner_props and marker_props resources.
• The target selected in config; K4MB1 cave is optional and disabled by default.

Startup order

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

ensure oxmysql
ensure ox_lib
ensure qb-core
ensure ox_inventory
ensure qb-target
ensure miner_props
ensure marker_props
ensure aws-minerjob

Setup steps

1. Extract all three resource folders from the ZIP.
2. server/database.lua creates the qs_miner family of tables; retain those names for existing player data.
3. Register configured pickaxes, minerals and processed products in your inventory.

Gameplay and usage

1. Interact with the mining NPC and select a job/mission in the tablet.
2. Mine ore using the configured pickaxe, then test processing and selling.

Configuration

• config/config.lua controls framework, inventory, target, ore levels, respawn and locations.
• Keep Config.K4MB1Cave=false unless you own and install that optional map.
• Set Config.TargetScript to the target actually installed; the original server used a qb-target compatibility shim.

Exports and integrations

• aws-minerjob.togglePickaxe — see aws-minerjob/client/pickaxe.lua for its arguments and client/server context.
• aws-minerjob.ExitJob — see aws-minerjob/client/utility.lua for its arguments and client/server context.
• aws-minerjob.pickaxe — see aws-minerjob/server/inventory.lua for its arguments and client/server context.

Troubleshooting

• Check that props load and the expected ore can be mined.

• Test progression and reset/leaderboard records across a restart.

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

Package reference

Database files

• aws-minerjob/sql/qs_miner.sql

Configuration reference

• aws-minerjob/config/clothing.lua: Framework
• aws-minerjob/config/config.lua: Framework, Inventory, Dispatch, Phone, Wardrobe, Garage, RequireJob, MinerJob, Target, TargetScript, DefaultNotifications, EnableMarker, MarkerColor, RespawnTime, K4MB1Cave, DrawOutline, InventoryPickaxe, QuasarInventory

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.