Advanced Wheel Clamp

Q: qb-target option does not appear when item requirement is enabled

For QB setups, the wheel_clamp item must have useable = true in qb-core/shared/items.lua. Older docs sometimes showed false, which breaks qb-target item checks. Also confirm the item name in inventory matches config (wheel_clamp).

Q: The clamp works but the prop is invisible to other players

Whitelist gs_wheelclamp in your anti-cheat. The prop spawns server-side, but client-side attachment to the wheel can be deleted or blocked by AC scripts. Also avoid running ox_target and qb-target at the same time. That combination has caused invisible props and broken sync.

Q: Does this require a specific job or item?

Jobs and items are configurable. Disable Config.RequiredItem temporarily to test whether item setup is the issue, then re-enable once inventory and target are correct.

Resource folder: gs_wheelclamp

View product

Installation Instructions for Advanced Wheel Clamp

Follow these steps to install and configure gs_wheelclamp on your FiveM server.

Download the Resource
- Go to portal.cfx.re
- Navigate to Assets > Granted Assets > gs_wheelclamp
- Download the resource
Extract the Files
- Open the downloaded .zip file
- Inside, you'll find a folder named gs_wheelclamp
- Move the entire gs_wheelclamp folder into your desired server resources folder (e.g., /resources/[scripts])
Add to Server Configuration
- Open your server.cfg
- Add the following line:
```
ensure gs_wheelclamp
```
Restart the Server
- Restart your FiveM server (Important!)
Configure the Script (Optional)
- Navigate to gs_wheelclamp/config.lua
- Edit the configuration options to fit your server's needs

Included images

Installation Instructions

Add the following items to your ox_inventory/data/items.lua file:

['wheel_clamp'] = {
    label = 'Wheel Clamp',
    weight = 1000,
},

Execute the following SQL query to add the items to the database:

INSERT INTO
	`items` (`name`, `label`, `weight`, `rare`, `can_remove`)
VALUES
	('wheel_clamp', 'Wheel Clamp', 1, 0, 1);

Add the following items to your qb-core/shared/items.lua file:

['wheel_clamp'] = {
    ['name'] = 'wheel_clamp',
    ['label'] = 'Wheel Clamp',
    ['weight'] = 1000,
    ['type'] = 'item',
    ['image'] = 'wheel_clamp.png',
    ['unique'] = false,
    ['useable'] = false,
    ['shouldClose'] = true,
    ['combinable'] = nil,
},

qb-target option does not appear when item requirement is enabled

For QB setups, the wheel_clamp item must have useable = true in qb-core/shared/items.lua. Older docs sometimes showed false, which breaks qb-target item checks.

Also confirm the item name in inventory matches config (wheel_clamp).

I run both ox_target and qb-target

Do not run both together. They conflict on the same key and can break menus, prop sync, and item checks. Pick one target system for your server.

The wheel clamp option only appears when I disable the item requirement

That usually means the inventory item is misconfigured or the wrong target system is handling the interaction. Fix the QB item setup first. With item requirement off, ox_target may answer instead of qb-target, which hides the real problem.

Lockpick option always shows on every vehicle

Edit the client bridge and remove the qb-target lockpick entry if you only want clamp-specific actions.

The clamp works but the prop is invisible to other players

Whitelist gs_wheelclamp in your anti-cheat. The prop spawns server-side, but client-side attachment to the wheel can be deleted or blocked by AC scripts.

Also avoid running ox_target and qb-target at the same time. That combination has caused invisible props and broken sync.

The clamp blocks the vehicle but nobody sees the prop

Same as above: anti-cheat whitelist and a single target system. Test with AC relaxed on a dev server to confirm.

Can civilians lockpick or remove clamps?

Lockpick support is configurable and tied to your target bridge setup. If lockpick shows when it should not, trim the extra qb-target option from the bridge.

Does this require a specific job or item?

Jobs and items are configurable. Disable Config.RequiredItem temporarily to test whether item setup is the issue, then re-enable once inventory and target are correct.