> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-loading/troubleshooting.md). # Troubleshooting ## The loading screen does not close A script has to call `ShutdownLoadingScreenNui()`. Framework spawn scripts do this. If yours does not, the resource closes the screen 60 seconds after the player is active. Set another delay with `setr daddy_loading_autoclose 20` in your `server.cfg`, or `0` to turn the safety net off. ## `/loadingedit` does nothing Your account is missing the permission. Add it in `server.cfg` and restart the server: ```cfg add_ace group.admin command.loadingedit allow ``` ## My changes do not show on the loading screen The loading screen only loads at connection time. Reconnect to the server. If it still shows the old look, check that the editor showed that the save worked. ## The editor says the save failed * The config is larger than 512 KB or has a wrong shape, reload the editor and try again * A video or music path is not a local `.mp4`, `.webm` or `.mp3` file inside the resource * The server cannot write `config.json`, check the folder permissions ## The Discord name and avatar are missing * `Config.DiscordBotToken` is empty or wrong * The player does not have the Discord app open, FiveM then has no Discord identifier * Set `Config.Debug = true` and read the server console for the answer of Discord ## The video does not play Use an H.264 `.mp4` or a `.webm`, and check the path in the editor. Large videos make the resource download slower for every new player, keep them small. ## The music does not start Browsers block sound until the first click. Players click the prompt on the screen. Check the track paths and that the files are `.mp3`. ## Texts are in the wrong language Set `Config.Language` in `config.lua` and restart the resource. Texts you typed in the editor are not translated. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-loading/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.