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

# Morpheus Emulator

Welcome to the official documentation of **Morpheus Emulator** — a complete MU Online server with 40+ custom systems, 32 events, cross-platform play (Windows, Android, iPhone/iPad, macOS and the browser) and a web control panel that lets you run everything without touching the machine.

{% hint style="info" %}
New here? Start with [Getting started](/getting-started.md). It takes you from your first sign-in to your first configuration change and your first event in a few minutes.
{% endhint %}

## What you will find here

| Section                                     | What it covers                                                                        |
| ------------------------------------------- | ------------------------------------------------------------------------------------- |
| [Getting started](/getting-started.md)      | What is in the package and your first steps                                           |
| [Feature overview](/features.md)            | Everything Morpheus Emulator delivers                                                 |
| [Videos](/videos.md)                        | Previews of the panel and the game on every platform                                  |
| [Changelog](/changelog.md)                  | Main customs, features and the version history                                        |
| [Tutorials](/tutorials/tutorials.md)        | Step-by-step: EventItemBag, custom items, maps, wings and pets                        |
| [Guides](/guides/guides.md)                 | Profitable server methodology, multi-platform playbook and monetization catalog       |
| [Dashboard](/dashboard/dashboard.md)        | How to use every screen of the control panel and its visual editors                   |
| [MuServer](/muserver/muserver.md)           | How to configure every server, every file and every setting, with syntax and examples |
| [Events](/events/events.md)                 | All classic and custom events: enabling, scheduling and rewards                       |
| [Customs](/customs/customs.md)              | Every custom system and how to configure it                                           |
| [Client customs](/client/client.md)         | Client-side customs, managed in the Client Hub and published to players               |
| [Troubleshooting](/help/troubleshooting.md) | Common problems and how to fix them                                                   |

## How to read the configuration pages

Every configuration page follows the same structure:

1. **What it does** — the feature from the player's point of view.
2. **Where it lives** — the file and the switch that enables it.
3. **Syntax** — every column or key, with its values and meaning.
4. **Example** — real lines taken from the shipped files.
5. **Pitfalls** — the mistakes that make the server ignore a file or behave unexpectedly.
6. **Reload** — how to apply the change without restarting the server.

{% hint style="warning" %}
Before editing any server file, read [File format basics](/muserver/file-format-basics.md). A missing `end` line or a wrong number of columns is the most common reason a change "does nothing".
{% endhint %}

## Quick links

* [Hot reload: which module reloads which file](/dashboard/services-and-reload.md)
* [GameServerInfo - Common (main server settings)](/muserver/gameserver/common.md)
* [EventItemBag — boxes, boss drops and event rewards](/game-data/event-item-bag.md)
* [Chat commands](/game-data/commands.md)
* [Visual editors in the panel](/dashboard/editors.md)


---

# 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.morpheusemulator.com.br/readme.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.