How to edit monster 3D models (BMD) on your MU Online server

Monsters are the first visual impression a player gets of your MU Online server, and a reskinned bestiary or exclusive creatures set a server apart from being "just another clone." A creature's entire appearance lives in BMD files (mesh, skeleton, animation) and their associated textures (OZJ/OZT), completely independent from the combat attributes stored on the server. This tutorial covers the full editing workflow: from the anatomy of the BMD file to texture reskinning, scale and hitbox adjustments, animations, and finally safely distributing changes to players without breaking anti-cheat.

Anatomy of a monster's BMD file

A monster's .bmd file contains three main blocks: the mesh (geometry, vertices, and faces), the skeleton (bones and hierarchy used for animation), and the texture references (which point to external OZJ/OZT files). Unlike a static item, a monster's BMD carries multiple animation sequences — idle, walk, attack, die — all tied to the same skeleton. Editing any of these parts without understanding how it depends on the others usually results in deformed monsters or ones stuck in a single pose.

Required tools

• A community MU BMD editor (the most common ones read and rewrite mesh, skeleton, and animation together).
• An image editor with alpha channel support (for textures with transparency, such as wings or effects).
• A standalone BMD viewer to test the model outside the client, avoiding a game restart for every tweak.
• A full backup of the Data/Monster/ folder before making any changes.

Prerequisites

• A functional, unmodified MU client matching the version of your already configured server.
• Write access to the client's Data/Monster/ folder.
• An update launcher to distribute the files to players.
• Familiarity with the MonsterSetBase.txt structure on the server, to match appearance with attributes.

Step 1 — Choose between a reskin and a new model

Reskinning (only swapping the texture of an existing monster) is fast, safe, and doesn't touch the mesh or skeleton — ideal for color variants (e.g., a purple Elite Bull Fighter). Building a new model from scratch requires its own mesh and skeleton plus every animation redone, which multiplies production time and the risk of error. For most servers, the recommended path is to start with reskins and reserve entirely new models for exclusive event bosses.

Step 2 — Open and inspect the original BMD

Open the base monster's file in the BMD editor and check: number of referenced textures, number of skeleton bones, and the list of available animations (idle, walk, attack1, attack2, die, etc.). Note these numbers down — any structural edit needs to preserve the bone count referenced by the animations, or they will break.

Step 3 — Edit or replace the textures (reskin)

1. Export the monster's original texture (OZJ/OZT) to an editable format.
2. Adjust color, pattern, or add detail in the image editor, keeping the same resolution and the same alpha channel (if any).
3. Repack it into the OZJ/OZT format expected by the client.
4. Re-link the new texture to the BMD, keeping the same filename (if replacing) or a new filename properly referenced inside the BMD (if it's a new variant).

Step 4 — Adjust scale and hitbox

The monster's visual size is controlled by a scale factor inside the BMD itself or by a column in the server's MonsterSetBase.txt, depending on the emulator. The table below summarizes the visual effect of different scales on a base monster:

Scales above 2x tend to detach the collision hitbox from the visual mesh, making the player hit the monster "in mid-air." Always test in-game after changing the scale, not just in the standalone viewer.

Step 5 — Adjust or reuse animations

Animations are tied to the original BMD's skeleton. If you haven't changed the bone structure, you can reuse all the original animations in a reskin with no extra work. If you created a new skeleton (a model built from scratch), each animation (idle, walk, attack, death) needs to be recreated and individually tested — the most time-consuming stage of a fully custom monster.

Step 6 — Match the appearance with the server-side attributes

Once the BMD is ready, link it to the corresponding monster index in MonsterSetBase.txt (or your emulator's equivalent file), setting health, damage, defense, experience, and the drop table. A visually terrifying monster with common-mob attributes frustrates players; keep appearance and difficulty coherent.

Step 7 — Test on a clean client

1. Copy the test client (never the production one) and replace the edited files.
2. Spawn the monster via GM on a test map.
3. Watch the animation in every state: idle, walking, attacking, and dying.
4. Check the hitbox by attacking from different angles.
5. Test on at least two screen resolutions to make sure the texture doesn't distort.

Step 8 — Package and distribute via launcher

Include the new BMD and texture files in the launcher's update package, keeping the same folder structure as the client. If your launcher or anti-cheat validates file hashes, update the checksum list to include the new files — otherwise legitimate players may get flagged for using a modified client.

Common errors and fixes

Monster editing checklist

• Backup of the Data/Monster/ folder made before any changes.
• Original BMD inspected (bones, animations, textures).
• Reskin vs. new model decided based on available time.
• Scale and hitbox tested in-game, not just in the viewer.
• Animations complete and free of freezes.
• Server-side attributes (MonsterSetBase.txt) coherent with the appearance.
• Tested on a clean client, in more than one resolution.
• Files distributed via the launcher and anti-cheat updated.

With the monster editing pipeline mastered, the natural next step is applying the same visual-customization logic to other layers of the game, such as items and skill effects, giving your server a consistent visual identity — also check out the MU Online server creation tutorial to review the fundamentals before expanding your custom content.

Frequently asked questions