> For the complete documentation index, see [llms.txt](https://wiki.frontierro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.frontierro.com/ro-project-frontier/server-modifications/drop-adjustment.md).

# Drop Adjustment

{% hint style="info" %}
📉 **Drop rates have been re-tuned.** Select items — mostly high-tier and heavily-used gear — had their drop chances adjusted to keep the market stable and progression meaningful.
{% endhint %}

Most common and low-tier items are left untouched. The aim isn't to make the game grindier — it's to protect the value of what's genuinely rare.

***

## 🔍 Check Any Drop Rate Yourself

{% hint style="success" %}
⌨️ Type **`@mi <monster>`** in-game to instantly see a monster's current drop rates.
{% endhint %}

Because so many items were tuned, there's no manual changelog to fall out of date — the **`@mi`** command is always the live, accurate source. No guesswork, no stale tables.

***

## 🎯 Why Drops Were Adjusted

<details>

<summary>💠 Rare stays rare</summary>

Curbing overabundance keeps top-tier gear worth the hunt.

</details>

<details>

<summary>🎉 Rewards feel earned</summary>

Landing a great drop should feel like a moment — not a routine.

</details>

<details>

<summary>🔁 Trade thrives</summary>

A balanced supply pushes players toward trading, vending, and teaming up.

</details>

<details>

<summary>📊 Economy stays healthy</summary>

Steady drop flow protects item prices and the server's long-term economy.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.frontierro.com/ro-project-frontier/server-modifications/drop-adjustment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.