How to Configure Ranking and VIP on the MU Server Website

Understanding the Architecture Before You Start

Configuring a ranking and VIP system on a MU Online server website requires you to understand how your three main components interact: the game server database, the web application, and the caching layer. Rushing into SQL queries and PHP or ASP.NET code without a clear mental model of the data flow is the most common reason administrators end up with broken rankings or VIP flags that never activate.

The game server writes player data — resets, zen, kills, level — into a Microsoft SQL Server database, typically named MuOnline. Your website must read from that same database (or a replicated copy) to display accurate rankings. The VIP system works in the opposite direction: your website writes a VIP status flag to a table that the game server reads when authenticating players or granting in-game benefits.

Plan your architecture on paper first: which machine hosts the database, which hosts the web panel, whether they are on the same LAN or separated, and what port rules are in place. This planning saves hours of debugging later.

Setting Up the Database Connection and Ranking Query

Open your web panel configuration file. In most community-built MU panels the connection settings live in a single file at the project root or inside a config/ directory.

; web panel database configuration
; → connection pointing to MSSQL game server database

DB_HOST     → 192.168.1.10        ; IP of the MSSQL server
DB_PORT     → 1433                ; default MSSQL port
DB_NAME     → MuOnline            ; main game database
DB_USER     → web_readonly        ; dedicated read-only user
DB_PASS     → StrongP@ssw0rd!    ; use a strong password

; → separate connection for VIP writes (can be same host, different user)
VIP_DB_HOST → 192.168.1.10
VIP_DB_NAME → MuOnline
VIP_DB_USER → web_vip_writer
VIP_DB_PASS → AnotherStr0ngPass!

; → ranking cache settings
RANKING_CACHE_TTL   → 600        ; seconds — refresh every 10 minutes
RANKING_CACHE_DRIVER → file      ; options: file, redis, memcached
RANKING_CACHE_PATH  → ./cache/ranking/

With the connection established, write or review the ranking query. A standard overall ranking ordered by resets looks like this:

-- → top 100 players ranked by resets then by level
SELECT TOP 100
    C.Name              AS CharacterName,
    A.Id                AS AccountId,
    C.cLevel            AS [Level],
    C.Resets            AS Resets,
    C.Class             AS Class,
    C.MapNumber         AS LastMap,
    C.PkCount           AS PkKills
FROM
    Character AS C
    INNER JOIN AccountCharacter AS AC ON AC.GameIDC = C.Name
    INNER JOIN Account          AS A  ON A.Id = AC.Id
WHERE
    C.CtlCode = 0          -- → exclude GM accounts from public ranking
    AND A.blocked = 0      -- → exclude banned accounts
ORDER BY
    C.Resets DESC,
    C.cLevel DESC;

> [!TIP] > Add a composite index on (Resets DESC, cLevel DESC) in the Character table if your server has more than a few hundred active characters. This single change can reduce ranking query execution time from several seconds to under 100 milliseconds.

Cache the result of this query using your chosen driver. Never run the full ranking SQL on every page load — even a fast query repeated hundreds of times per minute will degrade both the web server and the database.

Configuring the VIP System

The VIP system has two sides: the website writes the VIP status, and the game server reads it. Start by creating the VIP table if it does not already exist in your database.

-- → VIP accounts table
CREATE TABLE VipAccounts (
    Id          INT IDENTITY(1,1) PRIMARY KEY,
    AccountId   VARCHAR(10)  NOT NULL,
    VipLevel    TINYINT      NOT NULL DEFAULT 1,  -- → 1=Silver 2=Gold 3=Diamond
    StartDate   DATETIME     NOT NULL DEFAULT GETDATE(),
    ExpiryDate  DATETIME     NOT NULL,
    GrantedBy   VARCHAR(50)  NOT NULL DEFAULT 'system',
    Notes       VARCHAR(255) NULL
);

-- → index for fast lookup by AccountId
CREATE INDEX IX_VipAccounts_AccountId ON VipAccounts (AccountId);

-- → index for expiry cleanup job
CREATE INDEX IX_VipAccounts_ExpiryDate ON VipAccounts (ExpiryDate);

In your web panel, the VIP grant logic should validate the account exists, check for an existing active VIP record, and either insert a new row or extend the existing expiry date. Never duplicate rows for the same account — always update if a record already exists.

> [!WARNING] > If your game server reads VIP status directly from this table during login, changes take effect only on the player's next login. Communicate this clearly to your players to avoid support tickets claiming VIP did not activate immediately after a grant.

On the game server side, locate the configuration or script responsible for login authentication and bonus granting. Add a lookup against VipAccounts filtered by AccountId and ExpiryDate > GETDATE(). Map each VipLevel value to the specific in-game bonuses you have defined (experience multiplier, command access, warp rights, and so on).

Building the Ranking Display Page

With the data layer solid, build the front-end ranking page. The key principles are: paginate results, make columns sortable by class or by a specific stat, and clearly distinguish GM accounts even when they are excluded from the ranked list.

Structure your ranking table with clear headers: Position, Character Name, Class icon, Level, Resets, and Guild. Add a search input that filters client-side for fast UX — do not issue a new SQL query for every keystroke.

For the VIP display, add a badge or icon next to VIP player names in the ranking. Query VipAccounts in the same cached ranking job and join the result in memory (not in SQL) so you do not slow down the main ranking query. A simple associative array keyed by AccountId is enough.

Test the ranking and VIP pages with a browser developer tool open. Check that your cache headers prevent the browser from serving stale ranking data, and verify that the VIP badge appears and disappears correctly when you manually insert and expire test rows in VipAccounts.

Automating Expiry and Maintenance

A VIP system without automated expiry management becomes messy within weeks. Create a scheduled job — a cron job on Linux or a Windows Task Scheduler entry on Windows — that runs a cleanup query once per hour.

-- → scheduled cleanup: flag expired VIP accounts
-- → run this as a stored procedure on a schedule

UPDATE Character
SET CtlCode = 0          -- → remove any VIP-granted in-game flags if applicable
FROM Character AS C
INNER JOIN AccountCharacter AS AC ON AC.GameIDC = C.Name
WHERE AC.Id IN (
    SELECT AccountId FROM VipAccounts
    WHERE ExpiryDate < GETDATE()
      AND VipLevel > 0
);

-- → optional: archive expired rows instead of deleting them
INSERT INTO VipAccountsArchive
    SELECT *, GETDATE() AS ArchivedAt FROM VipAccounts
    WHERE ExpiryDate < GETDATE();

DELETE FROM VipAccounts WHERE ExpiryDate < GETDATE();

Also schedule a ranking cache refresh job at the same interval you defined in RANKING_CACHE_TTL. On PHP-based panels this is often a CLI script called via cron; on ASP.NET panels it is typically a background hosted service or a hangfire job.

Log every VIP grant, renewal, and expiry to an audit table. When a player disputes their VIP status, a clean audit log resolves the issue in seconds rather than requiring you to dig through application logs manually.

By keeping the database schema clean, the ranking query cached, the VIP logic auditable, and the expiry automated, your server website will run reliably even as your player base grows.

Perguntas frequentes