> For the complete documentation index, see [llms.txt](https://wiki.aero-revolution.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.aero-revolution.com/server-information.md).

# Server Information

AeRO's rates, caps, and core settings at a glance.

Everything you need to know about how AeRO plays, pulled straight from the server configuration.

{% hint style="info" %}
AeRO is a **high-rate pre-renewal** server. The numbers below are the live server settings.
{% endhint %}

### ℹ️ General server details

| Setting              | Value                                     |
| -------------------- | ----------------------------------------- |
| Server Type          | Pre-renewal                               |
| Max Base / Job Level | 255 / 100                                 |
| Max Stats            | 255 (all classes, including Trans & Baby) |
| Max ASPD             | 195                                       |
| Max SP               | 4,500                                     |

### ⚡ Rates

| Type      | Rate   |
| --------- | ------ |
| Base EXP  | 5,000x |
| Job EXP   | 5,000x |
| MVP EXP   | 1x     |
| Quest EXP | 1x     |

### ⚡ Drop rates

| Type                             | Rate              |
| -------------------------------- | ----------------- |
| Common items                     | 1x                |
| Healing items                    | 1x                |
| Usable items                     | 1x                |
| Equipment                        | 1% (set per-item) |
| Cards (normal / mini-boss / MVP) | 1%                |

{% hint style="info" %}
Rare Boss cards keep their own custom rates. MVP card drops are **broadcast server-wide** when they drop (without showing the drop chance). A maximum of **2 Deadly cards** can be equipped at once.
{% endhint %}

### 🪙 Economy

| Setting                                   | Value                            |
| ----------------------------------------- | -------------------------------- |
| Zeny tax (trade / vending / buying store) | 10%                              |
| Mailing zeny (RODEX)                      | Disabled                         |
| NPC sell price cut (above 500z)           | −85%                             |
| NPC sell price cut (500z or below)        | −70%                             |
| Vending currency                          | Zeny or Pods (Proof of Donation) |

### 👥 Party system

| Setting              | Value |
| -------------------- | ----- |
| Max party size       | 12    |
| Share level range    | 15    |
| Even-share EXP bonus | None  |

### 🛡️ Guild system

| Setting           | Value                                                  |
| ----------------- | ------------------------------------------------------ |
| Max guild members | 76                                                     |
| Max alliances     | 3                                                      |
| Guild EXP source  | Guild Contribution NPC only (no natural guild tax EXP) |

{% hint style="success" %}
Looking for how refining, skills, and MvPs differ from standard pre-renewal? See **Server Modifications**.
{% 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://wiki.aero-revolution.com/server-information.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.