> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/entry-flow.md).

# Loading Screen

You can change various parts of the game loading including:

* Adding (skippable) splash images & videos
* Changing fade in timers and colours
* Other features configurable via live-config

## Loading Screen

Admins can edit the default loading screen via the [Settings](https://docs.otherside.xyz/platform-documentation/admins/settings.md#customization) section.

By default, when launching a client, users are met with this screen like this:

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-30909c24b91466365824c3c8bdad0ea9379bbe38%2Fimage%20(302).png?alt=media" alt=""><figcaption></figcaption></figure>

Splash image is determined by a hierarchy that can be modified either in your packaged editor, or from the dashboard itself. The way in which the image displayed is determined is as follows:

<table><thead><tr><th width="263">Image Type</th><th width="110">Priority</th><th>Where to edit (see examples below)</th></tr></thead><tbody><tr><td>World Image</td><td>1</td><td>Dashboard worlds tab</td></tr><tr><td>Mod Image</td><td>2</td><td>Dashboard mods tab</td></tr><tr><td>Map Image</td><td>3</td><td>Editor project settings -> M2 World Builder Data</td></tr><tr><td>Organisation Image</td><td>4</td><td>Dashboard settings tab (only with specific permissions)</td></tr></tbody></table>

1.

```
<figure><img src="../../.gitbook/assets/image (906).png" alt=""><figcaption></figcaption></figure>
```

2.

```
<figure><img src="../../.gitbook/assets/image (908).png" alt=""><figcaption></figcaption></figure>
```

3.

```
<figure><img src="../../.gitbook/assets/image (910).png" alt=""><figcaption></figcaption></figure>
```

4.

```
<figure><img src="../../.gitbook/assets/image (911).png" alt=""><figcaption></figcaption></figure>
```

## Live Config

There are some features that have been feature-flagged through live-config the list below will show you how to enable them and what they do.

* ShowOriginVersion (bool) - When logging entering an experience the origin version will be shown in the bottom right. **Default true.**
* SkipLegalScreens (bool) - At the beginning of the entry flow an Improbable branding / legal screen is displayed. This screen can be skipped. **Default false.**
* ShowNowEnteringText (bool) - When entering an experience a text appears saying "now entering {experience name} this text can be toggled on and off. **Default false.**
* SkipSignInConfirmationScreen (bool) - Right as the player loads the client we go through some sign in steps. Once the player signs in then a confirmation button is shown and a welcome message. This flag allows us to skip that step entirely and go straight into the experience. **Default true.**


---

# 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://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/entry-flow.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.
