Castle Siege Guide: Registration, Roles and Winning the Castle
Last updated: 10 July 2026
Castle Siege is MU Online's guild-versus-guild war for ownership of the Loren castle, fought weekly on RiftMu on the Loren battlefield beside the Land of Trials. Attackers win by breaking the gates, destroying the guardian statues and registering the crown; defenders win by still holding the crown when the timer runs out.
It is the single biggest scheduled fight on the server, and it is won in the week before the battle - in registration, rosters and preparation - at least as often as it is won on the stairs to the throne room.
What is at stake
The winning alliance owns the castle until the next siege. Castle ownership traditionally brings [Common on private servers]: control of the Land of Trials hunting grounds and its bosses, castle treasury or tax income on some servers [varies by server], Castle Lord prestige effects, and the loudest bragging rights in the game. On RiftMu the current castle owner is tracked in the records section on the homepage, so the whole server sees exactly whose flag is flying.
Because RiftMu's siege is weekly, ownership is never settled. A guild that wins once and stops preparing is usually a guild that owns the castle for exactly seven days.
How registration works
The registration flow below is the common private-server pattern [Common on private servers]; exact windows, item requirements and qualifying-slot counts vary by server, so confirm RiftMu's current schedule on the events page and in the news feed before siege week.
- Form the alliance. Castle Siege is fought by guild alliances, not single guilds. The main guild's master locks in allied guilds well before registration opens.
- Register the alliance. During the sign-up window, the guild master registers at the siege registration NPC in the Loren Market area.
- Sign of Lord phase. Registered guilds hunt Signs of Lord (a monster drop during siege week) and submit them to the NPC. The alliances that submit the most Signs qualify as attackers - commonly the top three [varies by server]. The current owner defends automatically and does not need to qualify.
- Announcement and ready phase. Qualified attackers are announced before the battle; use the remaining time for rosters and supplies, not panic.
The Sign of Lord phase is where most first-time alliances fail. It is a full-guild farming assignment, not something two officers handle on the last evening.
Siege timeline: from the gates to the crown
Once the battle starts, the fight moves through fixed stages. The battle length and crown timings are set by the server files [varies by server]; the sequence itself is standard:
- Muster early. Be on the battlefield, partied and buffed, well before the start. Sort comms and assignments now - on RiftMu use guild chat with
@, alliance chat with@@, and/gpostfor guild-wide announcements. - Break the gates. The castle gates have huge HP pools. Attackers commit their damage line to a gate while defenders pour area damage down from the walls. This stage is a war of attrition - rotate fresh damage dealers onto the gate.
- Destroy the guardian statues. Behind the gates stand guardian statues that must fall before the path onward opens. Defenders will stack their strongest area casters here; attackers should burn statues fast, not trade kills.
- Push the stairs. The stairway to the throne room is the bloodiest chokepoint in the game. Tanks body-block, casters carpet the steps, and progress is measured in metres.
- Take the crown switches. Two switches near the crown must be activated and held by attackers to unlock crown registration. Losing either switch mid-attempt resets the plan.
- Register the crown. The attacking guild master channels the crown for a set time [timing varies by server]. If the channel completes uninterrupted, ownership flips instantly - and the former defenders become attackers on their own castle.
- Hold until the end. The alliance registered on the crown when the timer expires wins the castle. Late steals in the final minutes are a proud siege tradition; never log off early.
Roles by class group
A siege roster is built from roles, not from whoever shows up. With 16 classes on RiftMu there is a job for everyone:
| Role | Typical classes | Job during the siege |
|---|---|---|
| Tank line | Dark Knight, Crusader, Illusion Knight, Grow Lancer | Body-block gates, statues and stairs; soak damage; peel attackers off the casters. |
| Crown clickers | Guild master plus a protected escort | The only players who can flip switches and register the crown. Their survival is the actual win condition. |
| Defense casters | Dark Wizard, Rune Wizard, Light Wizard, Lemuria Mage, Summoner | Area damage on chokepoints - walls during the gate phase, statue rooms, and the stairway. |
| Flank hunters | Magic Gladiator, Slayer, Rage Fighter, Gun Crusher | Dive the enemy backline, assassinate crown clickers and casters, punish stragglers. |
| Support | Elf, Dark Lord | Elf buffs and heals keep the tank line standing; the Dark Lord's guild summon regroups a scattered force in seconds [Official]. |
Class strengths differ - if you are unsure where your character fits, the class pages list each class's strong and weak matchups, which map directly onto siege roles.
Guild preparation checklist
- Consumables in bulk. HP and SD potions stocked deep for every member, plus antidotes against debuff-heavy defenders. Whoever runs dry at minute 90 loses the stairs.
- Buff plan. Assign Elves and Dark Lords to specific parties so buffs cover the tank line first, and re-buff on every respawn.
- Voice comms. A siege without voice chat is a mob, not an army. Use in-game
@@alliance chat only as the backup channel. - Written assignments. Gate team, statue burners, switch holders, crown escort, and a respawn plan - including where attackers place their forward respawn points [Common on private servers].
- Alt and second-account rules. Account limits differ per realm and channel on RiftMu; check the current server rules before planning to stack extra accounts, and assume the Dreadnaught anti-cheat is watching either way.
- Scout the enemy. Watch the rankings during siege week - who is levelling, who transferred guilds, and which alliance suddenly got bigger.
What winners get
Immediately: the castle, the Castle Lord title for the owning guild, and control of the Land of Trials [Common on private servers]. On some servers ownership also brings tax or treasury income [varies by server]. On RiftMu the reward with the longest shelf life is visibility - the homepage records show the reigning castle owner to every player and every visitor, all week.
Strategically, winning also changes your next siege: you defend instead of attack, which means holding chokepoints with interior lines instead of grinding through them. Many guilds find defending easier - until two attacking alliances decide to deal with the owner first.
Common mistakes
- Skipping the Sign of Lord phase. The most common failure is never qualifying at all because Sign farming was left to a handful of players.
- No designated crown escort. If the guild master dies alone at the switches, thirty people's work evaporates. The escort's only job is the master's health bar.
- Everyone at one gate, nobody watching flanks. Flank hunters exist because guilds tunnel-vision. Post sentries or lose your casters from behind.
- Burning consumables in the first twenty minutes. Siege battles run long; pace potion use and keep a reserve for the final crown fight.
- Typing instead of talking. Nobody reads guild chat while holding a chokepoint. Calls must be voice.
- Logging off after a successful crown flip. Ownership only counts at the final whistle. Defend the crown until the battle actually ends.