Troubleshooting

❓ Common Issues & Solutions

Q: The /implants command doesn't work

A:

1. Make sure the resource is running: ensure alone-implants in server.cfg

2. Check the server console for startup errors

3. Verify oxmysql is started before alone-implants

4. Restart the resource: restart alone-implants

Q: The interface opens but shows no implants

A:

1. The player needs implant items in their inventory

2. Give yourself an item to test: giveitem [id] implant_double_jump 1

3. If items exist but don't appear, check that item names match the format implant_[id]

4. Verify your inventory resource is running and items are registered

5. Check the server console — it prints which inventory was detected on startup

Q: Implants install but abilities don't work

A:

1. Check if keybinds are enabled: Config.Keybinds.Enabled = true

2. Verify the player has bound the correct keys (Settings > Key Bindings > FiveM)

3. Check if the player is in a vehicle (Config.Security.BlockActivationsInVehicle)

4. Check if the system is overheated (look for red HUD indicator)

5. Verify the implant has durability remaining

Q: Double Jump doesn't work

A:

1. If Config.Rules.DoubleJumpRequireBothLegs = true, the implant must be installed on both legs

2. Check that the double_jump implant is on leg_l AND leg_r

3. Make sure the player is in the air before pressing Space again

4. Check cooldown — there's a 4-second default cooldown between jumps

Q: Framework not detected

A:

1. Make sure your framework (ESX/QB-Core/QBOX) is properly installed

2. The script auto-detects — no manual configuration needed

3. Restart the resource: restart alone-implants

4. Check the server console for detection messages

Q: Database errors on startup

A:

1. Verify oxmysql is installed and configured correctly

2. Check your database connection string in server.cfg

3. Import the SQL file: sql/install.sql

4. Make sure the player_implants table exists in your database

Q: Implant images don't show in the UI

A:

1. Check that images exist in your inventory's image folder (see Installation Guide)

2. Images must be named: implant_[id].png (e.g., implant_double_jump.png)

3. Supported format: PNG

4. If images are missing, a fallback placeholder is shown

5. If using a non-standard inventory, set Config.Inventory.ImagePath to your custom image path

Q: Inventory not detected / wrong inventory used

A:

1. The script auto-detects your inventory on startup — check the server console for the detection message

2. Make sure your inventory resource starts before alone-implants in server.cfg

3. If auto-detection picks the wrong inventory, force it in config.lua:

   Config.Inventory = {
       Type = 'ox',  -- or 'qs', 'ps', 'codem', 'core', 'origen', 'tgiann', 'mf', 'qb', 'esx'
       ImagePath = '',
   }

4. See the Configuration Guide for all supported values

Q: The Cooldown HUD doesn't appear

A: The Cooldown HUD only appears when:

1. An ability is actively running (cyan ring)

2. An ability is on cooldown (blue ring)

3. The system is overheated (red ring)

If no timers are active, the HUD is hidden — this is intended behavior.

Q: Implant broke and disappeared

A: This is intended behavior when Config.Durability.Enabled = true:

1. Each activation reduces durability by Config.Durability.LossOnActivate

2. At 0 durability, the implant breaks and is removed

3. A notification is shown when durability is critically low

4. To disable this: set Config.Durability.Enabled = false

Q: "System Overheated" keeps appearing

A: Players are using abilities too frequently:

1. Each ability has a heatCost — using many abilities quickly builds heat

2. At max heat (default 100), the system locks for Config.Heat.Overheat.BlockSeconds

3. Solutions:

   • Increase Config.Heat.Max (e.g., 150)

   • Increase Config.Heat.DecayPerSecond rates

   • Decrease Config.Heat.Overheat.BlockSeconds

   • Reduce implant heatCost via Config.ImplantOverrides

Q: Can I add custom implants?

A: The implant catalog is escrow-protected and cannot be modified directly. However, you can:

1. Override properties of existing implants via Config.ImplantOverrides

2. Change costs, cooldowns, heat costs, effects, and incompatibilities

3. Disable implants effectively by setting extreme requirements

Q: Clinic location restriction doesn't work

A:

1. Make sure Config.Clinic.RequireClinic = true

2. Verify coordinates in Config.Clinic.Zones:

   Zones = {
       { coords = vec3(312.2, -592.8, 43.3), radius = 4.0 },
   }

3. The player must be within radius of the coords to open the menu

4. Use /tp to verify the coordinates are correct

Q: Players can install more implants than the limit

A:

1. Check Config.Rules.MaxActiveImplants and Config.Rules.MaxPassiveImplants

2. Remember: double_jump on both legs counts as 1 active implant

3. The limits are enforced server-side — they cannot be bypassed

Q: Discord webhook logs aren't working

A:

1. Set Config.Logs.Webhook.Enabled = true

2. Add your Discord webhook URL to Config.Logs.Webhook.Url

3. Make sure the webhook URL is valid and the channel exists

4. Test by installing an implant and checking the Discord channel

Q: Passive slots don't show in the interface

A:

1. Passive slots appear below the catalog on the left panel

2. Make sure passive implants exist (they should be in the catalog by default)

3. Passive implants are listed under the "PASSIVE" section in the catalog

4. Drag passive implants to the 4 passive slots (not the body map)

Q: Performance issues

A:

1. The script is optimized for performance with server-authoritative architecture

2. All validation happens server-side — minimal client overhead

3. If experiencing issues:

   • Check server console for repetitive error messages

   • Verify oxmysql performance

   • Set Config.Logs.Print = false to reduce console output

🔧 Debug Mode

Enable detailed logging in the server console:

Config.Logs = {
    Enabled = true,
    Print = true,  -- Shows detailed prints in F8 / console
}

Check the server console (F8) for:

• Implant installation/removal events

• Heat level changes

• Durability updates

• Error messages with context

📊 Server Commands

Command	Description
/implants	Open the implant interface
ensure alone-implants	Start/restart the resource
restart alone-implants	Restart the resource

⚠️ Important Notes

• Asset Escrow: Only config.lua is editable — do not attempt to modify other files

• Database: Always back up your player_implants table before major changes

• Updates: When updating, your config.lua will be preserved but check for new options

• Testing: Always test configuration changes on a development server first

---

Still having issues? Check the server console for detailed error messages.

Last updated: February 2026