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

# Primeros pasos

Instalación, estructura de archivos y primeros pasos.

## Primeros pasos

### Instalación rápida

1. Compila el plugin.
2. Copia el `.jar` en `plugins/`.
3. Inicia el servidor una vez.
4. Ajusta `config/main.yml` y los archivos de `quests/`.
5. Reinicia para recargar caché y registros.

### Compatibilidad

* **Paper** para servidores Java.
* **Folia** para entornos con ejecución paralela.
* **Geyser + Floodgate + Cumulus** para Bedrock.

### Estructura de archivos

* `config/main.yml` — configuración principal.
* `quests/quests.yml` — quests base.
* `quests/rotation.yml` — rotación diaria y semanal.
* `quests/storylines.yml` — narrativa y decisiones.
* `lang/es.yml` y `lang/en.yml` — textos.

### Migración automática

El plugin mantiene compatibilidad con rutas antiguas.

* `config.yml` antiguo → `config/main.yml`
* `quests/config.yml` antiguo → `quests/quests.yml`
* `config.yml` se sincroniza para compatibilidad Bukkit.

### Comandos principales

* `/quests`
* `/quests top`
* `/quests search <texto>`
* `/quests shop`
* `/quests editor`

### Permisos

* `quests.admin` — acceso al editor.
* `quests.shop` — acceso a la tienda.

### Qué configurar primero

1. Define categorías y quests base.
2. Ajusta `rotation.daily` y `rotation.weekly`.
3. Configura `database` según tu escala.
4. Revisa `antiabuse`, `party` y `bonus`.
5. Activa `websocket` o `discord` si integras sistemas externos.

### Siguiente paso

Continúa con [Sistema de misiones](/documentation/quests/guia-de-administracion/sistema-de-misiones.md) para diseñar contenido, o con [Arquitectura](broken://spaces/oFc3uf3rR4WLlxYGj3mN/pages/rcDTrihTxjARdcMfrYbM) para entender el motor completo.


---

# 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://camiladev.gitbook.io/documentation/quests/primeros-pasos.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.