> For the complete documentation index, see [llms.txt](https://dark-elf-online.gitbook.io/dark-elf-online-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dark-elf-online.gitbook.io/dark-elf-online-docs/town-and-island/features/town_relations.md).

# Town Relations

Buy the blessing of a town: a 2-hour buff that works on every map, with a ladder of the biggest buyers.

## Quick Guide

* Talk to a Town Relations NPC in Elf Island or in one of the ten other towns. Every NPC sells every town's blessing.
* Pick **Purchase Buff**, choose a town and confirm.
* You pay 20,000,000 Zeny and get that town's blessing for 2 hours. A status icon shows the time left.
* **View Ladder** shows the top 10 buyers of the day, week, month, quarter or year. **My Stats** shows your own count and rank on each ladder and your active blessing.

**Note:** One blessing at a time. You cannot buy another until the current one runs out. The blessing survives warps and relogs.

## The Blessings

Every blessing gives **All Stats +5** and **+10% drop rate from all monsters**, plus one town perk.

| Town      | Perk                                |
| --------- | ----------------------------------- |
| Prontera  | DEF +15, MDEF +15                   |
| Izlude    | 10% less damage from ranged attacks |
| Alberta   | Melee physical damage +10%          |
| Morroc    | Critical damage +10%                |
| Geffen    | MATK +10%                           |
| Aldebaran | 10% less damage from melee attacks  |
| Payon     | Ranged physical damage +10%         |
| Comodo    | ATK +10%                            |
| Juno      | 10% less damage from magic          |
| Lutie     | After-cast delay -10%               |
| Hugel     | 10% less damage from Boss monsters  |

## Purchase Ladder

Every purchase adds 1 to your count on five ladders at once. Each ladder shows its top 10 and starts over when its period ends.

| Ladder    | Period                                |
| --------- | ------------------------------------- |
| Daily     | One server day, from midnight         |
| Weekly    | Monday to Sunday                      |
| Monthly   | The calendar month                    |
| Quarterly | From January, April, July and October |
| Yearly    | The calendar year                     |

The ladders are for bragging rights. There is no prize.

## Where To Find It

| Town       | Location            |
| ---------- | ------------------- |
| Elf Island | `mainprt 215 180`   |
| Prontera   | `prontera 200 166`  |
| Izlude     | `izlude 121 99`     |
| Alberta    | `alberta 124 55`    |
| Morroc     | `morocc 151 93`     |
| Geffen     | `geffen 128 59`     |
| Aldebaran  | `aldebaran 128 118` |
| Payon      | `payon 179 231`     |
| Comodo     | `comodo 217 151`    |
| Juno       | `yuno 167 183`      |
| Lutie      | `xmas 158 127`      |
| Hugel      | `hugel 91 138`      |


---

# 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://dark-elf-online.gitbook.io/dark-elf-online-docs/town-and-island/features/town_relations.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.