How to configure Castle Siege on your MU Online server

Castle Siege is the centerpiece of guild competition in MU Online. When it's well-configured and properly promoted, it becomes the event that drives player retention and gives guilds a long-term goal.

How Castle Siege works

THE CASTLE SIEGE CYCLE:

PHASE 1 — REGISTRATION (typically Monday → Friday):
→ Guild Masters register their guild by paying a registration fee (in Zen)
→ Guild must meet the minimum Guild Point requirement to be eligible
→ Multiple guilds can register for the same siege

PHASE 2 — MARKING / DECLARATION (typically Friday):
→ Registered guilds mark which side they're on (attacker or defender)
→ The current castle owner defends; challengers attack
→ Guild alliances declared at this stage

PHASE 3 — SIEGE BATTLE (typically Saturday or Sunday, evening):
→ The actual battle — lasts a fixed duration (usually 1-2 hours)
→ Attackers try to capture the castle by killing the owning guild's characters in the castle
→ Defenders hold the castle and protect specific areas
→ The guild that controls the castle at the end of the battle wins possession

PHASE 4 — POSSESSION (until next siege):
→ The winning guild gains control of the castle
→ They access the castle's benefits until the next siege cycle
→ They defend in the next Castle Siege as the current owner

Configuration files for Season 6

WHERE TO FIND CASTLE SIEGE SETTINGS:

COMMON FILE LOCATIONS IN S6:

CastleSiege.ini or CastleSiegeSetup.ini (in the MuServer config folder):
→ Siege day and time
→ Phase durations
→ Registration start time
→ Number of guilds that can register

Example CastleSiege.ini parameters:
SiegeDay = 6                    ; 0=Monday, 6=Sunday
SiegeHour = 20                  ; 8 PM
SiegeMinute = 0
RegistrationStartDay = 0        ; Monday registration begins
RegistrationEndDay = 5          ; Saturday registration closes
BattleDuration = 90             ; 90 minutes of siege battle
RegistrationFee = 5000000       ; 5 million Zen to register

DATABASE TABLES (in EventMU or MuOnline, varies by distribution):
→ T_CastleSiege or CastleSiege table: current owner guild, status
→ T_CastleSiegeRegistration: which guilds registered for this siege
→ CastleNPCInfo: NPC settings for the castle

Setting the siege schedule

SCHEDULING CASTLE SIEGE:

RECOMMENDED SCHEDULE FOR A LATAM/BRAZIL SERVER:
→ Registration open: Monday 12:00 AM
→ Registration closes: Friday 11:59 PM
→ Siege battle: Saturday 8:00 PM (server time)
→ Post-siege: Sunday — players explore what the winning guild does with the castle

SETTING THE TIME IN THE CONFIG FILE:
SiegeDay = 6          ; 6 = Saturday (0=Monday, 1=Tuesday, ..., 6=Sunday)
SiegeHour = 20        ; 20 = 8 PM in 24h format
SiegeMinute = 0       ; Start at exactly 8:00 PM

TIMEZONE CONSIDERATION:
→ Your server's system clock timezone determines when "20:00" is
→ If your VPS is in UTC and your players are in BRT (UTC-3):
  → "20:00 server time" = 17:00 BRT
  → To hit 8 PM BRT: set SiegeHour = 23 (23:00 UTC = 20:00 BRT)
→ Always announce the siege time in player local time (BRT, COT, MEX, etc.)

Guild requirements for participation

REGISTRATION REQUIREMENTS:

GUILD POINT MINIMUM:
→ Guilds must have a minimum Guild Points score to register
→ This prevents newly-created guilds from disrupting competitive siege
→ Typical minimum: 1,000-5,000 Guild Points for established servers
→ For new/small servers: 100-500 to let more guilds participate

GUILD MASTER REQUIREMENT:
→ Only the Guild Master can register the guild for Castle Siege
→ The Guild Master must be online during registration
→ The Guild Master receives the benefits of castle ownership if they win

REGISTRATION FEE:
→ 5,000,000 Zen (5M) is common for S6 mid-rate servers
→ Low enough that serious guilds can pay it; high enough to deter joke registrations
→ Reduce for new servers: 1,000,000 Zen (1M) is more accessible early

DATABASE UPDATE (if needed):
UPDATE CastleSiege
SET RegistrationFee = 5000000,
    GuildPointRequired = 1000
WHERE SiegeIndex = 1;

Castle benefits for the owning guild

BENEFITS OF CASTLE OWNERSHIP:

TAX COLLECTION:
→ The owning guild can set a tax rate on NPC trades at the castle
→ Guild Master sets the tax percentage in the castle's Treasury NPC
→ All Zen spent at the castle NPCs generates tax income for the guild
→ Tax income is split among guild members (configurable)

EXCLUSIVE ACCESS:
→ The castle's inner areas are only accessible to the owning guild and allies
→ This includes exclusive NPCs (blacksmith, warehouse, jewel NPC)
→ Some distributions give access to unique monsters that drop rare items

CRYWOLF CONNECTION:
→ The castle-owning guild controls Crywolf Fortress defense in Season 6
→ Crywolf success: Balgass doesn't spawn, but players get other rewards
→ Crywolf failure: Balgass spawns → drops Loch's Feather (Level 3 Wings material)
→ The owning guild can choose defense strategy based on what their members need

PRESTIGE:
→ Castle ownership is the top status symbol on the server
→ The guild name is displayed in the castle area
→ Server rankings typically display the current castle-owning guild at #1

Crywolf configuration (linked to Castle Siege)

CRYWOLF FORTRESS IN S6:

HOW CRYWOLF WORKS:
→ Crywolf is a defense event where players protect an altar from waves of monsters
→ Success: the Altar of God survives → Balgass doesn't reach full power
→ Failure: the Altar is destroyed → Balgass spawns in full power form

BALGASS AND LOCH'S FEATHER:
→ Balgass only drops Loch's Feather when Crywolf FAILS
→ Loch's Feather is required (3x) to craft Level 3 Wings
→ This means: letting Crywolf fail occasionally is strategically valuable for the server

CONFIGURATION IN CrywolfSetup.ini (or similar):
CrywolfDay = 3                  ; Wednesday
CrywolfHour = 21                ; 9 PM
CrywolfDuration = 30            ; 30 minutes
BalgassSpawnOnFail = 1          ; 1 = Balgass spawns when Crywolf fails

BALANCE RECOMMENDATION:
→ Run Crywolf 1-2 times per week
→ Schedule it 2-3 days BEFORE Castle Siege
→ This gives Loch's Feather time to circulate before the siege-prep rush

Running Castle Siege as a GM

GM DUTIES DURING CASTLE SIEGE:

BEFORE THE SIEGE:
→ 1 hour before: /post [Castle Siege] starts in 1 hour! Register your guild by [time].
→ 30 minutes before: /post [Castle Siege] battle begins in 30 minutes at Lorencia Castle!
→ 5 minutes before: final reminder /post

DURING THE SIEGE:
→ Monitor the castle area for rule violations (hackers, speed hacks)
→ If you see obvious cheating: /ban or /disconnect immediately
→ Don't intervene in legitimate PvP battles — players dislike GM interference in fair fights
→ Take screenshots/video of the castle capture moment for server social media

AFTER THE SIEGE:
→ /post [Castle Siege] over! [Guild Name] conquered the castle!
→ Congratulate the winner — public recognition is part of what makes siege valuable
→ Update the server website's castle ownership display if it's manual

COMMON SIEGE PROBLEMS:
→ The siege doesn't start at the right time: check server timezone vs config file timezone
→ No guilds registered: reduce the registration fee and guild point requirement
→ One guild always wins: adjust the benefit distribution or balance the battle mechanics

Pair this guide with the GM commands tutorial (for the /post and moderation commands used during events), the Crywolf event guide (player perspective on the event linked to Castle Siege), and the experience and rate configuration tutorial (for understanding how server balance affects guild progression toward Castle Siege participation).

Frequently asked questions