Troubleshooting & FAQ

🆘 Troubleshooting & FAQ

Found an issue? Don't panic! Most problems are caused by small configuration mistakes. Check this guide to resolve them in seconds.

---

❓ Why can't I see the markers or blips?

• Draw Distance: Ensure you are close enough. Check Config.Visuals.drawDistance.
• Script Naming: Ensure the folder is named exactly esx_auto_repair. Renaming the folder can break internal references.
• Console Check: Look at your server console. If you see [esx_auto_repair] failed to load, a dependency is missing.

---

❓ The "E" interaction doesn't appear!

• Mechanic Logic: If Config.MechanicSettings.checkOnline is true, the markers will hide when real mechanics are available. Set this to false for testing.
• Vehicle Health: The script won't show the prompt if your car is already at 100.0% health.
• Job Whitelist: If you are in a job like 'Police', check if your job settings in Config.lua allow you to use the station.

---

❓ I'm getting a "Black Screen" or stuck in animation!

• Conflict: This usually happens if another script (like a seatbelt script) is trying to force the player to stay in the car while our script tries to pull them out.
• Fix: Set Config.Visuals.exitVehicle = false to see if the conflict resolves.

---

❓ Payment is failing!

• Account Names: Ensure your ESX accounts are named money and bank (default). If you use cash, update the server-side code.
• Insufficient Funds: The script checks both bank and cash. If both are empty, it will play an "Error" sound and cancel.

---

❌ Common Error Codes & Fixes

Error Message	Possible Cause	Solution
Attempt to index a nil value (field 'Framework')	Wrong folder name or ESX not loaded.	Ensure es_extended starts BEFORE this script.
No such export 'isBusy' in resource	Script hasn't started correctly.	Check for syntax errors in your Config.lua.
Invalid Vector3	Incorrect coordinates in config.	Ensure your coordinates are vector3(x, y, z) format.

---

💡 Still stuck?

If your problem persists, please follow these steps:

1. Open your F8 Console and look for red lines.
2. Check your Server Artifacts version (Recommended: 5848 or higher).
3. Open a GitHub Issue with a detailed description and screenshots.

---

Tip

Pro Tip: Using the /refresh and /restart esx_auto_repair commands is the fastest way to test your new configuration changes without restarting the whole server.