What goes wrong most often with Crutches, what it actually means, and what to do about it. Several of these are not bugs at all, but the script doing exactly what it was built to do.
Installation#
Using the crutch item does nothing
The item is not in your inventory's item list, or it is not named exactly
crutch. See Adding the Crutch Item.Your framework starts after
qs-crutchesinserver.cfg. It is detected only if it is already running, so moveensure qs-crutchesbelow it.On qb-inventory, the item must have
useable = true.
Unknown column 'crutch_forced_until' or 'crutch_manual'
The SQL was not imported, or the wrong one was. ESX adds the columns to users; QBCore and Qbox add them to players. Import the file for your framework from [sql]/ and restart. Without these columns nothing is saved, so crutches are lost on every reconnect.
The console is full of [DEBUG 1.0.8] lines
Config.Debug ships set to true. Set it to false in config.lua and restart the resource.
"API is not available. Unable to check the version."
Harmless. The update check could not reach GitHub when the server started. The script works the same either way.
The Crutch and Movement#
The player limps but there is no crutch in their hand
The crutch model is not loaded. Check that:
The
crutchesresource is in your resources folder andensure crutchescomes beforeensure qs-crutches.It was downloaded with the Cfx.re account that owns the asset, on a server key tied to that account. Otherwise it is encrypted for someone else and does not load.
Config.CrutchModelstill points tov_med_crutch01, or to a model you stream yourself.
The crutch floats or sits in the wrong place
Usually an addon ped with a different skeleton, or a replacement model. Adjust pos and rot in Config.Attach a little at a time and restart the resource to see each change. See The Crutch Prop.
The player is crawling and cannot stand up
Correct behaviour. A player on a prescription who has lost their crutch — to a hit, a fall or /dropcrutch — crawls until they get it back. The crutch is on the ground close to where it fell: crawl to it and press E. If it was deleted by an entity clean-up script, a new one is put in their hand automatically.
The crutch cannot be picked up
After a hit, the crutch cannot be picked up for 2 seconds.
The prompt only appears within about 2 metres, and not while the player is still falling or ragdolling.
Each player can only pick up their own crutch.
The player cannot sprint, jump, shoot or open the weapon wheel
Correct behaviour while on crutches. Everything comes back when the prescription ends. To end it early, a paramedic uses /crutchmenu → Remove crutches from player, or an admin script calls RemoveCrutch.
Saving and Reconnecting#
The crutches came back after the player reconnected
Correct behaviour. A prescription is saved on the character and survives disconnects and restarts until its time is up. Remove it with the EMS menu or RemoveCrutch if it should not be there.
The crutches did not come back after a reconnect
The time ran out while the player was offline. The clock never pauses.
The SQL columns are missing — see above.
Your multicharacter loads the character after the script has already asked. Add a sync call to its loaded event — see Character Loading.
The EMS Menu#
"No permission." on /crutchmenu
The player's job is not in Config.AllowedJobs. The list takes the internal job name — ambulance, not "EMS" or "Paramedic". Add yours and restart the resource.
The menu does not open at all
If the F8 console shows [qs-crutches] ox_lib not loaded..., ox_lib is missing or starts after Crutches. Put ensure ox_lib near the top of server.cfg.
"No nearby player found"
Nearby player only reaches 3 metres. Step closer, or use By ID with the patient's server ID.
"Invalid player." or "Invalid minutes."
The ID typed is not online, or the minutes were 0 or empty. Nothing was applied.
Logs and Languages#
Nothing is posted to Discord
Webhook.URL in server/webhook.lua is empty, or the webhook was deleted in Discord. Expiries and manual crutches are never logged — only applications and removals.
A message shows a key like menu_title instead of text
That key is missing from the language file in use — usually an older or hand-made locale. Copy the missing line from locales/en.lua and translate it.
The language does not change
Config.Language must match a file name in locales/ exactly: jp for Japanese, zh-CN for Chinese. Any code without a file falls back to English.
Still stuck? Open a ticket and include your framework and inventory, the
server.cfglines for Crutches and its dependencies, and the server console output withConfig.Debug = true.



