triangle-exclamationCommon Errors

In this section, you will find answers to commonly encountered issues. Remember that most errors stem from incorrect configuration, lack of required resources, or insufficient modification.

Bear in mind that troubleshooting requires patience and precision. Try to carefully analyze the errors and systematically review possible solutions.

If the issue persists after verifying the configuration and available resources, please contact the support on the VMS Discord.


chevron-rightNo such export Notification in vms_notifyhashtag
  1. Go to vms_hud/config/config.lua file

  2. Find function Config.Notification

  3. Remove vms_notify exports and add your notify events or exports

chevron-rightStress is not working on my ESX server.hashtag

In that case, the problem is that the stress status is not registered in your esx_status & esx_basicneeds.

  1. Install prepared esx_status & esx_basicneeds - Prepared Resources

chevron-rightMy minimap is always large when I join the server.hashtag
  1. Try adding a new option to config.lua - Config.MapBigBypass = true

chevron-rightMy seat belts are not working properly.hashtag

If this is the case, we recommend that you make sure that you don't have another resource for seat belts, they may be implemented inside another script.

By default in ESX, the script responsible for seatbelts, among other things, is esx_cruisecontrol, if you have it on your server, remove it or disable it.

By default in QB-Core, inside the qb-smallresources resource, there is a seatbelts.lua file in the client file, if it is available, remove it.

chevron-rightHunger and Thirst are not working.hashtag

ESX:

If you have a problem displaying the status of food, drink, it means that you don't have esx_status & esx_basicneeds installed or they are not working properly, in that case, go to Prepared Resources and download our esx_status and esx_basicneeds.

QB-Core:

This means that you have not configured Config.Core and Config.CoreExport

chevron-rightMy status bars go beyond the limit.hashtag

This means that your status system has no limit.

A solution for QB-Core users:

  1. Go to qb-smallresources/server/consumables.lua

  2. Find event consumables:server:addThirst

  3. Replace the event with the following:

  1. Go to qb-smallresources/server/consumables.lua

  2. Find event consumables:server:addHunger

  3. Replace the event with the following:

Last updated