JJM Modifications

Troubleshooting

Solutions to common problems with JM-Pimping.

No Blips Appearing on the Map#

  • Confirm the resource started without errors in the server console.
  • Make sure ensure JM-Pimping is present in server.cfg and that QBCore fully loads before it.
  • Try restart JM-Pimping in the console and rejoin.
  • Check the F8 client console for any Lua errors on resource start.

Client NPC Won't Spawn#

  • Check if the selected ped model is in Config.BlacklistedPeds. Blacklisted models are skipped automatically — remove custom models from that list if they are safe on your server.
  • If you added an addon ped, make sure the model name in Config.ClientPeds exactly matches the in-game spawn name.
  • OneSync can cause certain emergency or cop peds to despawn immediately — keep those in Config.BlacklistedPeds.

Notifications Not Showing#

  • Run /testnotifs in-game to identify which notification systems are active.
  • If using "qb-phone" or "ox_lib", confirm those resources are started before JM-Pimping in server.cfg.
  • Check that the dependency lines in fxmanifest.lua are uncommented for the system you chose.
  • Switch to system = "chat" as a fallback — it requires no extra dependencies.

Database Errors / Table Doesn't Exist#

  • Re-import SQL/player_escort.sql and verify the import completed without errors.
  • Confirm oxmysql is started before JM-Pimping.
  • Verify the MySQL user has full privileges on the target database:
GRANT ALL PRIVILEGES ON database_name.* TO 'username'@'localhost';FLUSH PRIVILEGES;

Players Not Receiving Payment#

  • Check the server console for errors from the escort:completeContract event handler.
  • Confirm oxmysql is running and can reach the database — failed DB reads will prevent payments.
  • Make sure the player's citizenid is stored correctly in QBCore.

Resource Won't Start#

  • Verify qb-core, oxmysql, and qb-menu are all started and error-free before JM-Pimping.
  • Check fxmanifest.lua for any syntax issues if you edited it.
  • Look for specific Lua errors in the server console — they will point to the exact file and line number.

Version Check Warning at Startup#

This is a non-critical message. It means the resource could not reach the remote version endpoint — most commonly a firewall or outbound connectivity issue on the server machine. All gameplay features work normally regardless.

You can also manually trigger a version check from the server console:

checkjmpimpingupdates