Start/stop components in order, auto-restart on crash, SQL connect + DB backup scheduling, logs per server tab, and lightweight CPU/RAM monitoring — built for speed and clarity.
Works great for multi-instance setups (GameServer, DataServer, JoinServer, etc.).
Simple & practical
Add screenshots later: one with the main dashboard, one with DB Manager / Backups, one with Logs.
What it is, in one minute
Start components top→bottom, auto-hide after launch, double-click to show/hide a running process, and stop safely (CloseMainWindow / Kill).
Connect using host/user/pass, load available databases per server tab, select one or many, run manual backup or schedule auto backup with retention (keep last X).
Small UI, big utility
Lightweight usage panels + per-process info, designed to stay compact.
Configurable logging per tab. Clean folder structure in Data/Logs.
Detects unexpected exits and restarts what needs to be restarted — without spawning duplicates.
Simple “Connected / Closed” indicators, running/stopped icons, and clear tooltips.
Each tab can have its own stack, SQL settings, backup schedule, and log toggles.
Runs with clean defaults and scales as you add components and modules.
Short and honest
ItzyServerManager is a focused desktop tool built for people who run MU Online stacks and want one place to
start, monitor, restart, and maintain everything without messy scripts and guesswork.
The goal is simple: less clicking, fewer mistakes, and clean logs.
Add your link later
Add a GitHub release link, Discord link, or direct installer here.
Replace the button href with your real URL.
• GitHub Releases
• Discord Support
• Changelog
• Documentation
Keep it short
It’s optimized for MU stacks, but it can manage any Windows processes you configure.
No. As long as SQL is reachable and you selected the backup folder, scheduled backups can run even if the server processes are stopped.
Yes — each server tab is independent (paths, SQL settings, backup schedule, logs).