Install & security guide.
How the MU-CMS realm agent is installed, what it is allowed to do, and what happens to your data.
What you need
- Windows Server running your MU server (IGCN Season 22 today).
- SQL Server installed locally on the same machine.
- Outbound HTTPS on port 443. No inbound port has to be opened.
- About 50 MB of disk space for the agent.
Four steps
Request access
Sign-ups are by invitation for now. Talk to us on Discord; the agent download is available after approval.
Create the read-only SQL login
A dedicated SQL login with column-level SELECT grants on the tables the site needs, and EXECUTE only on SELECT-only procedures.
Install the agent service
Run the agent installer on the machine with your MU server and SQL Server (step by step: /docs/install). It runs in the background as a small Windows task.
Link your licence
Enter your licence key. The agent binds to the machine with a salted hardware fingerprint and starts its outbound heartbeat.
Only what the site shows
- Column-level SELECT on the account, character, guild, ranking, Jewel Bank and warehouse data the site displays.
- EXECUTE on SELECT-only stored procedures, including your server's own login check.
- Nothing else: the read-only SQL login has no write, DDL or admin rights, so the database itself refuses anything outside these grants.
- Only if you enable the web vault: a second, separate login may EXECUTE three vault procedures (grant, transfer, list) and nothing else. It has no table access and cannot touch inventories.
Hard limits
- Write item blobs. No web route patches inventory or warehouse data; items move through a ledger and are created or removed in game by the engine.
- Touch game files. The agent does not read or change your server folders, configs or client files.
- Stop, restart or control your game server. It has no process control over the GameServer, ConnectServer or DataServer.
- Accept inbound connections. It only connects outbound over HTTPS.
A lapse never stops the game
Licence valid and heartbeat arriving: every web feature runs normally.
When the licence expires, its grace period starts: 48 hours unless staff set another value on the licence (up to 30 days). Everything keeps working and the console shows a renew notice. A stopped heartbeat only shows the realm link as offline.
After the grace period only the web features pause and players see a maintenance page.
⚑The game server is never touched. Players can keep playing through a lapse, and web features resume once the licence is valid again.
ⓘOffline licence tokens: built, not switched on yet. When activation is enabled, an install gets a signed token and refreshes it every 7 days (never past the licence end plus its grace). A missed refresh leaves 72 hours with a "connect to refresh" notice. Today the install only reports that state; it does not lock anything.
Your data stays yours
- Player passwords are checked by your server's own login procedure on your machine. They pass through our service only in transit, encrypted, and are never stored or logged.
- After a successful login the CMS keeps only a hash of the session token, never the token itself.
- Your SQL Server is never exposed to the internet; the agent connects outbound only.
- Site statistics are daily page-view counts per page only: no cookies, no IP addresses, no device data or visitor ids are stored, bots are skipped, and browsers that send Do Not Track or Global Privacy Control are not counted.
JSON for your launcher
Served on each player site. Sign in with POST /companion/v1/login, then send the token as Authorization: Bearer <token>. No cookies are used, so other sites cannot ride a player's session.