User protection

[mty713]

Some demonbuddy users, including me, have fallen into the half an hour window, as a result of which, probably have been flagged by blizzard.

Just wondering is there any mechanism that demonbuddy could have to stop this happening again?

I mean why this window can not be even shorter, so next time even less users will be caught?

 

[samsmug]

Some demonbuddy users, including me, have fallen into the half an hour window, as a result of which, probably have been flagged by blizzard.

Just wondering is there any mechanism that demonbuddy could have to stop this happening again?

I mean why this window can not be even shorter, so next time even less users will be caught?

I was wondering what this new DB build has that already bypasses whatever the new warden does. Only took them a few hours to prevent detection with a new build? I've read the BosslandGmbH faqs and didn't see how...which makes sense bc then blizz would know too =P

Also OP, is there a log that shows exact log in and log out times for the last time you ran DB?

I've been trying to remember if I had it running. I know I was manually playing during that time but sometimes I leave DB open other turn it on to edit the itemlist, etc. Can't remember if I ran it during the window...


Edit - Are all the "log-in" logs kept here?

C:\Program Files\DemonBuddy\Logs


So if the last log I see in there before the Tripwire went in to effect is "2016-02-08 22:43:41,363 [1] INFO MainWindow (null) - Demonbuddy v1.1.2914.450 started" (Eastern Time Zone)

I guess I'm safe. But I'm not sure if that folder actually has a log for each time you connect to DBuddy.

 

[glmillz]

its fine if it was on during that window. just not started.

 

[magictiger]

I was wondering what this new DB build has that already bypasses whatever the new warden does. Only took them a few hours to prevent detection with a new build? I've read the BosslandGmbH faqs and didn't see how...which makes sense bc then blizz would know too =P

There are ways to hide what your process is doing from a specific detection method. The developers never know what Blizzard is going to try next, so it takes a little bit of time to see a new Warden update then go through it to discover what it's doing differently and what it's looking for. Depending on the methods used and how hard Blizzard tries to obfuscate it, it takes wildly varying amounts of time and effort. The techniques are similar to how security researchers handle malware analysis, which kinda makes sense as Warden does things that some malware tries to do.

For our own protection, the devs here don't post much in the way of details, but don't think that means Blizzard doesn't know what gets changed in the bots to evade detection.

 

[ChetanG]

Some demonbuddy users, including me, have fallen into the half an hour window, as a result of which, probably have been flagged by blizzard.

Just wondering is there any mechanism that demonbuddy could have to stop this happening again?

I mean why this window can not be even shorter, so next time even less users will be caught?

Blizzard does not always Ban or Suspend an Account for botting immediately. I have friends that were banned in game playing manually after the season was over and new patch had been released with no bot update available. It is as at times Blizz will wait and ban a number of accounts at same time.

 

[zepwin]

The smartest way to ban these flagged accounts would be wait til the season is over, and wait until the next season has about a week until it starts, then mass-ban the accounts. That way all of us would be motivated to buy new accounts.