ss-spikestrip by Sparki is an ESX resource for placing and retrieving a tyre-spike prop. The linked archive declares version 1.0.0. It uses ox_lib progress bars and notifications, ox_target pickup interaction and an ox_inventory item example.
Install the extracted resource
Extract the ZIP and place the ss-spikestrip folder containing fxmanifest.lua in resources. Start es_extended, ox_lib, ox_target and ox_inventory before ensure ss-spikestrip. A ZIP left in resources is not an installed resource.
The README defines spike_strip in ox_inventory/data/items.lua with a client event named spike_strip:use. Check the definition and consumption behavior against your inventory version. The server also registers an ESX usable item; neither that handler nor placement removes an item explicitly. Confirm exactly one item is consumed and returned across success and cancellation.
The server initializes ESX through the deprecated esx:getSharedObject event. Adapt this to the supported import or export for your ESX version before testing. The archive is not evidence of seamless compatibility with current ESX.
Placement, pickup and limitations
Placement has a cancellable 1000-millisecond progress bar; pickup takes 5000 milliseconds and disables cancellation. The placer scans nearby client vehicles every 100 milliseconds and bursts tyre indexes 0–5 when the vehicle position is within 1.5 units of the prop. This is a proximity test, not individual wheel contact.
Pickup grants an item after checking only that an ESX player exists. There is no server record tying the request to a deployed strip, owner or pickup distance, and no police-job restriction. Add authoritative placement, consumption and one-time pickup validation before exposing this to players.
Pickup targets are registered locally by the placing client. Test visibility and pickup from another player, vehicle ownership changes, cancellation and resource restarts. The stored prop list has no resource-stop cleanup handler; the supplied code does not establish reliable multiplayer recovery.
Original video preview
The exact linked archive and all four source files were inspected on 10 September 2026. No FiveM placement, tyre synchronization or inventory test was performed.