Common Issues
HUD shows during character select
If you have
Config.TestMode
set totrue
in your config file, this starts the hud the second you join the server, not after your player loadsThis should only be enabled when testing config changes and you are going to be restarting the script while you're in the server
Once you're done with your config changes, make sure to turn this off
If using a Multicharacter script
Check your Multicharacter script to see if there's settings to enable/disable the hud
You can find the exports to use in the Exports page in these docs
Verify your script load order
Starting scripts in the wrong order could possibly cause this
Check out our First Steps guide if you haven't already (though you really should have) on how to set up the load order for Envi scripts
Check
[cfx-default]
folderThere's a script called
basic-gamemode
in the[gamemodes]
folder in hereOdds are you do not need this script as your framework should already handle player spawning, which
basic-gamemode
does as well, except it tries to force the player to spawn the second they load inThis can possibly cause conflicts where the event saying a player has spawned actually triggers before your framework has finished loading your character data
Most multicharacter scripts will be the ones to trigger the event saying the player has fully loaded once they've actually selected one of their characters to load in as
You can try deleting this script if you're comfortable doing so. If not then please leave it in!
ESX - Hunger / Thirst / Stress updates are slow
If you're using ESX and your Hunger, Thirst, or Stress statuses don't update very often (longer than 1 second between updates), check your esx_status
config. Envi-Bridge is what handles the status updates via the esx_status:onTick
event. The frequency of that event is controlled via the Config.TickTime
value. If you would like the status updates to become more frequent, reduce whatever number you have there. The default is 1000
, which is 1 thousand milliseconds.
Last updated