EPT![[image loading]](http://i.imgur.com/051jGOO.png)
Clearly the brief amusement of my ~1000 readers is more important than the competitive integrity of the SC2 ladder. Another bone-headed move by Blizz!
In addition to this, my Battle.net or SC2 client or something managed to break in an extremely frustrating manner: SC2, despite being on the most recent patch, insisted that a) it needed to download an update, but b) it needed to wait for another game to update first (the only other game on the computer, Hearthstone, was up to date and made no effort to download any patch). Every time I tried to pause all other updates, move the SC2 update to the front of the queue, scan and repair SC2, or even uninstall the game, an error message informed me that Battle.net had encountered an error from trying to perform two actions at once, and referred me to a tech support page that essentially told me to 1) wait 15 minutes, and then 2) turn it off and on again. Once upon a time you could just boot SC2 directly by opening SC2Switcher, but apparently now it won't let you.
Ultimately I had to delete the program files of both Battle.net and Starcraft II and reinstall them to get it to work. Somehow my replays are still present, even if most of them don't work (where does it store them if not in program files?), but this has all set part three back quite a bit. Just an update for all two of you that actually read parts one and two and have been waiting for the next one.
In the meantime, though, I had a screenshot from one of my games in an (apparently) bugged SC2 client which has brought me a great deal of pleasure. I don't know how this was brought about; I assume somewhere in the code a signed int variable tried to decrement from 0, though I have no idea how I achieved this.
![[image loading]](http://i.imgur.com/GIoTvtQ.png)
You know, I've been working on keeping up with constant worker production, and I think I've really improved.
It fixed itself when the next workers rallied to that mineral line, but I was excited enough that I thought I'd share it in a blog. If anyone has encountered this before or has any idea how to recreate this bug, I'd love to hear it. Otherwise, I hope it delights you as much as it did me. Enjoy!
