The difference between a metal detecting script players run once and one they return to is progression. Metal Detecting 2 builds the activity around a proper leveling system — detectors are tiered and locked behind levels, the loot pool scales with rank, and players who invest time in the hobby find better items than those who just picked up a detector for the first time. That structure turns a solo leisure activity into a long-term character investment.

Five Detector Tiers Tied to Player Level

Each of the five custom detector props has its own loot pool, cooldown, and detection radius. Low-tier detectors find common items at close range with slower beeps. Higher-tier equipment covers more ground per sweep, pings at greater distances, and unlocks access to rarer item categories. Players buy detectors from the level-gated shop — you can’t skip to the best equipment on day one, which keeps the progression curve meaningful rather than decorative.

Key Features

• 5 custom metal detector props, each with configurable loot pool, detection radius, and cooldown
• Level-locked detector access — higher tiers require earned experience before purchase
• 50+ discoverable items ranging from bottle caps and coins to gold watches and rare finds
• Configurable XP rewards, item quantities, and sell prices per item
• Soil type configuration — define which terrain types support detecting activity
• Restricted zone support to limit detecting in specific map areas
• Dual shop system: level-gated detector purchase vendor and separate loot sell shop
• Lifetime player statistics tracking — items found, total earnings
• Detailed Discord webhook logs for admin oversight
• Active inventory check — detector must remain in inventory during use, cannot detect from a vehicle
• Optional job restriction configuration
• Open-source bridge folder for framework-specific events — readable and extensible
• Approximately 1,800 lines of code
• Requires: OneSync Infinity, Server v7290+, ox_lib, oxmysql, interact-sound or xsound
• Framework support: ESX, QBCore, Qbox

Soil Types Make Geography Matter

Configuring which terrain types support detecting means the activity isn’t uniform across the map. Beaches, parks, and rural areas work; concrete downtown blocks don’t. That constraint creates geographic logic — players travel to specific locations because the terrain allows it, which produces natural player distribution and gives the activity a sense of place. A server where everyone knows to head to Vespucci Beach to detect feels more like a living world than one where any sidewalk counts.

The Dual Shop Design

Two separate vendors handle the economy on each end. One sells detectors with level gates; the other buys what players dig up. Keeping them separate lets you tune each side independently — adjust detector pricing without touching loot sell values, or rework the sell vendor for a specific server economy without changing equipment costs. That granularity is the difference between an economy loop you can balance and one you’re constantly fighting.

Framework Compatibility

ESX, QBCore, and Qbox are supported through an open-source bridge folder that exposes framework-specific functions. Server devs can modify behavior or add integrations by reading the bridge — it’s documented, not a black box.