> 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/guides/guides.md).

# Guides

The rest of this documentation explains **how each system works**. These guides explain **how to use them together** to build a server that players enjoy, come back to, and support financially over the long term.

They are opinionated, practical playbooks. Every feature they mention links to its reference page, so you can go from a strategy straight to the setting that implements it.

## Available guides

| Guide                                                                     | Read it when you want to                                                                                                                                                        |
| ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Profitable server methodology](/guides/profitable-server-methodology.md) | Plan the whole life of your server: positioning, launch, acquisition, retention, monetization, economy health, operations and the numbers to watch.                             |
| [Multi-platform playbook](/guides/multiplatform-playbook.md)              | Get the most out of each platform (Windows, Android, iPhone and iPad, macOS, web browser and mobile browser) and promote each one to the right audience.                        |
| [Monetization catalog blueprint](/guides/monetization-catalog.md)         | Build a fair, ready-to-adapt store: product categories, illustrative price ladders, bundles, limited-time offers, what not to sell, and where to set each item up in the panel. |

## Suggested reading order

{% stepper %}
{% step %}

### Start with the methodology

Read the [Profitable server methodology](/guides/profitable-server-methodology.md) end to end once. It gives you the phases and the vocabulary the other two guides use.
{% endstep %}

{% step %}

### Pick your platform focus

Use the [Multi-platform playbook](/guides/multiplatform-playbook.md) to decide which platforms you will promote first, based on the audience you chose.
{% endstep %}

{% step %}

### Design the store last

Build your catalog with the [Monetization catalog blueprint](/guides/monetization-catalog.md) only after positioning and economy are decided. A store designed before the economy almost always ends up selling power.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
All numbers in these guides (prices, rates, percentages, targets) are **illustrative examples** to show the reasoning. They are not promises of results, and every community is different. Test, measure and adjust for your own players.
{% endhint %}


---

# 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/guides/guides.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.