Client launch crash and long loading times fixed — Warcrown now runs its own game data mirror

Over the past week players have been hitting one of three symptoms at launch:

1. ACCESS_VIOLATION crash window with a hash dump
2. Tact instance creation failed. Error (17): cdn hosts exhausted
3. The launcher or login screen sitting frozen for several minutes before anything happens

All three share the same root cause: the CDN that the WoW Classic 3.4.4 client originally downloaded its game data from has stopped serving the assets our build references. The client kept retrying every dead host on its list — eventually crashing for some, eventually giving up for others, and consuming the long wait time everyone noticed.

What changes for players

If you already have the client installed:

1. Open the launcher.
2. Go to the Settings tab and click Verify Integrity of the Game Files.
3. The launcher will detect the outdated binary and download the patched version. Once it finishes, launch and play.

If you're installing fresh, the launcher already pulls the patched version — nothing extra to do.

If something still breaks

Join our Discord server and open a ticket in the #support channel, mentioning a member of the @Developer role. Attach the crash log (<install>/Errors/*.txt — the most recent one). The first three log lines tell us exactly what failed, and most issues from this point should be one-line fixes.

Thanks for your patience while we rebuilt the data pipeline.