> For the complete documentation index, see [llms.txt](https://siege-of-midgard-ro.gitbook.io/wiki-smro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://siege-of-midgard-ro.gitbook.io/wiki-smro/events/woe-guide.md). # WoE Guide The **War of Emperium (WoE)** is one of the most important competitive features in Siege of Midgard RO. It is a guild-based event where players fight for castle ownership, defend territory, and prove their strength through teamwork, preparation, and strategy. For many players, WoE is one of the biggest long-term goals on the server. ### What WoE Is WoE is a large-scale guild battle where players enter castles and fight for control of the **Emperium**. The main objective is simple: * break the Emperium in the target castle * take ownership of the castle * defend it from other guilds until the event ends While the goal sounds simple, WoE is one of the most demanding and competitive parts of Ragnarok gameplay. ### Why WoE Matters WoE matters because it gives players a reason to build strong characters, join guilds, and work as a team. It adds value to the server by creating: * guild competition * organized team play * castle control goals * prestige and recognition * long-term PvP motivation * reasons to improve gear, builds, and coordination WoE is not only about individual strength. It is about group performance. ### Who WoE Is For WoE is best suited for players who enjoy: * guild-based content * organized PvP * teamwork and strategy * competitive progression * support and front-line roles * coordinated attacks and defenses Even players who are not top damage dealers can still be valuable in WoE if they fill the right role. ### Why Guilds Matter in WoE WoE is not designed for random solo play. Success usually depends on: * guild coordination * role assignment * communication * preparation * timing * defensive and offensive planning A well-organized guild can often outperform stronger individual players who do not work together. ### Common Roles in WoE Different classes and builds can contribute in different ways during WoE. Common guild roles may include: * front-line fighters * damage dealers * support and healers * debuff or control roles * defensive line holders * castle breakers * utility or disruption roles This is why WoE rewards class diversity and organized planning. ### Why WoE Preparation Matters WoE is one of the clearest examples of preparation turning into performance. A player who prepares properly usually performs much better than one who joins casually without a plan. Preparation may include: * building a WoE-appropriate class setup * improving gear and refinement * using proper cards * bringing enough supplies * understanding your guild role * knowing how your class contributes in group fights WoE is not the kind of content where “just showing up” is always enough. ### WoE Builds Are Different From Farming Builds One of the biggest beginner mistakes is assuming that a normal farming build is automatically good for WoE. That is often not true. A farming build is usually made for: * efficient monster killing * safe solo progression * zeny or loot farming * low downtime A WoE build may need more focus on: * survivability in player combat * guild utility * area control * support value * burst or pressure in PvP situations * coordinated team fighting This means players often need to adjust their build if they want to take WoE seriously. ### What Makes a Good WoE Character A good WoE character usually has: * a clear role * proper PvP or WoE-oriented skill choices * gear that supports survivability and function * enough supplies for sustained fighting * understanding of positioning * awareness of guild strategy Raw damage is useful, but in WoE, a character that supports the guild properly is often more valuable than a selfish build with no team purpose. ### Offense and Defense in WoE WoE usually has two major sides: #### Offense Your guild pushes into enemy-held castles, clears defenders, reaches the Emperium, and tries to take control. #### Defense Your guild protects its castle, stops enemy pushes, controls chokepoints, and prevents the Emperium from being broken. Both sides require different thinking, and strong guilds know how to switch between them effectively. ### Why WoE Is a Progression Goal WoE gives players a reason to improve their characters beyond ordinary farming. It motivates progression in areas like: * better gear * stronger class builds * refined equipment * card optimization * guild coordination * PvP experience Because of this, many players treat WoE as one of the main “why” goals behind all their farming and gearing. ### Good Beginner Approach to WoE If you are new to WoE, do not worry about being perfect immediately. A good beginner approach is: 1. join a guild that participates in WoE 2. learn your role before the event starts 3. bring enough supplies 4. focus on helping your team instead of chasing solo kills 5. observe experienced players 6. improve your build over time based on real experience WoE becomes much easier to understand once you participate regularly. ### What New Players Should Focus On As a new WoE player, your first priorities should be: * staying alive longer * understanding movement and positioning * learning how guild pushes work * knowing where to stand * following calls and instructions * supporting team goals Trying to be a hero too early often leads to poor performance. ### WoE and Guild Communication Communication is one of the biggest factors in WoE success. Strong guilds usually do better because they: * coordinate movement * call targets * assign roles clearly * react quickly to threats * manage defense and offense properly Even a strong build can underperform if the player does not follow team coordination. ### Common Beginner Mistakes in WoE Try to avoid these mistakes: * entering WoE with a pure farming build * ignoring your guild’s strategy * rushing ahead alone * underpreparing your supplies * standing in bad positions * focusing only on personal kills * not understanding your class role in group fights WoE is won by disciplined play much more than by random aggression. ### Why WoE Is Worth Learning Even if you are not a PvP expert yet, WoE is worth learning because it gives you: * a stronger reason to gear up * more connection to the guild community * valuable PvP experience * long-term motivation * some of the most exciting moments on the server For many players, WoE becomes one of the most memorable parts of Ragnarok. ### Final Advice Do not think of WoE as content only for elite players. Every experienced WoE player started by learning the basics: where to stand, how to prepare, how to support a guild, and how to improve over time. If you approach it with the right mindset, WoE can become one of the most rewarding parts of Siege of Midgard RO. Build for your role, work with your guild, and improve step by step. ### Summary The WoE Guide helps players understand: * what WoE is * why guild coordination matters * how WoE differs from normal farming content * why builds and preparation matter * how beginners can start joining WoE properly WoE is one of the server’s biggest competitive goals. Learn it well, and it can become one of your best long-term experiences. --- # 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: ``` GET https://siege-of-midgard-ro.gitbook.io/wiki-smro/events/woe-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.