Mining Job V3

Most free FiveM scripts stop at the first interaction — mine rock, get money, repeat. Mining Job V3 actually runs the full production chain inside a single resource: dig at Davis Quarry or the Chaparral Mineshaft, haul raw stone to a conveyor belt for processing, feed black stone into the furnace (coal required), then take finished ingots to the crafting bench to produce jewelry and sellable items. That four-stage loop is what makes the difference between a job players run once and one they keep coming back to — and it costs nothing.

The Production Chain in Detail

Each stage has its own friction built in, which is what keeps the economy balanced without needing server-side artificial limits. Pickaxes and stone pans have durability — they wear down through use and eventually break, creating an ongoing tool economy. Coal for the furnace comes from delivery missions rather than drops, so players coordinate around supply rather than hoarding indefinitely. Stone panning zones give randomized rewards, and uncut gemstones that come out of panning require a cracking tool before they're tradeable.

• Two default locations: Davis Quarry and Chaparral Mineshaft — both configurable

• Conveyor belt processing converts raw stone to black stone

• Furnace smelting stage gated by coal supply

• Crafting bench produces jewelry and custom items from ingots

• Stone panning zones with randomized loot pools

• Uncut gemstone mechanic — cracking tool required before gems are usable

• Coal delivery missions integrated into the job loop

• Tool breakage: pickaxes and pans degrade and break with use

• Quest system with configurable cash and item rewards

• Mining leaderboard tracking XP rankings across players

• Optional XP progression system — enable or disable per server preference

• Night-time lighting support at both mine locations

• Work uniform system with configurable outfit

• Portable and static workstation variants

Open Source Means You Own the Config

The source is fully open — no obfuscated Lua, no escrow lock. That matters when you're running a custom server economy and need to adjust drop rates, add a third mine location, or wire in a new crafting recipe without waiting on a developer update. Dependencies are ox_lib, oxmysql, bzzz-miningprops, and your framework's inventory, target, and vehicle key systems — nothing unusual for a QBCore or ESX server already running ox stack.

Framework Compatibility

Supports ESX, QBCore, and Qbox. The leaderboard and XP system work across all three. Rated 4.22/5 from nine reviews — for a free, open source script with this depth of crafting chain, that's a reliable foundation rather than a throwaway job script.