Skip to main content
Filter the server console and the F8 client console for nexdev_crutchsystem first.

Common issues

Rate limiting

Every player-triggered event is rate-limited and server-validated:
  • canAfford re-checks the price, the has-crutch state, the near-medic state, and the player’s wallet.
  • chargeMoney validates the same again before debiting.
  • selfRemoveInternal validates again before clearing the crutch.
If a player sees their action repeatedly fail with no clear reason, it’s almost always one of these gates. Set Config.Debug = true (in config.lua, if exposed in your build) or read the server console — each rejection logs the reason.

Before opening a support ticket

Please include:
  1. Server console output filtered for nexdev_crutchsystem.
  2. F8 client console output filtered for nexdev_crutchsystem.
  3. Your framework (Qbox / QBCore / ESX / ND_Core), inventory, and ambulance job.
  4. Your Config.AllowedJobs entries and the value of playerData.job.name for the affected player.
  5. What you did and what you expected to happen.
See Support & contact.