> For the complete documentation index, see [llms.txt](https://wiki.ragnacore.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.ragnacore.net/introduction/about-us.md). # About Us RagnaCore is a Pre-Renewal high-rate Ragnarok Online server built around farming, progression, competition, and community. Our team is focused on creating a stable, secure, and rewarding environment for all types of players—from casual adventurers and dedicated farmers to MVP hunters, PvP competitors, and organized guilds. We carefully develop and improve our systems to provide: * Rewarding long-term progression * Balanced farming and competitive gameplay * Fair opportunities for every player * Active development and regular improvements * Strong anti-cheat and server security * Clear communication and full transparency * Responsive support from the management team We understand that a strong server is built through trust, consistency, and accountability. Our team is committed to openly communicating important changes, addressing community concerns, and continuously working toward a better gaming experience. Whether your goal is to become stronger, build your guild, dominate the battlefield, earn through farming, or simply enjoy the classic Ragnarok experience, RagnaCore is built to give your journey purpose. --- # 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.ragnacore.net/introduction/about-us.md?ask=&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.