gpgoodpeeps
New Member
- Joined
- Oct 28, 2012
- Messages
- 14
- Reaction score
- 0
My cousin was banned what seems like guilt by association.
Can we start botting again or we should wait for a message from the devs?
- Thread starter zeelive
- Start date
- Status
euroasian80
New Member
- Joined
- Dec 12, 2012
- Messages
- 21
- Reaction score
- 0
i can confirm it was the case for me.. 5 account s were botting when they all got banned, while i was setting my 6th which was botting 24/7 but not yet after the blizz patch..so i ll have some balls and say " fuck u DB" ..Hey i paid 2 more 3 x sessions after losing 5 accounts so dont bann me
.. some1 had to say the truth since DEVS nowhere to be found..not like we gonna sue u for it..
.. some1 had to say the truth since DEVS nowhere to be found..not like we gonna sue u for it..Fozzybear42
New Member
- Joined
- Dec 13, 2012
- Messages
- 11
- Reaction score
- 0
I think they are made by the same company. I could be wrong....
Reasons i am sure DB was the cause of the Bans:
1: All other bots had no ban reports
2: .288 before patch, .289 bugged out 4 hours later, .290 6 hours later ban wave, .291 now 24 hours after wave.
3: DB crashes, error logs, packets.
4: 200+ ban reports in 1 day DB software 0 reports in other software.
I think that the devs messed up packets got sent, people got banned. People mess up tho, coding is tricky and can lead to stuff like that. Personally tho, If the devs admitted to a mistake like this, sure it costed people money and more problems, But at least there would be some honesty regarding what exactly happen. Me and a few others have brain stormed for hours trying to figure out exactly how the ban wave started, what triggered it and why. Conclusions: A: people got banned non banned got flagged for next wave. B: people hit by the wave were all running DB not other software which no wave has detected.(By all means not saying there software is better, Like i said people do mess up and little mistakes cause problems but everything can be fixed) C: battle.net port opener manual scans, But if this were the case DB users would have not just been the only target. D: 3 versions released within 2 days.. during a ban wave and a buggy DB release.
Regardless of what has happened, If it was a mistake made with demonbuddy, the devs should respond to questions on why. i think it would be a lot more assuring if something like: Dev: yeah sorry guys there was a glitch in 1 one of our DB versions which repeatedly sent a packet to blizzard allowing them to target DB users and create a banwave, But be assured we have fixed this problem and we are sorry for your loss. was said.
You know just anything would be nice to hear about what actually happened.
Also, To the people that say that if it was a DB detection they would have banned everyone.. You are 100% wrong, They ban 40-60% of db users never 100%, and why they do this is for game resales, Gold prices to go up so more is sold on RMAH and game activity increases. If they were to ban 100% of all botters/db users less sales would happen, less game activity and RMAH plumit. And its not just DB that goes for any bot...
Sorry about the rant and the long post, Just kinda voicing my oppinion on the situation.
Now .291 is released im bot running again, before this release it wasn't worth the chance.
1: All other bots had no ban reports
2: .288 before patch, .289 bugged out 4 hours later, .290 6 hours later ban wave, .291 now 24 hours after wave.
3: DB crashes, error logs, packets.
4: 200+ ban reports in 1 day DB software 0 reports in other software.
I think that the devs messed up packets got sent, people got banned. People mess up tho, coding is tricky and can lead to stuff like that. Personally tho, If the devs admitted to a mistake like this, sure it costed people money and more problems, But at least there would be some honesty regarding what exactly happen. Me and a few others have brain stormed for hours trying to figure out exactly how the ban wave started, what triggered it and why. Conclusions: A: people got banned non banned got flagged for next wave. B: people hit by the wave were all running DB not other software which no wave has detected.(By all means not saying there software is better, Like i said people do mess up and little mistakes cause problems but everything can be fixed) C: battle.net port opener manual scans, But if this were the case DB users would have not just been the only target. D: 3 versions released within 2 days.. during a ban wave and a buggy DB release.
Regardless of what has happened, If it was a mistake made with demonbuddy, the devs should respond to questions on why. i think it would be a lot more assuring if something like: Dev: yeah sorry guys there was a glitch in 1 one of our DB versions which repeatedly sent a packet to blizzard allowing them to target DB users and create a banwave, But be assured we have fixed this problem and we are sorry for your loss. was said.
You know just anything would be nice to hear about what actually happened.
Also, To the people that say that if it was a DB detection they would have banned everyone.. You are 100% wrong, They ban 40-60% of db users never 100%, and why they do this is for game resales, Gold prices to go up so more is sold on RMAH and game activity increases. If they were to ban 100% of all botters/db users less sales would happen, less game activity and RMAH plumit. And its not just DB that goes for any bot...
Sorry about the rant and the long post, Just kinda voicing my oppinion on the situation.
Now .291 is released im bot running again, before this release it wasn't worth the chance.
Last edited:
- Status