What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Official] Demonbuddy Auth after Banwave

Status
Not open for further replies.
"Once this is done, the bot will be as safe as we can make it and we will re-open auth. We hope it will be later today but it could take until Saturday."

that brings me to the question, whether there hasnt been done everything to make it as save as possible in the past?
 
"Once this is done, the bot will be as safe as we can make it and we will re-open auth. We hope it will be later today but it could take until Saturday."

that brings me to the question, whether there hasnt been done everything to make it as save as possible in the past?

Obviously perfection is hard to reach.
 
"Once this is done, the bot will be as safe as we can make it and we will re-open auth. We hope it will be later today but it could take until Saturday."

that brings me to the question, whether there hasnt been done everything to make it as save as possible in the past?


ofc,this doesnt mean that Blizz cant change things meanwhile or add new features
 
Im pretty sure the new releases of DB has a big role in this banwave

A friend of mine has botted 100 hours with .287 and he is not banned. My brother botted for 6 hours with .290 and he got banned. Meself was botting during two banwaves and i survived. This banwave got me and i was using the new db updates.

Theory about infceted db software i belive can be true as above.

Edit: If you use a new char in level 1 and you push "Force town portal" bla bla, it will make a town portal. Things like that should be fixed as its obvious to blizzard that you dont play with fair hand. Alot of the injects should be fixed. Like you can write in chat, move your mouse over things and mutch more without affect your running bot

I dont know how you made them to this but in my nooby mind i think blizzard can see such things. When the bot run it do it "beneath" user interface (you can write in chat etc). Also it can enter quests and mp without entering Quest selection. If your settings is 10mp in DB and its off or not the same as DB settings it should be flagged as something. How can you make a game on another MP then its set for? This is one of many things i think will reveal people botting

The game also freezes many times and laag but when you shutdown/stop DB it run smooth.
 
Last edited:
Also it can enter quests and mp without entering Quest selection. If your settings is 10mp in DB and its off or not the same as DB settings it should be flagged as something. How can you make a game on another MP then its set for? This is one of many things i think will reveal people botting.

I think that THIS was (maybe) the biggest reason for the bans.
 
so many ppl using the *****ed version, come on, do sth about this.
 
i used hacked version for a while bcos ppl said "we avoid banwave with it!" but its not true
 
Lol at thinking Blizzard knows when your inventory is open or closed or even cares. Why would they bother gathering that info client side and relaying it to server side? That information does them no good to have.

Way over analyzing here guys...

One town run, literally, one town run to unload inventory has enough automated timed based actions to flag you. Items are the one thing you can be sure they have solid logs for.
 
Lol at thinking Blizzard knows when your inventory is open or closed or even cares. Why would they bother gathering that info client side and relaying it to server side? That information does them no good to have.

Way over analyzing here guys...

One town run, literally, one town run to unload inventory has enough automated timed based actions to flag you. Items are the one thing you can be sure they have solid logs for.

We're analyzing what it does different from a human being, and those things are quite a factor when you compare it to a human being.
 
I think bans are based on very long investigation by blizzard, however I know they don't have enough employees to monitor all the accounts. I think part of the bot behavior cause botting accounts to be flagged. On the other hand I have seen *****ed version of demonbuddy which I think is one of the main reasons for the ban. They might also done this in a illegal way by *****ing Demonbuddy and test it out to see how it works and how it sends packet to the server etc.
 
I think bans are based on very long investigation by blizzard, however I know they don't have enough employees to monitor all the accounts. I think part of the bot behavior cause botting accounts to be flagged. On the other hand I have seen *****ed version of demonbuddy which I think is one of the main reasons for the ban. They might also done this in a illegal way by *****ing Demonbuddy and test it out to see how it works and how it sends packet to the server etc.

I don't think the investigations are 'very long', I've seen people being banned within hours. I, myself, have been banned within the space of a week.
 
be coz of the *****ed version available, it makes DB so commom and blizzard found it easy to deal with its botting pattern!
 
130n I think they are investigating since one or two months ago and gather enough evidence to prove that certain accounts are botting they can't just ban you like that. Myself I stopped botting for a week and still got banned on 18/12/12 and I know people who even stopped botting a month ago and still got banned which means they have been developing some kind of method and solid proof to ban all these accounts. Your account was banned within a week and people banned in hours because 18/12/12 was the scheduled day for the banwave so if you run the bot on the 17/12/12 you will get ban within a day. I hope you understand me
 
We're analyzing what it does different from a human being, and those things are quite a factor when you compare it to a human being.

And again, why would blizzard gather up and send every client side action of every millisecond to the server even if the server is agnostic to those actions? Big waste of packets and information gathering that slows connection speeds and play response times and dramatically increases blizzard server load. The server has no reason to know those actions. There are far easier things for which to catch us.

Outside the obvious mistakes like using a townportal before it is unlocked... I would guess that they are flagging accounts based on item actions. Items have solid logs.

Immediately picking up an item after it hits the ground.

The same incremental delay between selling items, or clicking repair after selling items is completed.

The same incremental delay between identifying items.

I used to work for NCsoft and the thing we banned people for the most on the game I worked on was auto deleting of items. Bots always auto deleted unneeded items 5seconds after obtaining them. So easy to catch in the logs.
 
Last edited:
And again, why would blizzard gather up and send every client side action of every millisecond to the server even if the server is agnostic to those actions? Big waste of packets and information gathering that slows connection speeds and play response times and dramatically increases blizzard server load. The server has no reason to know those actions. There are far easier things to catch us for.

I don't think you understand what's going on here. Whether we wanted or not, these packets are already sent to them. Which means it's quite easy for them to analyze it, hell, a script kid could make a code to analyze the packets if you know what you're looking for (non-human behavior). The alternative to that is detection, which I refuse to believe.
 
I think they implemented server side data collection about 4 weeks ago when they started the updates to "login" and bnet. Then last week with the patch implemented the tools to carry out the mass bans based no the data collected thus bans galore.

I think something like this would explain the grace period some had, and then also explains why these newer bans came quicker (now collection and bans both working together simultaneously). The people not getting banned are not getting flagged for whatever reason, maybe just luck or lack of processing power by blizzard.

I think the new algorithms are to replace the old gm's looking into flagged accounts to speed up the process tremendously and save them time/effort = $.

So i guess the question db devs and everyone else should be asking is ... what gets you flagged? consistent TPS? items per hour over set time frame? GPH? time played? clicking stuff not on screen? Maybe its all of them. No idea how you figure out which it is tho ... good ole fashioned trial and error? =/
 
I don't think you understand what's going on here. Whether we wanted or not, these packets are already sent to them. Which means it's quite easy for them to analyze it, hell, a script kid could make a code to analyze the packets if you know what you're looking for (non-human behavior). The alternative to that is detection, which I refuse to believe.

Again, it is far more simple than that. The way the bot handles items is easy to detect automation from. It was the first glaring flaw I saw in the bot day 1.

All of my accounts that survived, had not picked up any items. They were running level profiles from 1-60 and stopped at 60. They picked up zero items (unless I manually picked one up for it) so they never once did an ID or sell run. Surely they repaired a few times, but that alone is nothing without a log of selling 15 items at a half second delay between sells followed by a repair only .25seconds after the last item sold.

My accounts that got banned, even the freshest ones, had been farming items in Act3 and had used the same leveling profiles as the ones that survived because they stopped at 60 and hadnt started farming items yet.

Items items items. You can count on blizzard to keep good item logs, cause they need those for CS either way, regardless of bots.
 
Last edited:
Status
Not open for further replies.
Back
Top