How to safely reset rankings and seasons in MU Online

Resetting rankings and ending seasons is the heart of managing a MU Online server that wants to keep players engaged for a long time. A ranking that never resets loses its appeal: the pioneers pull so far ahead that no newcomer bothers to compete. A well-ended season, on the other hand, creates a restart milestone, rewards the champions and brings back old players eager to fight for the top again. The problem is that a poorly done reset destroys data, leaves characters corrupted and drives the community away. This tutorial shows how to do it with real safety.

First of all, you need to separate two concepts that many people confuse. Resetting the ranking means zeroing the competition metrics — a character's total resets, PvP kills, event points, Guild War points — to restart the race for the top, without deleting characters or items. Resetting the season is a bigger event: it can include wiping (deleting) characters, changing experience rates, adding new items and an almost complete fresh start. Both share the same safety rules — backup, maintenance and verification — but have different scopes. All table and column names in this guide are common examples whose naming varies by season/emulator (IGCN, MuEmu, Season 6, X-Files, etc.), so always confirm your server's real schema.

Prerequisites

Ranking and season resets are high-impact operations. Prepare the ground beforehand:

• SSMS with write access to the game database (MuOnline) and to the ranking database, if your emulator uses a separate one (Ranking, MuRanking, etc.).
• A full, tested backup of all databases involved. Restore it on a test machine to prove the backup works.
• A maintenance window announced to the community in advance. A surprise reset breeds outrage.
• GameServer, ConnectServer and ranking services shut down during the operation, to avoid cache overwrites.
• A prize plan for the champions of the season that is ending, with the data already extracted.
• A test environment where you run the entire reset before applying it in production. If you are still building the base, first see how to create a MU Online server.

Understanding where the ranking data lives

Rankings in MU Online can live in different places depending on the emulator. Knowing the origin of each number is what prevents you from zeroing the wrong thing. The typical mapping (example names, vary by season/emulator):

Note that the site ranking is often generated by a procedure or a cached table, fed from the game database. Zeroing only the game without regenerating the site cache leaves the site showing old data. Map both ends before you start.

Step 1: Extract and reward the champions

Never zero a ranking without first recording who won. Extract the final ranking and save the result outside the database (spreadsheet, file) for prizes and for history:

-- Top 20 by resets (example)
SELECT TOP 20
       Name,
       cLevel      AS Nivel,
       Resets,
       GrandResets AS GrandReset
FROM Character
ORDER BY GrandResets DESC, Resets DESC, cLevel DESC;

For the guild ranking (Guild War):

SELECT TOP 10 G_Name, G_Master, G_Score
FROM Guild
ORDER BY G_Score DESC;

Save these results. Then hand out the prizes agreed with the community and only then advance to the reset.

Step 2: Full, verified backup

This step is non-negotiable. Generate the backup via script to have exact control:

BACKUP DATABASE MuOnline
TO DISK = 'D:\Backups\MuOnline_pre_reset_2026.bak'
WITH FORMAT, INIT, NAME = 'Backup pre reset temporada';

Then validate the backup by restoring it on a test machine or using RESTORE VERIFYONLY:

RESTORE VERIFYONLY
FROM DISK = 'D:\Backups\MuOnline_pre_reset_2026.bak';

A backup you have never tested is not a backup — it is a hope. Keep a copy in a location separate from the production server.

Step 3: Reset only the ranking (no wipe)

This is the most frequent case: you want to restart the competition while preserving characters and items. Do it inside a transaction and always with the server shut down. Example zeroing resets, grand resets and kills:

BEGIN TRANSACTION;

-- Zero the competition metrics, preserving the character
UPDATE Character
SET Resets      = 0,
    GrandResets = 0,
    PkCount     = 0
-- Optional: filter so you do not touch GMs/admins
WHERE AccountID NOT IN (SELECT AccountID FROM MEMB_INFO WHERE CtlCode = 32);

-- Zero Guild War score
UPDATE Guild SET G_Score = 0;

-- Check the effect before committing
SELECT COUNT(*) AS PersonagensZerados FROM Character WHERE Resets = 0;

COMMIT TRANSACTION;

Numbered steps for the ranking reset:

1. Shut down GameServer, ConnectServer and ranking services.
2. Take and validate the backup.
3. Run the UPDATE inside BEGIN TRANSACTION.
4. Run the verification SELECT before the COMMIT.
5. Regenerate the site's ranking cache/table (procedure or job).
6. Bring the services back up.
7. Announce the new season to the community.

The CtlCode = 32 in the example protects administrator accounts from having their data zeroed — but the exact admin code value varies by emulator, so confirm it first.

Step 4: Reset the season with a wipe (optional)

A season wipe deletes characters for a total fresh start, keeping (or not) the accounts. This is the most destructive operation possible and requires clear communication with the community — players need to know weeks in advance. The deletion order matters because of dependencies between tables:

BEGIN TRANSACTION;

-- Remove dependencies before the characters
DELETE FROM GuildMember;   -- guild members
DELETE FROM Guild;         -- guilds
DELETE FROM warehouse;     -- vaults (if it is a total item wipe)
DELETE FROM Character;     -- characters

-- Keep the accounts (MEMB_INFO) if you want to preserve logins
-- Or zero specific fields instead of deleting

COMMIT TRANSACTION;

Many administrators opt for a partial wipe: they delete characters but keep accounts, VIP and purchased coins, so as not to punish those who invested. Decide the policy beforehand and document it for the community. Table names like warehouse and MEMB_INFO are examples and vary by emulator.

Step 5: Adjust the new season's settings

A new season is the time to rebalance. The most common changes live in GameServer configuration files and in configuration tables, not just in the database:

• Experience and drop rates in GameServer.ini or equivalent.
• Reset limits (required level, zen cost, maximum resets).
• New items and shop adjustments in the item file.
• Events and schedules in the server's scheduler.

Document each change. A new season with no novelties is not exciting; one with poorly tested changes drives players away. Test everything in the local environment first.

Step 6: Regenerate the site ranking

If your site pulls from a cache table or procedure, the ranking only reflects the reset after it is regenerated. Run the update procedure or the scheduled job:

-- Generic example; the real name varies by emulator/site
EXEC UpdateRankingCache;

If there is no procedure, confirm whether the site reads directly from the game database. If it does, the reset appears as soon as the services come back up.

Common errors and fixes

Launch checklist

Before announcing the new season as complete, go through:

• Final ranking extracted and saved for history
• Champions rewarded as agreed
• Full backup generated and validated with RESTORE VERIFYONLY
• GameServer, ConnectServer and ranking shut down during the reset
• Reset run inside a transaction, with a verification SELECT
• Administrator accounts protected from the reset
• Wipe policy (total, partial or ranking-only) defined and communicated
• New season settings adjusted and tested locally
• Site ranking cache/table regenerated
• Services brought back up and ranking checked in-game and on the site
• Official announcement published to the community

Resetting rankings and seasons is what gives your server long-term staying power, but it is also where a mistake costs the trust of the entire community. Treat each reset as a planned event: extract and reward first, take a validated backup, operate with the services shut down, and communicate transparently. Done this way, each new season becomes a reason to celebrate, not to complain.

Frequently asked questions