Troubleshooting
The things that go wrong with a rope, and where to look.
A change to the resource did nothing
Section titled “A change to the resource did nothing”restart does not re-read fxmanifest.lua. After updating mic_drag to a new version, or adding a file, run refresh in the server console first and then restart mic_drag. Edits to config.lua only need the restart.
The resource stops on start with “Config.Framework must be esx or qbcore”
Section titled “The resource stops on start with “Config.Framework must be esx or qbcore””Config.Framework in config.lua is something other than esx or qbcore. There is no auto-detect — set it to the framework you run. If it is already right, mic_drag is starting before your framework: move ensure mic_drag below it in server.cfg.
On QBox, the value is qbcore — QBox runs QBCore resources through its compatibility layer — and qbx_core must start before mic_drag.
Using the item does nothing
Section titled “Using the item does nothing”In order:
- The item is not registered. The rope registers
Config.Itemthrough your framework’s usable items. If your inventory uses its own item callbacks instead, triggermic_drag:useRopefrom there (see “The bridge” in Customization). - QBCore item name. The shipped QBCore entry has
nameset toRope. It must berope, the same as the key and asConfig.Item. - The prop does not load. The rope prop streams from
stream/. If that folder was not uploaded, the rope never appears in your hand. - You are being dragged yourself. Nothing can be used from the end of a rope.
The rope is in my hand but I can not grab anyone
Section titled “The rope is in my hand but I can not grab anyone”- The rope only grabs players — not NPCs, not yourself.
- They must be on foot, alive, and within
Config.MaxDetectionDistance(2 m by default). You must be on foot too. - The server checks that you still carry the item when the drag starts. If it left your inventory while the prop was out, the grab is refused.
- You can only drag one person at a time, and a person already on a rope can not be grabbed twice.
The target option never shows
Section titled “The target option never shows”Look at the client console (F8). “ox_target is not started; using drawtext until it starts” means the target in Config.InteractionSystem is not running — the rope is using 3D text and E instead. Check the name is exactly ox_target or qb-target; anything else prints “Unknown InteractionSystem” and uses drawtext.
I can not tie the rope to a car
Section titled “I can not tie the rope to a car”You must be dragging someone, with the rope in your hand, within Config.MaxVehicleAttachDistance of the vehicle (5 m by default). The vehicle must be a networked vehicle — local, client-only vehicles are refused.
The prompt shows the wrong key
Section titled “The prompt shows the wrong key”You changed Config.AttachKey or Config.AttachToVehicleKey but not Config.KeyLabels. The labels are only text; update them to match.
The rope broke on its own
Section titled “The rope broke on its own”Config.EnableMaxDragTime is on and Config.MaxDragTime seconds have passed. The rope also comes off when either player leaves, when the vehicle it is tied to is deleted, or when the dragged player goes out of range of the one dragging.
The dragged player can still move their camera or press keys
Section titled “The dragged player can still move their camera or press keys”Config.DisableControls is off. Turn it on to block every control while someone is on the rope.