290 is the culprit?

[demonbading]

apparently, common denominator is db v290 as the culprit
so is 289 safe?

 

[kager0]

its the other way around !!

 

[qwerq]

I'm going strong with all 6 of my bots with .289 atm.

 

[kager0]

I'm going strong with all 6 of my bots with .289 atm.

It's Eu?

 

[carlok]

I think not about the db 290, possibly 1.0.6a is the problem

 

[miracle]

290 and 24/7 didnt get banned

 

[JoshYoJoshYo]

290 and 24/7 didnt get banned

289 was what I was runnin24/7 and got banned

 

[Behla]

.290 and max 10h / day - not banned

 

[JimJohnsonBanMe4life]

apparently, common denominator is db v290 as the culprit
so is 289 safe?

You do realize that they most likely had you flagged for ban BEFORE v290. So you are talking out your ass with no basis for real solid information.

 

[demonbading]

like you know the real reason jerkoff!

 

[fr3357]

it has nothing to do with the version most likely it is just blizzard finally catching up to tickets that needed to be cleaned out of the "should this be banned" section for employees, its not something that is profitable to pay someonee 24/7 to be working on bans, so more or less its likely decisions get passed down when the ban tank is getting full and then GM's go and sort it out is all. Then again NO ONE knows the truth, probably not even blizzard because alot of it is done via warden, I am sure they have a statistical management system in place that logs flag types and for what.

 

[Tony]

has nothing to do with DB build version


closed