QBCore Item Use Not Working? Fix Usable Items

Match the item key first

Usable-item problems often start with naming. The item key in shared items, inventory data, shop rewards and usable registration must be the same key. A label can be friendly, but the internal item name must match exactly. If the item appears in the inventory but the click does nothing, check whether the usable callback is registered for the same key that the player actually owns. A typo, underscore difference or plural name can make the callback silently irrelevant.

Next identify your inventory resource. A server using qb-inventory may register items differently from a server using ox_inventory with a QBCore bridge. Do not mix examples without adapting them. Paste the inventory resource name into Stellar AI together with the item definition and callback. That context prevents a patch for the wrong inventory system.

item key in inventory:
usable registration key:
server callback:
client event:
inventory resource:
first console error:

Prove the callback fires

Add a temporary server-side print at the start of the usable-item callback. If the print never appears, the item is not registered as usable or the wrong inventory bridge is active. If the server print appears but the client effect does not, inspect the client event name, event registration and whether the client file is actually loaded by fxmanifest.lua. If the client event fires but the result fails, the problem is inside the effect logic rather than item registration.

Keep important results server-authoritative. Removing an item, giving money, applying rewards or changing saved player data should be validated on the server. The client can show an animation or progress bar, but it should not decide final rewards. A quick fix that moves everything to the client can create duplication or exploit problems.

Check cooldowns, remove logic and failure paths

Usable items need clean failure handling. What happens if the player uses the item twice quickly? What happens if the item is removed before the animation finishes? What happens if the target is invalid? A stable item use flow checks ownership, blocks spam, performs the action, then removes or updates the item only when the server accepts the result. If the item is consumed before validation, players can lose items on failure. If it is consumed after a client-only action, players may be able to replay events.

After patching, test success and failure. Use the item with the right conditions, use it without the required condition, spam it, restart and test again. That proves the item appears, the callback fires, the correct player is affected and the server stays in control.