A loading screen for Qbox Project
Qbox is a modern QBCore fork with a cleaner resource layout, and it pairs well with a hosted loading screen: one line in server.cfg, nothing bundled into your repo, and no HTML to maintain alongside your ox-based stack.
- Resource folder
- [standalone]/ or resources/[qbx]/
- Framework dependency
- None
- Lines to add to server.cfg
- 1
Installing on Qbox Project
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 qbx_core ensure ls_yourserver
Worth knowing on Qbox
The resource does not import qbx_core or ox_lib, so it will never break when you update the Qbox stack.
Because the design lives on our side, the resource stays tiny and static — safe to commit once and forget, unlike a bundled HTML screen you would keep re-editing.
If your Qbox template shipped a loading screen resource, disable it in server.cfg before enabling this one.
Designs you can start from
All 20 designs run on Qbox — 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