PrimordialWoW - News

Scheduled Maintenance Important

⚙️ Network Notice: Official Server Maintenance & Stability Schedule Classification: Infrastructure Update Target Architecture: Dev-Ops Systems / Player Operations To ensure peak network performance, clean instance resets, and maximum database integrity, PrimordialWoW follows a strict, automated maintenance loop. Because we pull updates directly from active source repositories, our update pipeline requires structured building time to compile new server engines. Below is the operational schedule for our live realm: 🔄 1. Daily Rolling Realm Restarts (Every 24 Hours) Schedule: Automated execution every day at 04:00 AM [Server Time]. Downtime Duration: 2 to 5 minutes. Purpose: Clears system memory allocation loops, flushes temporary character instance states, resets world creature nodes, and backs up core acore_auth and acore_characters tables to our local secure storage volumes. A 15-minute warnings broadcast (.announce) will automatically fire in-game before shutdown. 🛠️ 2. Weekly Core Upgrades & Extended Maintenance (Every Sunday Morning) Schedule: Every Sunday morning from 03:00 AM to 07:00 AM [Server Time]. Downtime Duration: Approximately 3 to 4 hours. The Compilation Pipeline (Why it takes time): PrimordialWoW does not use outdated pre-compiled binaries. To deploy performance patches, database updates, and changes made to our .conf configuration files, our pipeline executes a full structural build: Source Synchronization: The system connects to the main development repository to securely fetch the latest source code additions. CMake Architecture Generation: System dependencies and custom modules (like the Dungeon Master module) are structurally re-mapped. C++ Compilation Lifecycle: The server machine utilizes its multi-core processor layout to completely build fresh, optimized copies of authserver.exe and worldserver.exe using MSBuild/Visual Studio engines. Database Migration Hooks: Any new structural updates or item columns are safely integrated into the world databases before boot. 💾 3. Critical Policies You Might Have Missed (Added Frameworks) As the server operator, we have added these standard industry protections to your weekly pipeline to safeguard player data: Automated Cold Backups: Right before the Sunday compilation phase triggers, a complete compressed backup snapshot of the player database is generated. If a bad code update ever corrupts character inventories, we can roll back instantly with zero data loss. Database Optimization Cycle (DB Optimization): During the Sunday window, our SQL storage engine runs an automated optimization script (OPTIMIZE TABLE) to clean up log rows, clear deleted auction indices, and lower cross-network latency. Emergency Maintenance Protocol: In the rare event of a game-breaking exploit or physical hardware emergency, the team reserves the right to drop the network line for hotfix injections. Flash updates will be posted instantly to our official Discord community channels. Thank you for your patience and dedication while we build the most stable, high-performance Wrath of the Lich King playground in the community!