the scripts are starting in the wrong order, because the user scripts should start after the server.cfg configuration.
it’s wrong, and some frameworks are not working that way.
A framework called ESX, MUST start after something called spawnmanager.
if we take a look at the file
server.cfg then its clear because all the scripts are starting before the main lines, witch are required to make things work.
#Lines below this point are controlled by AMP. # -- server.cfg sets PoweredBy "AMP by CubeCoders - https://cubecoders.com/AMP" set udpLogAddress 127.0.0.1:43600 sets tags "default" sv_scriptHookAllowed 1 endpoint_add_tcp "0.0.0.0:30120" endpoint_add_udp "0.0.0.0:30120" rcon_password ensure AMPFiveMIntegrationServer stop webadmin ensure mapmanager ensure chat ensure spawnmanager ensure sessionmanager ensure fivem ensure hardcap ensure rconlog ensure scoreboard sv_endpointprivacy True sv_maxclients 512 sv_hostname "IMS - FiveM | Andrada City" sv_licenseKey "" set steam_webApiKey "" sets banner_connecting "IMS-FiveM+Background.png" sets banner_detail "IMS-FiveM+Background.png" load_server_icon "FiveM-Discord-IMS.png"
sets PoweredBy "AMP by CubeCoders - https://cubecoders.com/AMP"
can’t be changed…
ALL SCRIPTS IN FIVEM MUST START AFTER THAT SECTION
It’s simple, the
user.cfg file should output all the contents to the bottom of the config
ESX fixed the issue on their side, now it works with AMP.