A loading screen for ESX Legacy
ESX servers typically run esx_loadingscreen or a bundled HTML screen that has to be edited by hand. Ours is a drag-and-drop replacement hosted for you — change the server name, rules or background whenever you like and every player sees it on their next connect.
- Resource folder
- [esx]/ or resources/[standalone]/
- Framework dependency
- None
- Lines to add to server.cfg
- 1
Installing on ESX Legacy
Pick one of the templates, drag the widgets you want onto the canvas and set the server name, palette and rules.
Download the generated resource folder. It holds an fxmanifest and a small data file, with no HTML to maintain on your side.
Any resource folder works. The resource is standalone, so load order and framework version do not matter.
Add the ensure line, remove the ensure line of the loading screen you were using before, and restart the server.
# server.cfg # switch the old one off first: # ensure es_extended ensure ls_yourserver
Worth knowing on ESX
Only one loadscreen resource can be active. Remove or comment out the esx_loadingscreen ensure line in server.cfg first — running both leaves players on a black screen.
The exported resource is standalone. It does not require es_extended, so it starts before your framework and shows immediately while the rest of the server boots.
Nothing in the resource touches ESX internals — it only uses the FiveM loadscreen directive, which is identical across ESX versions.
Designs you can start from
All 20 designs run on ESX — they are designs, with no framework code in them. Three of them, rendered live:
- Aurora hunt convoy
- in 2 days
- Fjord market day
- in 5 days
- 1NightRider
- 184h
- 2PixelKing
- 156h
- 3GhostRP
- 142h
- 4Vortex
- 121h
- Omertà above all — no out-of-character snitching
- Respect the chain of command
- Business stays in the family
- Disputes settled by the Don, not in the streets