Grand opening25% off everything with FAM-261023-261025-UL4B9this weekendAdded for you at checkout Halloween Edition36 maps, limited runlimited runShop the drop
qbx_core · Qbox

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

01Design the screen

Pick one of the templates, drag the widgets you want onto the canvas and set the server name, palette and rules.

02Export the resource

Download the generated resource folder. It holds an fxmanifest and a small data file, with no HTML to maintain on your side.

03Drop it into resources/

Any resource folder works. The resource is standalone, so load order and framework version do not matter.

04Add one line to server.cfg

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

Standalone — no qbx_core needed

The resource does not import qbx_core or ox_lib, so it will never break when you update the Qbox stack.

Keep it out of your git submodules

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.

One loadscreen rule still applies

If your Qbox template shipped a loading screen resource, disable it in server.cfg before enabling this one.