The resource is not started. Check that ensure qs-loadingscreen is in server.cfg, that the folder is named exactly qs-loadingscreen, and that the server console shows no error for it on start. Another resource that declares a loading screen also takes its place — remove it.

Neither route matched. Check the ACE line (add_ace group.admin command.loadingcreator allow) and that your identifier is in that group, or that your framework group is in Config.Creator.adminGroups.

The answer is remembered for the session: after fixing it, reconnect before trying again.

The interface had not finished loading when the command ran — common in the first seconds after joining. Wait a moment and run /loadingcreator again. If it never opens, look in the F8 console for an error from qs-loadingscreen: the creator releases the mouse on its own when its window fails to appear.

Nothing closed it, so it waited for the safety ceiling — Config.MaxDuration (45 s) after the player spawns, or Config.MaxDurationHandoff (3 min) while Multicharacter is running. The client console prints loading screen safety timeout (… ms), forcing close when this happens.

Make your multicharacter or spawn script call exports['qs-loadingscreen']:CloseLoadingScreen() when it is ready, or lower the ceiling. See Integrations.

The ceiling ran out before the next screen was ready — usually a slow PC with a multicharacter that is not in Config.HandoffResources. Add your multicharacter to that list so it gets the three-minute ceiling, and make sure it closes the screen itself.

The theme is saved but not live. Press Set live — the theme list shows a Live badge on the one players get.

If it already is, read the server console on start. data/themes.json is corrupt, starting from scratch means the file was edited by hand into invalid JSON: restore it from a backup before saving anything, or the next save replaces it.

The clip is an .mp4. The FiveM browser cannot play H.264, so convert it to WebM (VP9) and put it in videos/. The creator marks .mp4 files as will not play.

Correct behaviour. PCs with four CPU cores or fewer, or 4 GB of memory or less, get the clip held on its first frame so the game loads faster. See Performance on Slow PCs.

Check that the soundtrack is switched on and has tracks, and that each track points at a file that still exists in song/. Then check the player has not muted it: the Sound toggle is remembered between joins, so a player who muted once keeps it muted until they press it again.

The name comes from sv_hostname with its colour codes removed, unless the theme's Settings tab overrides it. Players online and slots come from the server — slots from sv_maxclients — and refresh every ten seconds.

The folders are read when the resource starts: run restart qs-loadingscreen after adding files. Then check:

• The extension is one the resource serves — song/ mp3, ogg, wav, m4a · videos/ webm, mp4 · images/ png, jpg, jpeg, webp, gif.

• The images/ folder exists — it does not ship with the resource.

• The server console does not say could not read song/ (io.readdir is missing…). If it does, your server artifacts are too old to list folders — update them.

The server refused it. The usual reasons: 50 themes are already saved (limit_reached — delete one or raise Config.MaxThemes), the theme is over 512 KB (too_large), or the server cannot write data/themes.json (write_failed — a read-only file or host). The full list is under Error Codes below.

The code points at files that are not on this server. Copy the same files into song/, videos/ or images/ and restart the resource, or pick a replacement in each dropdown.

The code was cut short or changed on the way. Codes start with QSLS1: and are one long line — copy the whole box again with Ctrl + A, Ctrl + C, and avoid apps that shorten long messages.

Correct behaviour. A built-in theme you have never saved lives inside the interface and cannot be deleted. Once you save changes to one, Delete removes your version and brings the original back.

The resource is not started. Check that ensure qs-loadingscreen is in server.cfg, that the folder is named exactly qs-loadingscreen, and that the server console shows no error for it on start. Another resource that declares a loading screen also takes its place — remove it.

Neither route matched. Check the ACE line (add_ace group.admin command.loadingcreator allow) and that your identifier is in that group, or that your framework group is in Config.Creator.adminGroups.

The answer is remembered for the session: after fixing it, reconnect before trying again.

The interface had not finished loading when the command ran — common in the first seconds after joining. Wait a moment and run /loadingcreator again. If it never opens, look in the F8 console for an error from qs-loadingscreen: the creator releases the mouse on its own when its window fails to appear.

Nothing closed it, so it waited for the safety ceiling — Config.MaxDuration (45 s) after the player spawns, or Config.MaxDurationHandoff (3 min) while Multicharacter is running. The client console prints loading screen safety timeout (… ms), forcing close when this happens.

Make your multicharacter or spawn script call exports['qs-loadingscreen']:CloseLoadingScreen() when it is ready, or lower the ceiling. See Integrations.

The ceiling ran out before the next screen was ready — usually a slow PC with a multicharacter that is not in Config.HandoffResources. Add your multicharacter to that list so it gets the three-minute ceiling, and make sure it closes the screen itself.

The theme is saved but not live. Press Set live — the theme list shows a Live badge on the one players get.

If it already is, read the server console on start. data/themes.json is corrupt, starting from scratch means the file was edited by hand into invalid JSON: restore it from a backup before saving anything, or the next save replaces it.

The clip is an .mp4. The FiveM browser cannot play H.264, so convert it to WebM (VP9) and put it in videos/. The creator marks .mp4 files as will not play.

Correct behaviour. PCs with four CPU cores or fewer, or 4 GB of memory or less, get the clip held on its first frame so the game loads faster. See Performance on Slow PCs.

Check that the soundtrack is switched on and has tracks, and that each track points at a file that still exists in song/. Then check the player has not muted it: the Sound toggle is remembered between joins, so a player who muted once keeps it muted until they press it again.

The name comes from sv_hostname with its colour codes removed, unless the theme's Settings tab overrides it. Players online and slots come from the server — slots from sv_maxclients — and refresh every ten seconds.

The folders are read when the resource starts: run restart qs-loadingscreen after adding files. Then check:

• The extension is one the resource serves — song/ mp3, ogg, wav, m4a · videos/ webm, mp4 · images/ png, jpg, jpeg, webp, gif.

• The images/ folder exists — it does not ship with the resource.

• The server console does not say could not read song/ (io.readdir is missing…). If it does, your server artifacts are too old to list folders — update them.

The server refused it. The usual reasons: 50 themes are already saved (limit_reached — delete one or raise Config.MaxThemes), the theme is over 512 KB (too_large), or the server cannot write data/themes.json (write_failed — a read-only file or host). The full list is under Error Codes below.

The code points at files that are not on this server. Copy the same files into song/, videos/ or images/ and restart the resource, or pick a replacement in each dropdown.

The code was cut short or changed on the way. Codes start with QSLS1: and are one long line — copy the whole box again with Ctrl + A, Ctrl + C, and avoid apps that shorten long messages.

Correct behaviour. A built-in theme you have never saved lives inside the interface and cannot be deleted. Once you save changes to one, Delete removes your version and brings the original back.