Today, around 13:00, the server went through a short period of instability (repeated restarts) immediately after applying a routine AzerothCore update.

What happened?
The update brought changes in the loading mode of companion NPC-bots. At startup, the server detected that some of the recently added bots (Hunter, Rogue, Shaman, Mage, Warlock, and Druid classes from the dungeon hire list) did not have their appearance and equipment data fully defined in the database — an incomplete configuration left over from when they were added. The new version of the server treats this lack as a critical error and stops starting, resulting in a cycle of automatic restarts.

What I fixed:

• Filled missing data (visual model + equipment) for all 60 affected bots (companion hire — Hunter/Rogue/Shaman/Mage/Warlock/Druid)
• Removed an overlap between the server autostart mechanisms (cron + systemd), which could cause port conflicts on reboot
• Added a system-wide circuit breaker that stops any future cycle of chained restarts after a few consecutive failures, instead of continuing indefinitely
• Updated the automatic monitoring (watchdog) script to work properly with the server management system, avoiding starting duplicate processes

Current Status: The server is running stable, the World Server and Auth Server are online, all ports are responding normally, and further checks have not reported any errors. We apologize for the inconvenience caused during this short interval!

Update applied: 2026-06-08 15:57