> For the complete documentation index, see [llms.txt](https://juguitostudio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://juguitostudio.gitbook.io/docs/js_loadingscreen/installation.md).

# Instalación

Sigue estos sencillos pasos para instalar y verificar **js\_loadingscreen** en tu servidor FiveM.

***

## 1. Requisitos

* Servidor FiveM con Artifact **7290 o superior**.
* No requiere base de datos MySQL.
* Compatible con cualquier framework (ESX, QB-Core, QBX o Standalone).

***

## 2. Paso a Paso

### Paso 1: Colocar la carpeta

Copia la carpeta `js_loadingscreen` dentro del directorio `resources/` de tu servidor:

```
📂 resources/
└── 📂 [juguito]/
    └── 📂 js_loadingscreen/
```

### Paso 2: Agregar a `server.cfg`

Añade la siguiente línea en tu archivo `server.cfg`:

```cfg
ensure js_loadingscreen
```

> 💡 **Tip:** Asegúrate de iniciarlo antes de los scripts de framework para que la pantalla de carga tome efecto de inmediato mientras los recursos se descargan.

### Paso 3: Configurar

Abre `config.lua` y `web/config.js` para personalizar:

* El nombre y eslogan de tu servidor.
* El ID del vídeo de YouTube o imágenes de fondo.
* Enlaces de Discord, Tienda y Web.
* Lista de canciones de música de fondo.
* Reglas, miembros del Staff y teclas de rol.

***

## 3. Verificación en Consola

Al iniciar el servidor en la consola verás la línea de confirmación:

```
[JuguitoStudio] Loading Screen v1.0.0 — Loaded OK [framework: auto]
```

Si ves ese mensaje, la pantalla de carga está lista y operativa.


---

# 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://juguitostudio.gitbook.io/docs/js_loadingscreen/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.