How to configure automatic scheduled events in MU Online

A living MU Online server is one where there is always something happening. Events like Blood Castle, Devil Square, and Chaos Castle are the pulse of the game, but relying on a GM to open them manually is unsustainable. The solution is automatic scheduling by time: you configure it once and the GameServer starts opening each event on its own, at the right minute, every day. This tutorial shows how to set these times, sync the server clock, add automatic announcements, and check the logs to confirm everything fired as expected. The example files serve as a reference — the exact format varies by emulator, but the scheduling reasoning is the same across all popular builds.

Prerequisites

Before scheduling anything, ensure a stable foundation. If you are still at the start of building the server, begin with how to create a MU Online server and come back later.

• GameServer and ConnectServer working normally.
• Administrator access to the server folder (e.g., C:\MuServer\).
• Windows Server clock correct and in the desired time zone.
• Backup of the event configuration folder before editing.
• The basic events already enabled (Blood Castle, Devil Square, etc.).

> Tip: events must be enabled before being scheduled. Scheduling a time for a disabled event does nothing — first turn it on, then set the time.

Step 1 — Understand how scheduling works

The GameServer keeps an internal clock based on the operating system's time. At regular intervals, it compares the current time against a list of scheduled times. When it matches, it fires the corresponding event: teleporting players to the queue, opening the instance, or spawning the invasion monsters.

This scheduling usually lives in a dedicated configuration file (often something like EventTimer.txt, Schedule.ini, or a section inside the main .ini). The most common structure is an "event + day + time" table. Some emulators use intervals ("every 3 hours") instead of fixed times, but fixed times are more predictable for players.

Step 2 — Locate the schedule file

Look in the GameServer configuration folder for a schedule file. An example of a fixed-time-based format:

; EventSchedule (example — varies by emulator)
; Event            Day   Hour   Minute
BloodCastle        ALL   10     00
BloodCastle        ALL   16     00
BloodCastle        ALL   22     00
DevilSquare        ALL   12     00
DevilSquare        ALL   20     00
ChaosCastle        ALL   14     00
ChaosCastle        ALL   23     00
GoldenInvasion     ALL   18     30
Crywolf            SAT   21     00

> The format above is an example. Some emulators use comma-separated columns, others space-separated, and there are builds that schedule by interval in seconds inside GameServer.ini. Always check the syntax in your package's readme before editing.

The day field usually accepts ALL (every day) or abbreviations like MON, TUE, SAT. This allows weekend-only events, for example.

Step 3 — Plan the times

Before you start typing, plan a grid that covers the day without overlapping events. A good grid respects your community's peak hours. Example reasoning:

Space competing events by at least 30 minutes. If Blood Castle and Devil Square open together, you split the population and both end up empty.

Step 4 — Edit and save the times

With the GameServer stopped, edit the file following these steps:

1. Make a backup copy of the original file (e.g., EventSchedule.bak).
2. Add or adjust the schedule lines in your emulator's format.
3. Check that there are no exact duplicate times for the same event.
4. Save the file as plain text (watch out for editors that insert a BOM or change the encoding).
5. Restart the GameServer.

> Never edit with the GameServer open. Many emulators rewrite the configuration files on close, wiping out your changes.

Step 5 — Configure automatic announcements

An event that starts without warning loses half its participants. Configure automatic warning messages before each event. Many emulators already emit the opening message, but a heads-up beforehand makes a difference. An example announcement block:

; AutoNotice (example — varies by emulator)
; Minutes before  Message
05   Blood Castle opens in 5 minutes! Get ready.
05   Devil Square starts in 5 minutes! Gather your party.
10   Golden Invasion is approaching! Keep an eye on the maps.

If your emulator doesn't support a native heads-up, an alternative is to use the scheduled global "post/notice" system, or an external script that sends an announcement command via the console. Keep the messages short and clear.

Step 6 — Sync the server clock

Since everything depends on the system time, a wrong clock breaks the entire grid. On Windows Server, ensure automatic synchronization:

# Check the current time and time zone
Get-Date
tzutil /g

# Force clock synchronization with the time server
w32tm /resync

Set the time zone to that of most of your community and avoid changing it after the server is live — changing the time zone shifts all events at once and confuses players.

Step 7 — Check the logs

After restarting, don't rely on the configuration alone: confirm in the logs that the events fired. The GameServer records the opening of each event in the log file (often in Logs/ with a date-based name).

1. Open the current day's GameServer log.
2. Look for the event's opening line (e.g., "Blood Castle Start" or similar).
3. Confirm that the recorded time matches the scheduled one.
4. If an event doesn't appear, review the schedule file and the event's enablement.

Let the server run a full day and review whether all events on the grid fired at the correct times.

Common errors and fixes

Event grid best practices

• Start with a few well-spaced events and densify as the population grows.
• Reserve peak hours for the most popular events.
• Use specific days (weekends) for special events like Crywolf.
• Document your grid in a spreadsheet; it makes adjustments and team communication easier.
• Review the grid periodically based on real participation logs.

Launch checklist

• Backup of the schedule file done
• All desired events enabled before scheduling
• Time grid planned without overlaps
• Schedule file edited and saved as plain text
• Automatic warning announcements configured
• Windows clock and time zone synchronized
• GameServer restarted after the edits
• Logs checked after a full day of operation
• Grid published on the website/Discord for players

With events running automatically, your server gains its own rhythm: the player logs in knowing that every few hours there is something to do, and you stop being hostage to opening events manually. The work is concentrated in planning the grid and checking the logs; after that, the server clock does the rest and the community feels the difference of a world that never stops.

Frequently asked questions