Complete guide to GM commands by season in MU Online

Game Master commands are the most immediate administration tool on a MU Online server: with a single line typed into chat you teleport a stuck player, hand out an event reward, silence a flamer, or launch a manual invasion. The problem is that the syntax and the list of available commands vary quite a bit between seasons and between emulators — what works on a MuEmu Season 6 may have a different name on an IGCN Season 16, and a command that exists in your distribution might simply be disabled by default. This guide organizes the most-used commands by season generation, explains the real syntax, shows concrete examples, and points out where to confirm each detail on your own server. Every numeric value and command name here is an example that varies by season/emulator — use them as a starting point, never as absolute truth.

Prerequisites

Before you start typing commands in-game, make sure of the following:

• An account with the proper access level (ctl_code) in the database. Without it, the server ignores any GM command. If you don't yet have a secure administrative account, follow the step-by-step in how to create GM/Admin accounts securely.
• Access to the emulator's command file (commands.txt, GameServerInfo, or the Commands folder), so you know which commands are enabled and what level each one requires.
• A test environment separate from the production server. Never test commands that create items or grant zen on a server with real players — it throws off the economy instantly.
• SQL Server Management Studio (SSMS) or phpMyAdmin on hand, because many commands have a query equivalent and sometimes the in-game command is bugged in your build.
• Logging enabled (LogServer or GameServer logs) to audit who used what. A GM command without a log is an invitation to internal abuse.

How the server identifies a command

When you type something starting with / (slash) or sometimes ~, !, or @ depending on the emulator, the GameServer intercepts the string before treating it as normal chat. It checks three things: whether the text matches a registered command, whether the command is enabled in the config, and whether your account's ctl_code reaches the minimum level of that command. Only then does it execute. That's why the same command can "not work" for three different reasons — disabled, wrong name for the season, or insufficient access. Always diagnose in that order.

The default prefix varies: MuEmu and its derivatives usually use /, some older builds use ~, and there are distributions that accept multiple. Confirm it in your commands.txt.

Universal commands (work in almost every season)

These are the core set you'll find from Season 1 to the modern ones, with small name variations:

Note that /move usually accepts both a map name and a numeric map index depending on the build. In some seasons the command is /moveall to drag the whole party along.

Commands by season — overview

The table below summarizes what each generation adds to the universal set. Treat the names as examples that vary by season/emulator:

Season 6 — the most popular on Brazilian servers

Season 6 (especially Episode 3) is the most common base on PT-BR servers because of the maturity of the MuEmu and IGCN emulators. Typical commands:

1. Grant experience or level: /setlevel <nick> <level> adjusts the level instantly. Useful for balance testing.
2. Master Level: /setmaster <nick> <level> sets the master level; it's been around since S6 with the Master Skill Tree system.
3. Add points: /addstr, /addagi, /addvit, /addene, /addcmd (command is the Dark Lord's). Example: /addvit MyGM 5000.
4. Manual events: /openevent <id> or /event <name> starts Blood Castle, Devil Square, or Chaos Castle outside the automatic schedule.
5. PK clear: /pkclear <nick> resets the killer status without needing the NPC or the site.

A typical configuration block that enables commands and sets the minimum level (ini format, example):

[GameServerInfo]
; Minimum access level per command (varies by emulator)
GMMoveCommand      = 1   ; regular GM can move
GMPostCommand      = 2   ; senior GM can announce
GMBanCommand       = 4   ; only Admin bans
GMCreateItem       = 8   ; only Admin creates items
CommandPrefix      = /   ; command prefix

Modern seasons (13, 15, 17, 19)

Modern seasons add classes (Grow Lancer, Rune Wizard, Slayer), the fourth ascension Majestic, and dozens of new events. This brings specific commands:

• /majestic <nick> — forces the evolution to the fourth class in test environments.
• /setresets <nick> <qty> — sets the reset count, when the reset system is in-game.
• /openevent <id> — opens events such as Acheron Guardian, Nixie Lake, and Tormented Square, whose IDs you look up in the event config.
• /clearinv <nick> — clears the inventory, useful for resolving stuck-item bugs.
• Cash currency commands: some emulators expose /addcoin <nick> <value> to credit WCoin/Goblin Point directly, but the recommended approach is to do this through the web panel with a log.

Example of a command that credits an item by index (item numbering varies by season/emulator):

-- SQL equivalent of "create item" (Season 6, example)
-- Category 12 (wings), index 3 (Wings of Spirit)
-- The item hex build changes between versions; use the emulator's tool
INSERT INTO warehouse (AccountID, Items)
VALUES ('gmAccount', 0x...);

In practice, creating an item via raw SQL is fragile because the binary item format has changed several times. Prefer the in-game command /make or /item when available, or your emulator's official tool.

Admin commands vs GM commands

It's important to separate the two roles. A GM on duty needs moderation and support commands (move, warn, silence, disconnect, check a player). An Admin has access to destructive or value-generating commands (create item, grant zen, ban account, change rates at runtime). Mixing these is the main cause of internal abuse on servers. The example table:

Controlling who holds each level is done through the ctl_code in the database and, in many emulators, through a GMList that matches a nick or account to a numeric level.

Step-by-step: enabling a disabled command

1. Open the emulator's command file (commands.txt, GameServerInfo.dat, or the corresponding .ini).
2. Locate the line for the desired command. If it has a value of 0 or is commented out, the command is off.
3. Set the minimum access level — don't leave item-creation commands at level 1.
4. Save the file with its original encoding (many emulators require ANSI, not UTF-8).
5. Reload with /reload if the emulator supports it, or restart the GameServer.
6. Test with a GM account of the matching level and check that the log recorded the use.

Command auditing and logging

Every sensitive command should leave a trail. Configure the LogServer or the GameServer logs to record author, command, target, and timestamp. A healthy logging setup lets you answer "who gave that item?" in seconds. Without it, a malicious GM can inflate the economy and you only find out once the server is already broken. Review the logs of value-generating commands (item, zen, coin) at least once a day during the first months.

Common errors and fixes

Usage best practices

• Never use value-generating commands on the production server, except for an official event reward with a log.
• Standardize the prefix and document the real command list in an internal file for the staff.
• Use GM accounts separate from the administrators' personal gameplay accounts.
• Revoke destructive commands from GMs who leave the team immediately (lower their ctl_code).
• Test the whole list on a staging server after every emulator update — commands disappear or change names between builds.

Launch checklist

• Command file reviewed and each command assigned a minimum level
• Value-generating commands (item, zen, coin) restricted to Admin
• Command prefix documented and tested
• Command logging enabled and verified in a real test
• GM accounts with the correct ctl_code per role
• Command list per season documented for the staff
• Tested on staging after the current emulator version
• /ban and /disconnect working and recording to the log
• Access-revocation procedure defined for staff departures

Frequently asked questions