Tony
"The Bee"
- Joined
- Jan 15, 2010
- Messages
- 128,830
- Reaction score
- 570
197 accs are like a drop comparing them with the total session number
197 accs are like a drop comparing them with the total session number
choose to proceed with that information is up to them.
There's a major difference between patterns "detection" and actual program detection. When they detect the bot itself, warden will roll out with automatic bans. You've never been banned by Warden before, have you?
197 accs are like a drop comparing them with the total session number
197 REPORTED accounts. Why would someone assume everybody is reporting their bans is beyond me.
That being said, this banwave was minuscule....but I also remember 1 similar size banwave before the big Doomsday of december......cross your fingers!
Not everyone being banned doesn't mean DB couldn't be detected.
I'm not saying Blizzard would do the logical thing in any situation, but banning everyone when DB is detected is beyond the stupidest thing they could do (and you arguing that Warden does that is also rediculous; programming delayed timing bans into warden is entirely possible).
Ya, we should let the botting community live in fear, shut down their bot for updates, and kill purchasing of d3 copies by mass banning everyone at once.
Or.. they could trickle them through, so some people make a small profit, and there is a lul to continue to bot as there is hope of a profit. People would re-purchase d3 every so often to bot again and DB would never update it's detectability because there doesn't seem to be a flaw.
(I know in the past WoW had mass bans but diablo 3 is a different team employing different business strategies in all facets of the game).