> For the complete documentation index, see [llms.txt](https://wiki.qfdevelopers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.qfdevelopers.com/scripts/editor-1/additional-informations.md).

# Additional Informations

Page dedicated to Additional Informations about our Loading Screen

#### Core Features

* **Component Modularity:** Toggle every single UI element on or off via `Config.Components` (Logo, Hotkeys, Audio Player, Staff Showcase, FAQ, etc.).
* **Dynamic Announcements:** Inform players about updates, sales, or events directly on the loading screen using the rich announcement cards.
* **Interactive UI:** Players can browse images, read FAQs, and control the music volume while waiting for the game engine to initialize.

#### Developer API (Natives & Loading Control)

While loading screens operate primarily in a NUI (browser) context separate from the main game loop, there are times when custom server frameworks need to manually control when the loadscreen disappears.

{% hint style="info" %}
**Manual Shutdown:** If your `fxmanifest.lua` has `loadscreen_manual_shutdown 'yes'` enabled, the loadscreen will stay open indefinitely until you explicitly close it. This is useful for keeping the loading screen active while custom character selectors or login scripts load assets.
{% endhint %}

To terminate the loading screen from another client resource (such as your spawning, login, or multicharacter script), you should call the standard FiveM client natives:

```lua
-- CLIENT-SIDE
-- Call this once the player character is fully loaded, spawned, and ready to play.
RegisterNetEvent('myFramework:playerFullyLoaded', function()
    -- Perform custom camera movements, ped spawning, etc.
    DoScreenFadeOut(0)
    
    -- Terminate the loading screen UI and native game overlay
    ShutdownLoadingScreen()
    ShutdownLoadingScreenNui()
    
    -- Fade the game back in smoothly
    Wait(1000)
    DoScreenFadeIn(1000)
end)
```

#### Frequently Asked Questions (Q\&A)

**Q: How do I change the icons used in the menu?**\
A: The script utilizes the Iconify framework. You can search for thousands of free icons at [Iconify Design](https://icon-sets.iconify.design/). Simply copy the icon identifier (e.g., `lucide:home`) and paste it into your `Config.Icons`.

**Q: Why isn't the music playing automatically when I join?**\
A: Modern web browsers (including the Chromium Embedded Framework used by FiveM) enforce strict autoplay policies to prevent unwanted audio. Audio will only begin playing once the user interacts with the screen (e.g., clicking anywhere, pressing a hotkey).

**Q: How do I use local files instead of web URLs?**\
A: Place your media files inside the `web/dist` folder (we recommend creating an `assets` subfolder). You can then reference them using relative paths in your config: `"assets/background1.jpg"`.


---

# 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://wiki.qfdevelopers.com/scripts/editor-1/additional-informations.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.