Search Results
8/6/2025, 7:39:26 PM
>Password Reset/Account Management:
This is a priority today. The account management page just needs to be pointed at the new DB hosts and tested before it's live. (not acc creation, just management)
>Poll Status and Pruning:
No, we're not just sitting around waiting for the poll to end the results are already pretty clear, so work on the prune queries is starting today. That said, the poll is harmless to let run (maybe it flips, who knows, if it does, fine, no prune). We can't just crank the prune immediately because we're prepping a new patch to ship first.
>Complaints About "Nothingburger" Updates and ETAs/Technical Details:
People wanting constant ETAs and deep technical details are being entitled. ETAs only come from actually working through the problems (it took a while just to identify the bottleneck and if it could even be solved). Giving ETAs would basically mean intentionally providing wrong info, then reverting on it day after day.
>Launch Timing:
We're not giving a fixed launch time on purpose, one of the worst things would be repeating the "everyone log in at X time" rush. Once the next patch ships, we can switch on basically anytime we want, with a semi-slow trickle the first hour or two to manage load. The aim is simply ASAP; we're not artificially waiting. Assume the server isn't going up until you see a patch hit the launchers (including for the new starting areas).
>Why Not Launch Yesterday/Starting Zones:
Nope, we couldn't have just started servers yesterday after tests, the 24h poll was opened, but starting zones have been in the works since like 2 days into the server issues (different teams: those folks aren't server engineers). Spreading out starting zones reduces server load anyway, so it's a win-win. Paths converged by happenstance. A patch was going out either way for bug resolutions, more blizzlike/custom creature dynamic spawns, etc. If we're doing a "relaunch" might as well include them.
This is a priority today. The account management page just needs to be pointed at the new DB hosts and tested before it's live. (not acc creation, just management)
>Poll Status and Pruning:
No, we're not just sitting around waiting for the poll to end the results are already pretty clear, so work on the prune queries is starting today. That said, the poll is harmless to let run (maybe it flips, who knows, if it does, fine, no prune). We can't just crank the prune immediately because we're prepping a new patch to ship first.
>Complaints About "Nothingburger" Updates and ETAs/Technical Details:
People wanting constant ETAs and deep technical details are being entitled. ETAs only come from actually working through the problems (it took a while just to identify the bottleneck and if it could even be solved). Giving ETAs would basically mean intentionally providing wrong info, then reverting on it day after day.
>Launch Timing:
We're not giving a fixed launch time on purpose, one of the worst things would be repeating the "everyone log in at X time" rush. Once the next patch ships, we can switch on basically anytime we want, with a semi-slow trickle the first hour or two to manage load. The aim is simply ASAP; we're not artificially waiting. Assume the server isn't going up until you see a patch hit the launchers (including for the new starting areas).
>Why Not Launch Yesterday/Starting Zones:
Nope, we couldn't have just started servers yesterday after tests, the 24h poll was opened, but starting zones have been in the works since like 2 days into the server issues (different teams: those folks aren't server engineers). Spreading out starting zones reduces server load anyway, so it's a win-win. Paths converged by happenstance. A patch was going out either way for bug resolutions, more blizzlike/custom creature dynamic spawns, etc. If we're doing a "relaunch" might as well include them.
Page 1