How to swap the music and sounds of the MU Online client

Audio is the identity layer that almost every MU Online server neglects — and that is exactly why swapping the background track and the sound effects gives your client such a distinctive feel. A remixed Lorencia theme, a punchier skill effect, a login sound branded to the server: these are details players feel even without being able to explain why. This tutorial shows how to replace music and sounds correctly, respecting format, sample rate, volume, and loop, without clipping the audio or breaking playback. All file names and values are examples and vary by season/client.

Prerequisites

• The server's production client — the same version players download.
• An audio editor: Audacity (free) is more than enough to cut, normalize, and adjust the loop. Reaper or Adobe Audition if you want more control.
• Access to the client's audio folders — typically Music/ and Sound/ (or Data/Sound/), but this varies by season/client.
• Source audio files with usage rights. Copyrighted tracks can trigger a takedown on the client's distribution. Prefer royalty-free music, Creative Commons-compatible, or your own compositions.
• A text editor (Notepad++) in case the season uses a sound index/mapping file.
• A complete backup of the audio folders in an _original/ subfolder before any swap.
• Decent headphones or monitors to judge volume and clipping — laptop speakers deceive.

How MU Online organizes audio

The client's audio splits into two categories with very different rules:

1. Background tracks (BGM) — one song per map/screen, played in a continuous loop. They live in the Music/ folder. The critical requirement here is a clean loop: the track has to restart without a pop.
2. Sound effects (SFX) — short sounds triggered by events: skill hit, button click, item pickup, level up. They live in Sound/ or Data/Sound/. The critical requirement is low latency and consistent volume — an effect that is too loud becomes annoying.

The engine loads audio by file name. Swapping a sound is, in practice, replacing the file while keeping the same name and format the client expects. Some clients have an index file that maps event → file; in those cases you can even point to a new name, but this varies by season/client.

Audio formats and requirements

The exact format varies by season/client: older clients tend to use WAV for everything; modern seasons accept MP3/OGG for BGM. Always check the extension of the original files before exporting yours — if the original is .wav and you drop in an .mp3 with the same name, the client may ignore it or crash.

Map the audio files

Just as with the interface, the first job is knowing which file is which.

1. Open the Music/ folder. The names usually indicate the map:

Music/
├── MuTheme.mp3        -> main theme / login screen
├── Lorencia.mp3       -> Lorencia BGM
├── Dungeon.mp3        -> Dungeon BGM
├── Devias.mp3         -> Devias BGM
├── Noria.mp3          -> Noria BGM
└── ...

1. Open Sound/ (or Data/Sound/) and identify the effects:

Sound/
├── sword1.wav         -> sword swing sound
├── skill_evil.wav     -> skill sound (e.g., Evil Spirit)
├── button.wav         -> UI button click
├── levelup.wav        -> level-up sound
├── pickup.wav         -> item pickup
└── ...

These names are examples and vary by season/client. Build your own reference table by listening to the original files in Audacity before replacing anything.

Step by step: swap a background track (BGM)

Let's replace a map's music, the most common case.

1. Choose the source track (with usage rights) and open it in Audacity.
2. Confirm the target format by looking at the original file you are replacing (e.g., Lorencia.mp3, stereo, 44100 Hz).
3. Adjust your project's sample rate to match the original (Audacity → project rate, bottom-left corner).
4. Cut the track to the desired length. Background tracks work best between 1 and 3 minutes, since they play on loop.
5. Create a clean loop (dedicated section below) — this is the step that fails most often.
6. Normalize the volume to the same level as the original files (Effect → Normalize; keep the peak below -1 dB to avoid clipping).
7. Export in the exact format of the original (File → Export → MP3/OGG), with the same file name you are replacing.
8. Copy it to the working folder, test it, and only then move it to the production client.
9. Enter the corresponding map in the game and listen to at least two full cycles of the loop.

How to cut a clean loop

The "click" or "pop" on every repeat comes from a cut in the wrong place. The engine jumps back to the start instantly; if the end and the beginning do not meet in amplitude, you hear the jump.

1. In Audacity, zoom in very close on the start of the track and place the cut at a point where the wave crosses zero (zero amplitude).
2. Do the same at the end: cut at a zero crossing too.
3. Ideally, the start and end should have similar energy — do not end on a climax and restart in silence.
4. Apply a fade of a few milliseconds at the start and end (Effect → Fade In / Fade Out, very short) to smooth the seam, if there is still a pop.
5. To test the loop before exporting, use Audacity's loop playback (Shift+Space) and listen to the seam several times.

Step by step: swap sound effects (SFX)

Effects require less editing but more care with volume and latency.

1. Open the source effect in Audacity.
2. Confirm the format of the original (almost always WAV PCM, 22050 or 44100 Hz, mono or stereo).
3. Cut the effect to be short and direct — a swing sound cannot have a long tail, or it gets in the way of fast combat.
4. Remove silence at the start (Effect → Truncate Silence). Silence at the beginning of the file becomes perceived latency: the player clicks and the sound is delayed.
5. Normalize the volume consistent with the other effects. An effect much louder than the rest gets annoying fast.
6. Export as WAV PCM (or the original's format), with the same name.
7. Test in-game by triggering the event (land a hit, click the button, level up).

> [!AVISO] Never let an SFX be louder than the BGM. The player hears dozens of effects per minute; if every hit clips the audio, they lower the game's overall volume and lose your carefully crafted track too.

Standardize the volume across all audio

A consistent audio library is what sets a professional client apart. Do a standardization pass:

1. Set a reference level. A good starting point is to normalize all BGMs to the same peak (e.g., -3 dB) and the SFX a little below.
2. Use loudness analysis (if your editor supports LUFS) to level perceived volume, not just the peak. Two tracks with the same peak can sound very different in volume.
3. Avoid clipping: no file should touch 0 dB. Leave at least -1 dB of headroom.
4. Test the transition between maps: enter and leave several maps in a row. If one map "explodes" and the next "whispers", adjust.

VOLUME GUIDE (reference, adjust to taste)
BGM (background track)  -> peak ~ -3 dB, uniform loudness across tracks
Combat SFX              -> peak ~ -6 dB, short and without a tail
Interface SFX           -> peak ~ -9 dB, discreet
Login/theme sound       -> peak ~ -3 dB, no clipping on the climaxes

Test the complete audio

Before distributing, run this script on a test client:

1. Login/theme screen: the main theme should play clean, at the right volume.
2. Each map BGM: enter Lorencia, Dungeon, Devias, Noria, and the main maps. Listen to at least two loops of each — watch for the repeat pop.
3. Transitions: walk between connected maps and check that the track swap is smooth.
4. Combat SFX: land hits, use skills. Low latency, balanced volume.
5. Interface SFX: click buttons, open windows, pick up items. Discreet, responsive sounds.
6. Level up and events: trigger the progression sounds and confirm they feel rewarding, not shrill.
7. Long session: play for 15–20 minutes with the audio on. If any sound tires or annoys you, adjust it before launch.

Distribute the custom audio

1. Copy the final files to the Music/ and Sound/ folders of the production client.
2. Generate a patch with only the changed audio files — audio tends to be heavy, and nobody wants to re-download the entire client because of one track.
3. Publish the package's integrity hash.

# Package only the changed audio and generate a hash (PowerShell)
& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 patch-audio.7z Music\ Sound\
Get-FileHash patch-audio.7z -Algorithm SHA256 | Select-Object Hash

If you are still building the server and client from scratch, audio is one of the final customization steps — the full creation flow is in the guide on how to create a MU Online server.

Common errors and fixes

Launch checklist

• Backup of Music/ and Sound/ stored in _original/
• Format, sample rate, and channels confirmed from the original files
• All source music with proven usage rights
• BGM loops cut at zero amplitude, no pop
• Volume standardized across all BGMs (uniform loudness)
• SFX short, with no initial silence, quieter than the BGM
• No file with clipping (minimum -1 dB of headroom)
• Transitions between maps tested
• Long test session with no annoying or tiring audio
• Patch with only the changed audio generated and hash published
• Final client tested from login to real combat

With well-cut tracks, balanced effects, and standardized volume, audio stops being a forgotten detail and becomes part of the server's identity. Respect each season's format, take care with the loops and usage rights, and validate everything on a production client before sending the patch to players.

Frequently asked questions