> For the complete documentation index, see [llms.txt](https://wiki.osro.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.osro.gg/oldschool-ro/server-information.md).
# Server Information
## **Relive the RO experience in a world where adventure awaits! Here's what you need to know about our server:**
***
**General Information:**
* **Pre Renewal - Episode 13.2**
* **Max Level: 255/100**
* **Max Stats:** 255
* **Max ASPD:** 196
* **Instant Cast (DEX):** 150
* **Max Guild Capacity:** 21
* **Max Character Slots:** 15
* **Max Party Members:** 21
* **Party Share Leve Gap:** 50
***
**Server Rates:**
* **Exp Rates:** 3000x
* **Drop Rates:** 1000x
* **Normal Card Drop Rate: 20%**
* **MVP Card Drop Rate: 5%**
* **Rare MVP Card Drop Rate: 1%**
***
**Party Modification:**
* **Max Party Members:** 21
* **Party Share Leve Gap:** 50
***
**Client Information:**
* **Max Client:** Unlimited
* **Mobile Client:** Android
* **Game Guard:** Gepard Shield 3.0, ADelays System
* **Server Host:** Tokyo Japan - Good for US and SEA players
* **DDoS Protected Dedicated Server**
***
**Server Features:**
* **Pre-Renewal Setting:** Immerse yourself in the classic pre-renewal Ragnarok Online experience, reliving the nostalgia of Rune Midgard as it was in its golden age.
* **War of Emperium (WoE):** Engage in epic guild battles every week during our scheduled War of Emperium events. Assemble your guild, conquer castles, and dominate the battlefield.
* **Custom Events:** Experience unique and exciting events designed to challenge and reward our players. From seasonal celebrations to custom quests, there's always something special happening in Oldschool RO.
* **Balanced Economy:** Our server is carefully balanced to provide a fair and enjoyable economy. Participate in trading, vending, and crafting to build your wealth.
* **Active GMs:** Our dedicated Game Masters are actively involved in the community. Reach out to them for assistance, report issues, or simply join in the fun during GM-hosted events.
***
**Additional Information:**
* **Server Location:** Tokyo, Japan
* **Anti-Cheat & Security:** Our server is equipped with robust anti-cheat measures to ensure fair gameplay. Your security is our priority.
* **Languages:** English is the primary language in global channels, fostering clear communication among players.
* **Discord Community:** Join our Discord server to connect with fellow players, get updates, and engage with the community.
***
**How to Join:**
1. [Download the client from our website.](https://osro.gg/download)
2. [Create an account and join the community.](https://osro.gg/register)
3. Follow our guides and tips to navigate your early steps.
4. Most importantly, have fun!
**Connect with Us!**
* **Website:**
* **Discord:**
* **Facebook:**
#### Stay Updated:
Stay tuned to our website and social media channels for the latest news, events, and updates. We look forward to seeing you in-game and hope you have a fantastic journey in Oldschool RO!
---
# 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.osro.gg/oldschool-ro/server-information.md?ask=&goal=
```
`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.