GM and Admin commands in MU Online: complete reference

Game Master commands are the tools that let you run your server in real time: launching events, helping stuck players, moderating rule-breakers, and testing new content. Understanding them properly is part of running a server well.

How access levels work

CTLCODE — ACCESS LEVELS:

The CtlCode field in the MEMB_INFO database table controls what commands each account can use.

CtlCode 0 = Regular player (no GM commands)
CtlCode 1 = Game Master (moderation and event commands)
CtlCode 2 = Senior GM / Moderator (varies by distribution)
CtlCode 3 = Admin / Server Owner (all commands)

SET GM ACCESS IN THE DATABASE:
-- In SSMS → New Query → MuOnline database:
UPDATE MEMB_INFO
SET CtlCode = 1
WHERE memb___id = 'gm_account_name';

-- Remove GM access:
UPDATE MEMB_INFO
SET CtlCode = 0
WHERE memb___id = 'former_gm_account';

-- Verify current access levels:
SELECT memb___id, CtlCode FROM MEMB_INFO WHERE CtlCode > 0;

Player management commands

PLAYER MANAGEMENT:

/ban [account_name]
→ Bans an account from connecting
→ Common use: cheaters, rule violators, ban evaders

/unban [account_name]
→ Removes the ban from an account

/disconnect [character_name]
→ Disconnects a player from the server immediately
→ Common use: stuck players, suspected cheaters mid-investigation

/kick [character_name]
→ Similar to disconnect — kicks from the game session

/mute [character_name] [minutes]
→ Silences a player in public chat for the specified duration
→ Common use: spam, inappropriate language in global chat

/unmute [character_name]
→ Removes the silence penalty

/move [character_name] [map_name]
→ Teleports a character to a specific map
→ Common use: helping stuck players, pulling players for events
→ Example: /move PlayerName lorencia

/summon [character_name]
→ Teleports a character to YOUR current location
→ Common use: gathering players for events or investigation

Chat and announcement commands

COMMUNICATION COMMANDS:

/post [message]
→ Sends a golden announcement visible to ALL players on the server
→ The most important command for running a server
→ Examples:
  /post Blood Castle will start in 5 minutes!
  /post Server maintenance in 30 minutes — save your characters.
  /post Event: Find the GM for a special prize! Location: Devias.

/notice [message]
→ Similar to /post — sends a notice (some distributions use different text color)

/gmchat [message]
→ Sends a message visible only to other GMs (not regular players)
→ Use for coordination between GMs during events

Item commands

ITEM COMMANDS (typically CtlCode 3 / Admin only):

/additem [item_code] [level] [skill] [luck] [option]
→ Adds an item directly to your inventory
→ item_code: numerical code from your server's item database
→ Example: /additem 0,0 15 1 1 4  (Dark Knight sword +15 with skill, luck, +16 option)

/giveitem [character_name] [item_code] [...]
→ Gives an item to another player's inventory
→ Use extremely sparingly — items given by GMs can destabilize the server economy

/addzen [amount]
→ Adds Zen to your character's inventory
→ Only use for testing — giving Zen to players distorts the economy

/setlevel [character_name] [level]
→ Sets a character's level
→ Common testing use only — don't use in response to player requests

/resetchar [character_name]
→ Performs a reset on the specified character
→ Use only if the player had a reset bug that didn't process correctly

Event management commands

EVENT COMMANDS:

/bc [level]
→ Opens Blood Castle for the specified level range
→ Example: /bc 4 opens Blood Castle 4
→ Note: most servers have automatic scheduling — only use manually if auto-schedule failed

/ds [level]
→ Opens Devil Square for the specified level range

/cc [level]
→ Opens Chaos Castle for the specified level range

/startinvasion
→ Triggers a boss invasion (White Wizard, Red Dragon, or similar)
→ Available commands vary significantly by distribution

/gohide / /gobigmap
→ GM mode commands: hide your character from players (useful during investigations)
→ Some distributions use /hide or /unhide

BEST PRACTICES FOR EVENTS:
→ Announce 5-10 minutes before: /post [Event] starts in 10 minutes at [Location]!
→ After the event: /post [Event] has ended. Congratulations to [winner]!
→ Log what you did and when — keep an event history

Setting up a GM account properly

GM ACCOUNT SECURITY:

NEVER:
→ Use your personal game character account as the GM account
→ Share the GM account password with players (even "trusted" ones)
→ Leave the GM account logged in when you're away from the server
→ Give CtlCode 3 (admin) to people who don't need it

BEST PRACTICE SETUP:
→ Create a SEPARATE account for GM use (e.g., GM_ServerName)
→ Create a GM CHARACTER that stays at low level (no real items)
   — this prevents other players from knowing what items GMs have
→ Limit /post announcements to relevant, useful information
   — constant irrelevant posts train players to ignore them
→ If you have multiple GMs: give each their own account with the minimum access needed
   — not everyone needs CtlCode 3

GM CHARACTER NAME CONVENTION:
→ Use [GM] prefix: [GM]ServerName or [Admin]ServerName
→ This lets players know who to contact for help
→ Be consistent — all GMs should follow the same naming pattern

Common GM mistakes that harm servers

MISTAKES TO AVOID:

1. GIVING ITEMS TO FRIENDS
→ Even +15 weapons "just as a test" end up in circulation
→ Other players notice and lose motivation ("the GMs give free items to their friends")
→ Every item that bypasses the economy erodes trust in the server

2. BANNING WITHOUT INVESTIGATION
→ A player accuses another of cheating → you ban the accused immediately
→ The accused was innocent → you've lost a legitimate player and gained a reputation for unfairness
→ Always gather evidence first (screenshots, logs, witnesses)

3. IGNORING PLAYER REPORTS
→ Players who report rule violations and get no response stop bothering to report
→ They also stop playing
→ Acknowledge reports even when you can't act immediately

4. ANNOUNCING MAINTENANCE WITH NO NOTICE
→ Players lose progress if the server goes down mid-session without warning
→ Always /post maintenance 15-30 minutes in advance

5. OVERUSING /post
→ If every /post is "GM here — anyone need help?" players stop reading them
→ Reserve /post for announcements that actually matter: events, maintenance, rule changes

Pair this guide with the server anti-hack security tutorial (for protecting the GM accounts and server from abuse), the castle siege configuration tutorial (the largest event GMs will manage), and the award system tutorial (for setting up automated event rewards that reduce the need for manual GM item distribution).

Frequently asked questions