It has been a pretty bumpy release, we admit that, and we are truly sorry about that. We read everything in the forums, and we do not take all the criticism lightly. The service we provide has not been usable for a lot of people, and that is unacceptable. We have been working pretty much around the clock since the release this Friday to make stability improvements, and we are finally seeing some improvements, but we are not done yet. That said, you can read Bossland's post for the motivation behind making these changes, and why it had to be done.
There are just a few misconceptions I need to clear up here:
Speaking for Honorbuddy, this is not true. Meshes are streamed at runtime. I will also bet that any other bot that uses a mesh system for navigation does the same.
It was not the actual streaming that was utilized in VAC for detection. They utilized the DNS cache, and only after something suspicious had already been found. If Blizzard wanted to go straight for the networking, they could detect you visiting
www.thebuddyforum.com, or you pinging our servers. This would be
massively intrusive - as you can see, it was a PR nightmare for Valve, and their detection was even less intrusive.
We have also used our auth servers for a long time, and as said, meshes are being streamed. If Blizzard wanted to go this route, they could have done it since the beginning of HB. Not a good argument, but a level playing field has to be assumed.
This is not true. We have multiple servers that are load balanced, and the servers are holding up to the load they are under. The problems are elsewhere - and we have identified them, and are taking actions to resolve them.
This is not how it is supposed to work. It should definitely be more than 3-4 steps between requests to that server. This is one of the things we are collecting data on and improving upon.
As said previously, you can read the motivations in Bossland's post.
In short: Sorry for the bumpy launch, it was obviously not intended to be like this. Right now we are working around the clock to get DB back to the same levels of smoothness as before patch 2.3.