❓FAQ & Troubleshooting

Common questions and fixes for known setup issues.

Q: I get a database error: Table 'fivem_db.owned_vehicles' doesn't exist. A: This happens if you are running a Standalone server but left the ESX config enabled. Go to your config.lua and change Config.AutomaticSave_owned = false. This tells the script to stop looking for ESX tables and use the custom rx56_permvehicles table instead.

Q: Do I need to manually import a .sql file when updating from 3.5 to 3.6? A: No. Version 3.6 includes an automatic database migration system. Just replace the old files with the new ones and start the server; the script will automatically update your columns and migrate old JSON data into the new structure.

Q: Vehicles are duplicating or exploding when spawning. A: Make sure you are using version 3.6 or higher. We completely rewrote the spawning logic and added an "Anti-Clone" lock (spawning = true) to prevent FiveM from creating multiple entities on the same tick during high server load.

Q: Can I use my own vehicle keys script? A: Yes! If you prefer to use a third-party script (like qb-vehiclekeys or wasabi_carlock), simply go to your config.lua and set Config.VehicleKeys.Enabled = false to disable our built-in system and prevent conflicts.