Guild system and hierarchy: complete guide to MU Online guilds

Guilds are the social foundation of MU Online — the structure that transforms individual players into communities capable of conquering Castle Siege, taking on end-game bosses, and dominating server dynamics. This guide covers every aspect of the guild system: creation, hierarchy, alliance, war, and Castle Siege.

Creating a guild

Guild creation requirements:

Prerequisites:
→ Character level: typically 30+ (varies by server)
→ Zen fee: a Zen amount required to register (varies by server, usually modest)
→ Location: Guild Master NPC (in Lorencia or server-defined city)

Steps:
1. Go to the Guild Master NPC (usually in Lorencia's Safe Zone)
2. Select "Create Guild"
3. Enter guild name (unique name, server-wide)
4. Pay Zen fee
5. Create guild mark (optional but recommended)
6. Guild is created — you are automatically the Guild Master

Guild name:
→ Typically 2-10 characters
→ Unique: no two guilds on same server can share a name
→ Cannot be changed after creation (on most servers)

---

Guild mark (logo):

What the guild mark is:
→ A small pixel-art logo that appears on guild members' characters
→ Other players can see your guild mark when they inspect your character
→ Visual identity for the guild

Creating the guild mark:
→ Small grid editor (typically 8×8 or 16×16 pixels)
→ Limited color palette
→ Design your mark using the Guild Master NPC interface
→ Can be updated later (Guild Master only)

Why marks matter:
→ Recognition: players associate your mark with your guild's reputation
→ In PvP: seeing an enemy guild mark tells you who you're fighting
→ In Castle Siege: marks identify attacking and defending forces

Guild hierarchy

The three-tier rank system:

Rank 1: Guild Master
→ The creator of the guild (or whoever was promoted to Master)
→ Full administrative control:
  → Invite / kick members
  → Promote/demote Battle Masters
  → Set and change guild mark
  → Declare guild war
  → Form alliances
  → Disband guild
→ In Castle Siege: The Guild Master often leads strategy
→ Key role: the face of the guild on the server

Rank 2: Battle Master / Sub-Master (officer)
→ Second tier of authority
→ Typical powers (varies by server):
  → Invite new members
  → Participate in war management
  → Lead squads in Castle Siege
→ Trusted members — Guild Master's right hand
→ Most guilds have 3-5 Battle Masters

Rank 3: Member
→ Regular guild participants
→ Powers: participate in events, use guild features
→ Cannot invite or kick other members
→ The majority of guild population

---

The Dark Lord and guild capacity:

CMD (Command) stat:
→ Only the Dark Lord class has CMD
→ CMD determines how many members the guild can hold
→ Formula (approximate): base capacity + (CMD / some factor) = max members
→ Example: 500 CMD Guild Master DL = ~40 member cap
→ 800 CMD Guild Master DL = ~60 member cap (estimate)

Why this makes DL valuable as Guild Master:
→ Larger guild = more players for Castle Siege
→ More members = more raid groups for bosses
→ Economic: larger guild extracts more from castle tax

The DL incentive:
→ Many serious guilds require their Guild Master to be a Dark Lord
→ OR have a high-CMD DL designated as the formal Guild Master (even if not the leader)
→ A maxed CMD DL as guild master = maximum recruitment capacity

Increasing guild capacity:
→ Upgrade DL's CMD (invest stat points, use Ancient Thunder Hawk set for CMD bonus)
→ This is one of the reasons end-game DL builds prioritize CMD

Alliance system

What an alliance is:

An alliance connects multiple guilds for mutual benefit:
→ Allied guilds don't fight each other in guild war (exempt from friendly fire)
→ Alliance members participate together in Castle Siege
→ Coordination for major events (boss raids, Dragon invasions)

Alliance structure:

Alliance Master (guild):
→ The leading guild of the alliance
→ Guild Master of the alliance-leading guild = Alliance Master
→ Typically the most powerful guild sets alliance direction

Allied guilds:
→ Other guilds that accepted alliance invitation
→ Contribute members to joint Castle Siege, events
→ Maintain their own guild hierarchy internally

Alliance capacity:
→ Most servers: 2-4 guilds per alliance
→ Combined member pool for Castle Siege

---

How to form an alliance:

Step 1: Guild Masters agree to ally
Step 2: One Guild Master sends alliance invitation (via Guild Master interface)
Step 3: Target guild's Guild Master accepts
Step 4: Alliance is formed

Breaking alliance:
→ Either Guild Master can dissolve the alliance
→ Common when guilds split or rivalry develops

---

Alliance strategy for Castle Siege:

Why alliances are critical for Castle:
→ A castle defender needs consistent numbers at the gate AND Crystal
→ A single 30-member guild can't cover all entry points simultaneously
→ An alliance of 60-80 players: full coverage of Castle defenses

Example alliance structure for serious Castle Siege:

Main guild (25-30 members): elite players, defense specialists
Support guild (20-25 members): backup defense + offensive push
Reserve guild (15-20 members): rotational support

Alliance coordination:
→ Use Discord/voice chat for real-time coordination
→ Assign roles before siege: who defends which gate, who goes offensive
→ Have signal words for coordinated pushes

Guild war

What guild war is:

Guild war = a formal PvP state between two specific guilds
→ Once declared: members of both guilds can attack each other anywhere
→ No PK (Player Killer) penalty during active guild war
→ No morality loss from killing guild war opponents
→ Normal PvP rules apply to everyone else (non-war guilds)

How to declare guild war:

Step 1: Guild Master uses Guild War function (via Guild interface)
Step 2: Selects target guild
Step 3: Declaration is sent to the target Guild Master
Step 4: Target Guild Master accepts or declines
Step 5: If accepted: guild war starts

Requirements (vary by server):
→ Both guilds may need to have minimum member count
→ Some servers require minimum guild level

---

Guild war resolution:

Guild war ends when:
→ Kill limit reached (e.g., first guild to 30 kills wins): most common
→ Time limit expires: if kill limit not reached
→ One Guild Master surrenders via interface
→ Mutual agreement to end

Outcome:
→ Winning guild: prestige, possible reward (varies by server)
→ Losing guild: reputation hit, but no permanent loss

---

Strategic uses of guild war:

Resolving territorial disputes:
→ Two guilds competing for the same map spawn
→ Guild war: decide it through organized combat instead of random PK

Training PvP:
→ Guild war between allied guilds: organize PvP practice
→ Before Castle Siege: war with allies to practice coordination

Server dominance display:
→ A dominant guild declaring war on a challenger = public statement
→ Server watches how guild wars resolve (community dynamics)

---

Guild war vs regular PK:

Regular PK (Kill Player):
→ No declaration needed
→ Gives "PK" status to the attacker
→ Consequences: reduced stats, turned dark blue/red
→ Bounty hunters (PKK) can kill you without consequence

Guild war kill:
→ Both parties consent (by accepting war)
→ NO PK status gained
→ No morality loss
→ Clean PvP without consequences

Why guild war is preferred over PK:
→ No penalty
→ Organized and recognized by the server community
→ More satisfying: both sides chose to fight

Building a successful guild

Guild growth principles:

1. Recruit for activity over gear:
→ An active level 150 player contributes more to events than a level 300 who logs in twice a week
→ Screen for activity: "When do you play? What events do you attend?"
→ Strong players who ghost during Castle Siege are worse than average players who show up

2. Organize events:
→ Blood Castle/Devil Square: coordinate daily runs together
→ Castle Siege: weekly coordination call
→ Boss runs: Kanturu/Kundun/Balgass groups
→ Active event participation = guild retention

3. Communication infrastructure:
→ Discord is standard: create server with channels (#announcements, #events, #castle-siege)
→ In-game chat: guild chat exists but Discord is better for coordination
→ Event reminders: post 30 min before events start

4. Treat beginners well:
→ Low-level guilds who help beginners: those beginners stay loyal
→ Gear-sharing: lend pieces to new members temporarily
→ Teaching: explain what happens at Castle Siege before their first one
→ New player goodwill builds the foundation for 6 months from now

5. Have a Dark Lord:
→ Make your highest CMD DL the formal Guild Master
→ Or coordinate with a DL who can serve in this capacity
→ Guild capacity is real — more members = more capability

---

Common guild mistakes:

Mistake 1: Recruiting everyone indiscriminately
→ Inactive members reduce morale when they're ghosts at Castle Siege
→ Better to have 20 active than 50 with 30 idle

Mistake 2: No officer structure
→ Guild Master can't manage everything alone
→ Promote 2-4 trusted Battle Masters and delegate

Mistake 3: Weak communication
→ Guilds that don't communicate lose Castle Siege coordination
→ Set up Discord before you need it, not during a crisis

Mistake 4: No non-DL Guild Master
→ If your strongest player is a DW but they create the guild: limited capacity
→ Coordinate to have a DL create the guild formally

Mistake 5: Internal conflict during Castle Siege
→ In the middle of siege is the worst time for disagreements
→ Resolve strategy disputes before the event, not during

See also the Castle Siege guide (the guild system's ultimate test), the Dark Lord class guide (why CMD matters for guild capacity), and the guild war and territory guide (advanced war strategy and map control).

Frequently asked questions