How to Set Up the Admin Panel and Game Master Features on MU Server

Introduction to Server Administration Architecture

Running a private MU Online server means wearing two hats: the technical server operator and the in-game administrator. These roles use different tools and carry different responsibilities. The server operator works with configuration files, databases, and process management. The in-game administrator — the Game Master — interacts with players directly through privileged game commands.

This guide walks through the full setup of both layers: configuring your web-based or tool-based admin panel, defining account authority levels in the database, and enabling and securing Game Master commands inside the game world.

Before proceeding, make sure your GameServer, ConnectServer, JoinServer (or DataServer), and EventServer processes are all operational and that you have direct access to the underlying SQL Server or MySQL database.

Configuring Account Authority Levels in the Database

The foundation of all admin and GM functionality is the authority column in your accounts table. Depending on your server emulator the table is usually named MEMB_INFO, accounts, or tbl_user.

The standard authority scale used by most Season 6 and Season 9 emulators is:

memb_authority column values:
  0   → Regular player (default)
  1   → Trial Game Master (limited commands)
  2   → Game Master (standard GM commands)
  3   → Senior Game Master (all GM commands + kick/ban)
  100 → Head GM / Community Manager
  255 → Super Administrator (full access, no restrictions)

SQL example — promote account to GM level 2:
  UPDATE MEMB_INFO
  SET    memb_authority = 2
  WHERE  memb_id = 'your_gm_account';

SQL example — demote back to player:
  UPDATE MEMB_INFO
  SET    memb_authority = 0
  WHERE  memb_id = 'former_gm';

SQL example — list all non-player accounts:
  SELECT memb_id, memb_authority
  FROM   MEMB_INFO
  WHERE  memb_authority > 0
  ORDER  BY memb_authority DESC;

After updating authority values, the GameServer must either be restarted or — if your emulator supports it — you can use the in-game /reloadgm command (Super Admin only) to refresh the GM list without a full restart.

> [!WARNING] > Never leave a test or development account with authority level 255 on a live production server. Super Admin accounts bypass all normal game restrictions and can cause irreversible damage to economy balance if used carelessly or compromised.

Setting Up the GameServer Admin Configuration Files

Most MU server emulators read GM-related settings from one or more configuration files in the GameServer/Data/ or Server/Data/ directory. The key files to review are:

GMCommand.ini / GMCommandList.ini — defines which commands exist and the minimum authority level required to use each one.

ServerInfo.ini or GameServerInfo.ini — contains global GM settings such as whether GM characters display a special crown icon, whether GMs are invisible to players by default, and whether GM actions are written to a log file.

A typical GMCommand.ini section looks like this:

; GMCommand.ini — command permission mapping
; Format: CommandName → MinAuthorityLevel → LogEnabled(0/1)

/teleport      → 2  → 1
/summon        → 2  → 1
/item          → 3  → 1
/zen           → 3  → 1
/kick          → 2  → 1
/ban           → 3  → 1
/unban         → 3  → 1
/hide          → 2  → 0
/notice        → 1  → 1
/move          → 2  → 1
/reloadgm      → 255 → 1
/shutdown      → 255 → 1

; Logging path for GM command audit trail
GMLogPath      → ../Log/GMActions/
GMLogRotation  → Daily

Save the file and restart GameServer. Commands not listed in this file are either hardcoded or disabled entirely depending on the emulator.

Configuring the Web Admin Panel

Many server packages include a PHP-based web administration panel (often called WebAdmin, MuAdmin, or similar). This panel allows server operators to manage accounts, review logs, process item restoration requests, and monitor online player counts without touching the database directly.

Key steps for initial setup:

1. Place the panel files in your web server's document root (e.g., C:/xampp/htdocs/admin/).
2. Open config.php or settings.php and set the database connection parameters:

; config.php — Web Admin Panel database settings
DB_HOST     → 127.0.0.1
DB_PORT     → 1433          ; SQL Server default; use 3306 for MySQL
DB_NAME     → MuOnline      ; your main game database name
DB_USER     → mu_admin_user ; dedicated DB user, NOT sa or root
DB_PASS     → StrongP@ssw0rd!
DB_CHARSET  → utf8

; Panel access control
PANEL_USER  → webadmin
PANEL_PASS  → [bcrypt hash — never store plaintext]
SESSION_TTL → 1800          ; session timeout in seconds (30 min)

; Allowed IP addresses (leave empty to allow all — not recommended)
ALLOWED_IPS → 192.168.1.0/24, 203.0.113.10

1. Create a dedicated database user with only the permissions the panel needs (SELECT, INSERT, UPDATE on specific tables). Never connect the panel using a DBA-level account.
2. Place the panel directory behind HTTP Basic Auth or restrict it at the firewall level so it is not publicly accessible.

> [!TIP] > If your server is hosted on a VPS, consider binding the web admin panel to a non-standard port (e.g., 8443) and enabling it only over HTTPS with a self-signed certificate. This makes automated scanners far less likely to discover it.

Defining Game Master Responsibilities and In-Game Procedures

Technical setup is only half the work. A well-run server needs clear operational procedures for its GM team.

Handling player reports: Set a standard workflow — player submits a ticket via website or Discord, a GM logs in on the GM account, uses /teleport or /move to reach the reported location, observes or investigates, then takes action and logs the outcome.

Item and zen restoration: Most web panels include a restoration form. The GM must verify the player's claim against the server log files before restoring anything. Never restore items based solely on a player's word.

Monitoring and moderation: Use the /notice command to broadcast server-wide messages for scheduled events or maintenance windows. Use /hide to observe areas without alerting players.

Scheduled events: For castle siege, blood castle, and custom events, GMs should have a checklist:

• Confirm event configuration files are correct
• Post advance notice in-game and on Discord
• Log on at the designated time to supervise
• Record any abnormal behavior (teleport hacks, duplication attempts) to the GM log

Security Hardening for Admin Accounts

Admin and GM accounts are high-value targets. Apply these measures to protect them:

• Use a username that does not match the GM character's visible in-game name. The login name and the character name are separate — keep them that way.
• Enable two-factor authentication if your web panel supports it, or restrict panel access to known IP addresses.
• Rotate GM account passwords every 30 to 60 days.
• Audit the memb_authority table monthly. Remove authority from any account whose owner is no longer active on the team.
• Keep GM log files for at least 90 days. Store them outside the web root so they cannot be downloaded via the browser.
• Never share the Super Admin (255) account credentials. Each operator should have their own named account with the minimum authority level they need.

> [!TIP] > Create a read-only "observer" account at authority level 1 for new team members during their trial period. They can use non-destructive commands like /notice and observe player behavior, but cannot issue items or ban accounts until trust is established.

Proper administration discipline — consistent logging, least-privilege access, and clear team procedures — is what separates a well-managed private server from one that collapses under internal drama or compromised accounts. The technical configuration is the foundation; the operational culture built on top of it is what keeps the community healthy.

Perguntas frequentes