Why servers choose cr_wirestripper

• 🎯 Real map props: Targets A/C units (prop_aircon_m_02, _m_04, _m_06)—no map edits required.
• 🎮 Skill game: ox_lib skill check (keys & difficulty in config).
• 🧰 Tool-gated: requires wire_cutter (renameable) to start.
• 💰 Rewards: aluminum & copper with configurable min/max (default 1–8).
• ⚡ Shock on fail: sparks, camera shake, short ragdoll & small damage.
• 🚔 Dispatch: first-class ps-dispatch client exports (e.g., SuspiciousActivity or CustomAlert) or your own server event.
• 🔒 Anti-exploit: server-side distance & item checks, per-unit cooldown keyed by model+coords (not netId), optional player cooldown.
• 🧩 Bridges: swap Framework / Inventory / Target / Menu / Dispatch providers with open files—no core edits.
• ⚙️ Performance: event-driven, near-zero idle footprint on client & server.

What you get

• 🔓 Open (unescrowed): config.lua, shared/bridge_framework.lua, shared/bridge_inventory.lua, shared/bridge_target.lua, shared/bridge_menu.lua, shared/bridge_dispatch.lua
• 🔒 Escrowed core: server/main.lua, client/main.lua, client/targets.lua, client/dispatch.lua
• 📝 fxmanifest.lua with proper escrow_ignore
• 📘 Quickstart README (install, config, tips)

Quick Install

1. Drop the resource into your resources folder.
2. Ensure dependencies in the order you actually use:

   ensure ox_lib
   ensure qb-core            # or es_extended / qbx-core
   ensure ox_inventory       # or qb-inventory / ps-inventory
   ensure ox_target          # or qb-target
   ensure ps-dispatch        # optional (if using dispatch)
   ensure cr_wirestripper
         

3. Edit config.lua to match your server (items, providers, dispatch mode).

Config.Framework = 'auto'     -- 'auto' | 'qb' | 'esx' | 'qbox'
Config.Inventory = 'auto'     -- 'auto' | 'ox' | 'qb' | 'ps' | 'custom'
Config.Target    = 'auto'     -- 'auto' | 'ox_target' | 'qb-target'
Config.Menu      = 'auto'     -- 'auto' | 'ox_lib' | 'qb-menu'

Config.RequiredItem = 'wire_cutter'
Config.Rewards = { {item='aluminum',min=1,max=8}, {item='copper',min=1,max=8} }

Config.EntityCooldownSeconds = 3600  -- 60m per physical unit
Config.MaxDistanceValidate   = 4.0   -- server-side tolerance
Config.Shock = { enabled=true, damage=5, ragdollMs=2500, camShake=0.15, ptfxScale=1.2 }

-- Dispatch (client export or server event)
Config.Dispatch = {
  mode='client_export', chance=35, title='Suspicious Activity',
  message='Possible copper theft in progress near an A/C unit.', radius=45.0, code='10-90',
  exportRes='ps-dispatch', exportFn='SuspiciousActivity',  -- or 'CustomAlert'
  eventName='ps-dispatch:server:notify', debug=false
}
    

Customization & Extensibility

• Change the target/menu provider in config.lua—no core edits.
• Custom inventory? Switch Config.Inventory = 'custom' and implement three tiny functions in the open bridge_inventory.lua.
• Dispatch your way: use ps-dispatch client exports or set a server event name directly.
• Rewards/tool names: just match your item keys in ox_inventory/qb/ps.

Preview

🎬 Watch cr_wirestripper Gameplay

Support & Updates

Need help or feature requests? Join our Discord.

🔐 Licensing: Core files are escrowed. Configuration & integration bridges are open (unescrowed) for easy customization.