How to Install and Create Custom Skins for the MU Online Client

Custom skins transform the visual identity of a MU Online private server. Whether you want to retexture armor sets, reskin interface elements, or replace environmental props, the process follows a consistent workflow rooted in understanding the client's file system and asset pipeline. This guide walks through the complete process: inspecting the client structure, converting and editing textures, applying skins correctly, and distributing them to players.

Understanding the MU Online Client File Structure

Before editing anything, you need a clear map of which directories hold which assets. A standard Season 6 to Season 15 client organizes its content as follows:

MU Client Root/
  Data/
    Effect/         → particle and skill effect textures (OZJ)
    Interface/      → UI panels, buttons, icons (OZJ/OZT)
    Item/           → item icons and inventory graphics (OZJ)
    Monster/        → monster model textures (OZJ/OZT)
    Object/         → environment props and decorations (OZJ)
    Player/         → character body and armor textures (OZJ/OZT)
    Terrain/        → map ground and wall textures (OZJ)
  Custom/           → override folder (client reads this first on some builds)
  Model/
    *.BMD           → 3D model definitions including UV mappings
  Ini/
    Character.ini   → per-class skin slot assignments
    Object.ini      → object texture index mappings

The client uses an indexed loading system. When it needs a texture for, say, the Dark Knight class at armor level 2, it reads Character.ini to find the texture index, then loads the corresponding OZJ file from Data/Player/. Knowing this chain is essential before you replace any file.

Converting and Editing Texture Files

MU Online textures are stored in two proprietary formats:

• OZJ — a JPEG image with a 4-byte OZJ header prepended.
• OZT — a TGA (Targa) image with a similar OZT header prepended.

To edit these files you need a conversion workflow:

1. Strip the 4-byte header to recover the raw JPEG or TGA file.
2. Open the recovered file in any image editor (GIMP, Photoshop, Krita).
3. Edit the texture, keeping the same canvas dimensions and color mode.
4. Export back to JPEG (for OZJ) or TGA (for OZT) at the original bit depth.
5. Prepend the correct 4-byte header to produce the final file.

Many community-built tools automate steps 1 and 5. If you are working manually, the headers are simply the ASCII bytes of OZJ or OZT followed by a null byte (0x4F 0x5A 0x4A 0x00 for OZJ).

> [!WARNING] > Never change the canvas size of a texture without also updating the corresponding BMD model's UV coordinates. A 256x256 armor texture resized to 512x512 will render with severe UV stretching or tiling artifacts because the model still expects the original dimensions.

A practical conversion reference for common player textures:

Data/Player/ texture naming convention (Season 6 example):

DarkKnight_Body_00.OZJ   → base armor, set index 0
DarkKnight_Body_01.OZJ   → set index 1 (first upgrade)
DarkKnight_Body_02.OZJ   → set index 2
...
DarkKnight_Wing_01.OZJ   → wing set index 1

Workflow per file:
  original file  → strip header  → .jpg or .tga raw
  raw image      → edit in GIMP  → export same format, same resolution
  exported raw   → prepend header → new .OZJ or .OZT
  final file     → place in Data/Player/ or Custom/Player/

Creating a Complete Armor Skin Pack

A well-organized skin pack replaces all texture slots for a given armor set cohesively. Here is the recommended workflow for creating one from scratch:

Step 1 — Extract all existing textures for the target set. Use your header-stripping tool on every OZJ/OZT file that belongs to the set. Keep the originals backed up in a separate folder named _originals/.

Step 2 — Create a reference sheet. Open all extracted textures in your image editor simultaneously. Note shared color palettes, metallic highlight positions, and shadow regions. Consistency across slots prevents visual seams where different body parts meet.

Step 3 — Design with UV islands in mind. Open the corresponding BMD model in a model viewer that displays UV maps (several community tools support this). Understanding which region of the texture maps to which body part prevents you from accidentally painting over invisible areas or missing visible ones.

Step 4 — Maintain alpha channels for OZT files. TGA-based textures often carry an alpha channel used for transparency effects (wing membranes, certain helm visors). Preserve or intentionally design this channel. Dropping it flat will make transparent parts appear solid black in-game.

Step 5 — Validate in a local test client before distribution. Launch your development client, equip the target item set on a test character, and rotate the camera through all angles in bright and dark map lighting. Check for seam lines between body segments and verify that effect overlays (glow, darkness socket effects) still render correctly on top of your new textures.

> [!TIP] > Test your skins on multiple character classes if the armor is cross-class equippable. Some MU seasons share texture slots between classes and a change to one set index may visually affect a different class's lower-tier armors that reuse the same texture file.

Configuring INI Files for Custom Skin Slots

Beyond direct texture replacement, you can define entirely new skin entries by editing the INI configuration files. This is necessary when adding skin variants that go beyond the default set count:

; Character.ini — adding a custom skin slot for Dark Knight
; Original entry:
[DarkKnight]
BodyTextureCount = 13
BodyTexture0 = Data/Player/DarkKnight_Body_00.OZJ
BodyTexture1 = Data/Player/DarkKnight_Body_01.OZJ
...
BodyTexture12 = Data/Player/DarkKnight_Body_12.OZJ

; Extended entry with custom skin at index 13:
BodyTextureCount = 14
BodyTexture13 = Custom/Player/DarkKnight_Body_Custom01.OZJ
; → ensure the OZJ file exists at the exact path listed
; → index 13 must also be referenced in the item definition
;    on the server side (ItemOption.bmd or equivalent)

After editing the INI, the server's item database must reference the new index so the correct item definition maps to index 13. The exact field depends on your server's season and emulator version, but commonly it is the Texture or SkinIndex field in the item's BMD or CSV definition.

Distributing Skins to Players

Once your skin files are finalized and validated locally, you need to deliver them to players through the patch system:

1. Place all new or modified files in the patch server's hosted directory, preserving the exact relative paths (Data/Player/, Custom/Player/, etc.).
2. Update your patch list file to include each new file with its size and CRC/MD5 checksum.
3. Increment the patch version number so the launcher detects a pending update.
4. Instruct players to run the launcher/updater before the next session.

Maintain a changelog that documents exactly which files were added or replaced in each patch version. This makes rollbacks straightforward: restore the previous file version and decrement the patch entry.

By following this structured approach — understanding the file system, converting textures correctly, validating locally, and distributing through the patch pipeline — you can build and maintain a professional custom visual identity for your MU Online server without touching core game logic.

Perguntas frequentes