> 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/installation.md).

# Installation

1. Download `daddy-loading` (escrow edition from your [Keymaster](https://keymaster.fivem.net), open source edition from your Tebex purchase) and put the folder in your `resources` folder. Do not rename it.
2. Add it to your `server.cfg` and give your admins access to the editor:

```cfg
ensure daddy-loading
add_ace group.admin command.loadingedit allow
```

3. Restart the server. Players see the new loading screen the next time they connect.
4. Join the server and type `/loadingedit`. Change the server name, logo and the rest from the [editor](/daddy-studios-docs/scripts/daddy-loading/editor.md).

{% hint style="info" %}
The loading screen only loads at connection time. After you change something in the editor, reconnect to see the result on the real loading screen. The editor has its own live preview.
{% endhint %}

## The loading screen does not close

The screen stays until a script calls `ShutdownLoadingScreenNui()`. Framework spawn scripts do this (Qbox does). If yours does not, the resource closes the screen by itself 60 seconds after the player is active. Change the delay with a convar, `0` turns it off:

```cfg
setr daddy_loading_autoclose 60
```


---

# 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/installation.md?ask=<question>&goal=<user_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.