Documentation
Designing your loading screen in game: the creator, the 19 modules, and how the screen decides when to go away.
Everything happens in the creator. Type /loadingcreator, design the screen by dragging modules onto a 1920 × 1080 canvas, add music and video, hit Go live — and the next player who joins already sees it.
No resource restart. No config file to touch.
Two tabs, same style as the rest of the Quasar creators.
Design
The editor itself, laid out like a classic graphics editor:
Area | What it does |
|---|---|
Left |
Theme library. The 3 built-in ones, yours, and which one is live
Center | Toolbar + canvas with dragging, resize handles, grid and safe area |
Top right | Module stack: visibility, lock, order, duplicate, rename (double click) |
Bottom right | Inspector with the selected module's properties, or the canvas's own if nothing is selected |
Shortcuts
Shortcut | What it does |
|---|---|
| Undo and redo — one step per gesture, not per keypress |
| Duplicate the selected module |
| Delete it |
Arrow keys | Move by 0.1% · with |
| Snaps to 1% steps |
Preview
The Preview button opens the screen at full size, with the animations running and the music actually playing.
It is the same renderer the game uses, so what you see there is exactly what players will see.
The canvas draws videos as a thumbnail, not as a player. A video playing underneath the modules you are dragging helps nobody. Composition and framing are identical — use Preview to see it in motion.
Deselect everything (click on empty canvas) and the inspector switches to what belongs to the whole loading screen.
Section | What it holds |
|---|---|
Canvas | Reference resolution, 1920 × 1080 by default |
Background | Color/gradient, image, carousel or video file (WebM/VP9) |
Soundtrack | A playlist from |
Master Mute
The Sound button module mutes the background video and the soundtrack at once, and the player's choice is remembered for the next login.
There is no YouTube integration. An embed will not start from a
cfx-nui-*origin, so it would never play in game.
The second tab holds what a single module cannot decide:
Minimum time on screen
Fade out
Server identity — the name, Discord and website that the bound modules print
Leave the name empty and sv_hostname is used. Players online and slots always come from the server.
19 types, inspired by the most widely used loading screens.
Group | Modules |
|---|---|
Basics | text, image, shape, icon, effect |
Loading | progress bar, spinner, server info, clock |
Content | tips, news, rules, staff, social media, countdown |
Media | music player, sound button, carousel, video |
What They All Share
Every module has the same base:
Position and size in percentages, rotation, opacity, blend mode, corner radius
Entrance animation — 10 types, with delay and duration
Loop motion — float, sway, pulse, spin, blink, glitch… each with its own cycle and delay, so the screen does not freeze once everything has entered
An optional background panel with fill, border, shadow, blur and padding
Worth Knowing
Text can be bound to live data: server name, players online, slots, load percentage, status line, date, time, Discord or website. Or fixed text, with prefix and suffix.
Text can also draw itself by hand — enable Handwriting and the word is traced as if being written, then filled in. Works well with a script font like Pacifico.
Progress bar reads the game's real progress. It is smoothed and creeps forward slowly in the background, so it never looks frozen. Six styles: bar, thin line, neon rail, segmented, dots and ring.
Sound button controls the master mute — background video and soundtrack at once. The player's choice is saved.
Music player only draws: playback lives in a single shared engine, so switching styles does not restart the song.
Modules are scaled to fit. The background is scaled to cover. Two different scales, on purpose:
If everything were scaled to cover, on a non-16:9 screen anything pinned to an edge would be lost — the news panel on the right, the title on the left.
If everything were scaled to fit, you would get black bars around the background.
On 16:9, which is what almost everyone has, both scales match and nothing changes.
The resource decides when the screen closes, and every path ends up closing it:
Waits for the session to start and for the ped to exist.
Respects the theme's minimum time.
If the theme asks for it, waits for the key press.
Fade out and close.
Config.MaxDuration is a hard ceiling over all of the above, and stopping the resource also closes the screen.
Nobody gets stuck.
What | Where |
|---|---|
The 3 built-in themes | Inside the UI, so the screen draws something correct before it has talked to anyone |
The themes you create |
|
The last theme a player saw | Cached, so a cust |
