Updates

1.7.35 passed --path to Burralis. Burralis then exited without starting Wow, and IceDNicco froze for 90 seconds waiting. 1.7.36 opens Burralis from the 12.1 folder the same way as a double-click (no arguments) and returns immediately. Close the old launcher, download 1.7.36, or run D:\Games\12.1\IceDNicco-start-12.1.cmd.

1.7.34 started Burralis from _retail_. That folder has Wow.exe but no .build.info, so Wow never appeared. 1.7.35 starts Burralis from the 12.1 folder (next to .build.info) and passes --path to that same folder. Close Wow, Burralis and the old launcher, then download 1.7.35 and press Play. Or run D:\Games\12.1\IceDNicco-start-12.1.cmd.

Login and the realm list worked, but clicking IceDNicco kicked you back. Retail 12.1 speaks TLS to the world port; Trinity expects the V2 plaintext handshake. Burralis must run from _retail_ next to Wow.exe so it hooks that socket. 1.7.34 starts that copy. Or run D:\Games\12.1\_retail_\IceDNicco-start-12.1.cmd.

The 12.1 login screen stayed up but rejected the site password (error 2147483965). The portal stored Battle.net verifiers with the wrong SRP identity (email instead of SHA256(email)) and SRP v1. It now writes Trinity SRP v2, the same as bnetaccount create. Log into wow.icednicco.online once, then log into 12.1 with the same email and password.

12.1 did not stay up after the bnet RSA cert was reissued on the YR1/Root YR chain — Burralis saw the portal offline and Wow died on the login screen. bnet :1119/:8081 now uses the same trusted site ECDSA certificate as wow.icednicco.online. Launcher 1.7.33 starts Burralis from the 12.1 folder (next to .build.info) with Explorer, no cmd pipe. Login = site email + password.

Windows Schannel failed to read the Battle.net certificate from :8081/:1119 (Let's Encrypt Root YR), so Burralis kept a stale pin and reported the portal offline. 1.7.31 downloads the live leaf from https://wow.icednicco.online/client/t12-bnet.pem (normal HTTPS) and waits to confirm Wow.exe stays up after Burralis's portal check. Update the launcher, close Wow/Burralis, then Play. Do not start Burralis.exe yourself — use Play so --dev true is set.

The realm was segfaulting after players (especially raid leaders) sat in a 25-man with bots. Lua kept walking all 2000 bots and mass-summoning the raid every 25 seconds, including teleports to Z=-200000. Resume now runs only after login / a world boot, skips a raid that is already together, and rejects insane coordinates. Living-world bots are now 3000, spread across 1–80 so every leveling band has company.

1.7.29 turned Burralis developer mode off. Burralis then reported wow.icednicco.online:1119 as offline (Windows does not yet trust the new Let's Encrypt Root YR). 1.7.30 starts Burralis in developer mode and pins the live server certificate. Update the launcher, close Wow, then Play.

Burralis was started in developer mode and pinned an old certificate, so the 12.1 client disconnected after the login form. 1.7.29 starts Burralis with a public certificate (--dev false). Update the launcher, close Wow, then Play. Login is the same email and password as the site.

Freedom transfers and existing Death Knights now complete the Ebon Hold class quests and learn every trainer spell for their level (Death Gate, runeforging, presence ranks, and the rest of the book).