Modul Spikes

Spike strips that just work — for everyone on the server. Modul Spikes is a server-authoritative spike strip system: no ghost strips, no duplicates, no props only half the server can see. Terrain-aware placement, tire popping fast cars can't outrun, trunk stock for cruisers and four access modes — with zero dependencies, on Qbox, QBCore, ESX or fully standalone.

Qbox QBCore ESX Standalone ox_inventory qb-inventory ox_target qb-target No dependencies

Sync that actually holds up

Every spike script bug report you've ever read — ghost strips after a crash, strips some players can't see, duplicated props — comes from networked entities. Modul Spikes doesn't use any. The server owns the only authoritative spike state and every client renders lightweight local props from it: identical placement for everyone, automatic resync for late joiners, cleanup on disconnect, and strips that exist consistently at any distance the moment a player gets close. OneSync Legacy and Infinity, no caveats.

One deploy, a whole row across the road

• Deploy 1–N strips per action in a continuous end-to-end line (or a fan spread) — via rebindable keybind, chat command, or usable inventory item
• Optional ghost preview: transparent strips follow your aim with valid/invalid tinting, ENTER confirms, BACKSPACE cancels — pure game props, no NUI
• Terrain-aware raycast placement: strips match ground pitch and roll on hills, banked shoulders, ramps and curbs instead of floating or clipping
• Placement into walls, fences, vehicles, water or extreme slopes is rejected with a clean notice
• Optional deploy-from-vehicle mode drops the row behind your car mid-pursuit
• Kneel-and-place animation, optional progress bar, fold-out strip animation

Tire popping that can't be outrun

• Per-wheel contact detection against each strip's real footprint — up to 10 wheel bones, so bikes, sedans and 6+ wheelers all pop correctly
• Checks tighten to every frame in a speed-scaled window right before impact — a 200 km/h car cannot tunnel through a strip between ticks
• Three pop modes: only the wheels physically on the strip, the two nearest wheels, or all tires; instant burst or slow puncture deflate
• The driver's own client pops the tires, so under OneSync the burst replicates natively to every player — perfect sync, zero server round-trips
• NPC traffic untouched by default (a forgotten strip won't jam a highway); optional NPC mode is bounded to network-owned vehicles — no double popping
• Immunity rules: emergency class, vehicle classes, specific models, driver jobs

Four ways to hand out spikes

• Whitelist — anyone passing permissions deploys freely; perfect for standalone servers
• Inventory — deploying consumes a spike strip item; picking up returns it (ready-made item definitions + icon shipped for ox_inventory, QBCore and ESX)
• Vehicle — officers grab a limited stock from the trunk of whitelisted cruisers, tracked per plate for the session, with carry limits and store-back
• Both — carried trunk strips first, then inventory items

Pickup rules your server decides

• Press to pick up a single strip, hold to sweep every strip nearby
• Owner-only or police-only pickup — or leave it open so criminals can defensively clear a road
• Strips auto-expire on a timer and vanish with their owner's disconnect — the map never accumulates junk

Permissions that fit any server

• Framework jobs with minimum grades and an optional on-duty requirement
• ACE permissions — works everywhere, including standalone
• Standalone identifier whitelist (license, discord, …)
• Or one switch to open it to everyone — enforced server-side in every mode

Admin & integrations

• Clear all strips or one player's, live debug toggle across server + clients, full state dump — ACE and framework admin groups
• 4 client + 4 server exports (deploy, pickup, nearby query, active state/counts) and documented events for pursuit scripts, dispatch or MDT integrations
• English and Spanish shipped; add any language by copying one open locale file

Requirements: none. Fully standalone-capable. Framework (Qbox / QBCore / ESX), inventory, target, notify and progress resources are all optional and auto-detected. No database, no NUI, nothing to build.

Installation: drop into resources, ensure modul_spikes, pick your framework and access mode in the config — done. Ready-to-paste item definitions and an item icon are included for inventory modes.