How to Create Complete Documentation for Your MU Online Server

Why Documentation is the Foundation of a Solid Server

Running a MU Online server goes far beyond uploading files and opening ports. Without organized documentation, every configuration becomes a mystery — and when something breaks, the time spent trying to remember "what was done" costs far more than the time it would have taken to document properly from the start.

Good documentation acts as the collective memory of the project: new collaborators understand the server without asking obvious questions, players find answers before opening tickets, and you — six months later — won't be cursing your past self for the lack of organization.

This guide focuses on Season 6 — the most popular and technically rich version of MU Online — and shows how to structure documentation progressively, starting with what matters most to players and advancing to administration details.

Base Structure: What to Document First

Organize documentation into thematic blocks. Order matters: start with what players encounter the moment they first log in.

Suggested documentation structure:

1. Classes and Evolution
   → Dark Knight → Blade Knight → Blade Master
   → Dark Wizard → Soul Master → Grand Master
   → Elf → Muse Elf → High Elf
   → Magic Gladiator → Duel Master (no Wing L1, no 1st/2nd level quest)
   → Dark Lord → Lord Emperor (exclusive CMD stat)
   → Summoner → Bloody Summoner → Dimension Master

2. Stat System
   → STR (Strength) — physical damage, weapon requirements
   → AGI (Agility) — defense, attack speed
   → VIT (Vitality) — total HP
   → ENE (Energy) — magic damage, MP
   → CMD (Command) — Dark Lord exclusive, controls Darkhorses and Dark Ravens

3. Wings and Evolution
   → Wing L1: basic craft per class
   → Wing L2: advanced craft per class
   → Wing L3: Wing L2 + 3x Loch's Feather + Jewel of Creation
   → Loch's Feather: dropped by Balgass (Crywolf FAILS)

4. Available Maps
   → Lorencia, Noria, Devias, Dungeon (3F), Lost Tower (7F)
   → Atlans (3F), Tarkan, Icarus, Aida, Karutan
   → Kanturu (3F), Kalima (1-7), Land of Trials
   → Crywolf Fortress, Raklion, Vulcanus, Acheron

5. Events and Bosses
6. Craft System and Jewels
7. Server configurations (rates, reset, etc.)

Documenting the 6 S6 Classes with Accuracy

Each class has specific rules that must be recorded with precision. Common errors in MU Online documentation include assigning Wing L1 to Magic Gladiator (it has none), or listing Rage Fighter as an S6 class (it does not exist in this version).

Dark Knight (DK) The most straightforward class for new players. Evolves to Blade Knight at the 1st quest and Blade Master at the 3rd quest. Focuses on STR and AGI. Document the most commonly used builds on your server: Full STR BK, Agility BK, and hybrid variations. List the most relevant armor sets by level range.

Dark Wizard (DW) Base magic class. Evolves to Soul Master, then Grand Master. Primary stat: ENE. Document the damage difference between pure ENE builds and VIT-mixed builds for PvP survivability. Soul Master gains access to teleport — a feature that completely changes mobility and is worth highlighting explicitly.

Elf Support and ranged class. Evolves to Muse Elf, then High Elf. Has unique buff skills that affect the entire party. Record which buffs each evolution unlocks and the ENE requirements to activate them. Elf is the only class that can use Arc of Archangel efficiently — a detail many new players don't know.

Magic Gladiator (MG) Hybrid class unlocked after reaching level 220 with any character. Has no 1st or 2nd level quest. Evolves directly to Duel Master at the 3rd quest. Does not use Wing L1. Uses STR and ENE as primary stats. These two specific rules must be prominently displayed in the documentation — they are the most frequently asked questions about the class.

Dark Lord (DL) Support and leadership class. Evolves to Lord Emperor. Has the exclusive CMD (Command) stat, which determines how many creatures (Dark Horse and Dark Raven) can be controlled and boosts party skills. Document a CMD table showing effects at each point range.

Summoner Female class using summoning magic and debuffs. Evolves to Bloody Summoner, then Dimension Master. ENE-based. Has unique weakening skills that make her valuable in PvP. Record exclusive skills and their ENE requirements.

Documenting Maps: More Than a List of Names

Listing S6's 17 maps is easy. The challenge is documenting them usefully. For each map, record:

• Level requirement for entry (if any)
• Main monsters and recommended level range for farming
• Exclusive bosses and respawn timers
• Relevant drops — especially sets, weapons, and jewels
• Special dynamics — Atlans has fish and Hydras, Kanturu has the core event, Kalima has 7 floors with Kundun at the top, Crywolf has the statue defense event

Dungeon with its 3 progressive floors is excellent for documenting the difficulty curve for beginners. Lost Tower with 7 floors is dense — document floor by floor if possible.

Crywolf Fortress deserves special attention: this is where the Fenrir statue defense event takes place. When the event fails (players cannot protect the statue), Balgass spawns — and only at this moment can Loch's Feather be obtained. Loch's Feather is the critical ingredient for crafting Level 3 Wings (Wing L2 + 3x Loch's Feather + Jewel of Creation). This chain of information must be clearly linked throughout your documentation.

Tools and Formats for Writing Documentation

You don't need specialized software to create good documentation. What matters is consistency of format and ease of updating.

Markdown is the most recommended format for technical documentation. It's readable without rendering, portable across platforms, and compatible with GitHub, GitBook, Notion, Obsidian, and virtually any wiki system.

To organize your server documentation, consider:

• Discord Wiki — great for living documentation that the community frequently consults
• GitBook or Notion — ideal for more elaborate documentation with multiple pages and navigation
• Folder of .md files in the server repository — versioned alongside configs, great for technical teams
• Static site (Jekyll, Hugo, Docusaurus) — for projects that want their own documentation website

The least recommended format is PDF — it makes updates and searching difficult. Server documentation changes constantly; use editable formats.

Keeping Documentation Up to Date

Outdated documentation creates more confusion than no documentation at all. Establish a minimal process:

1. Change log — with every server change (new rate, new event, class rebalancing), record the change with date and reason.

1. Periodic review — set a frequency (bi-weekly, monthly) to review the most accessed pages and correct outdated information.

1. Player feedback — create a channel or form for players to report incorrect information. They find errors faster than you do.

1. Visible update date — every page should show when it was last updated. This helps players gauge the reliability of the information.

Well-maintained documentation is a living resource. In MU Online S6, where Wing crafting mechanics, the Jewel system, and event interactions are complex, having reliable and current information makes a real difference — both for your players' experience and for your administration team's workload.

Perguntas frequentes