Fisher67
Member
- Joined
- Jan 27, 2016
- Messages
- 229
- Reaction score
- 6
Source: http://us.battle.net/d3/en/forum/topic/20742865671?page=6#118
Lots of speculation going around, so here are the best guesses. Beyond these, no one truly knows what's going on except Blizzard employees.
A lot of this is psychological warfare. That's why Blizzard uses ban "waves" instead of doing it as they detect it. Don't pay any attention to that. Botting is a risk. If you can accept the risk, then simply trust the DB developers (again, if the program was truly detectable, there would be a lot more ban reports, probably hundreds.)
Botting is about having fun, don't let paranoia spoil that fun.
Update:
Lots of speculation going around, so here are the best guesses. Beyond these, no one truly knows what's going on except Blizzard employees.
- Based on the reports, this is a relatively small, surgical ban wave (can infer from this that DB itself is not currently detectable, which means Blizzard is resorting to other detection methods like looking for certain account behaviors)
- In this ban wave, many of those who were banned were 24/7 botters
- Highly ranked players are clearly being targeted/scrutinized by Blizzard for botting activity
- The botters who were exposed on the wrong side of the tripwire earlier in 2016 were apparently banned
- A number of TurboHUD users were detected
- Seeing more seasonal ban reports than non-seasonal
A lot of this is psychological warfare. That's why Blizzard uses ban "waves" instead of doing it as they detect it. Don't pay any attention to that. Botting is a risk. If you can accept the risk, then simply trust the DB developers (again, if the program was truly detectable, there would be a lot more ban reports, probably hundreds.)
Botting is about having fun, don't let paranoia spoil that fun.

Update:
there is no software detection and there is no DB banwave
Last edited: