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

Ban Theory

Status
Not open for further replies.
I put this in the OP, which was my reasoning for this theory.

Edit, additional info:

The reason I thought of this is because the only accounts of mine that survived were using the full questing leveling profiles.

Ban wave 1 - 3/4 accounts banned, all 3 that were running BigRed, 1 that survived just hit level 60 at the time of the banwave and had only run the questing profiles.
Ban wave 2 - 1/2 accounts banned (I started up 1 new bot between wave 1 and 2), 1 that was banned was running BigRed (which was actually the account that survived the first banwave while it was questing), 1 that was not was also near lvl 60 running questing profiles.

The difference between the questing profile and BigRed is that the questing profile merely Resumes your game and doesnt actually create new games as specific quest intervals.

That could very well be true, however the questing bots seem to be very new in your story. Meaning they could also just not have been flagged yet, in which case it just doesn't prove anything.
 
The detection could probably be done through any of these things, especially by tracking patterns of extremely fast and efficient item pickup and item ID. However, I think it would make even more sense that the detection was done by allowing information to exist in the game that only a bot could read. Implanting invisible treasure goblins or legendary items could work if the bot was reading data that such a thing exists nearby but not paying attention to data regarding its physical appearance on the screen. Essentially, the item or goblin is given an invisible skin, while skins may not have been a previously analyzed factor (since there was only one option). Its what I would do to fool a bot.
 
guys, we dont need to act like Michael J. Fox omfg. its something completely different. just rumors going around with no case behind that lawl. i am botting since release . no bans yet. never ever. i am just lucky and when i get banned i am unlucky. thats all. ur Michael J. Fox ideas makes me sick how kids are stupid these days
 
guys, we dont need to act like Michael J. Fox omfg. its something completely different. just rumors going around with no case behind that lawl. i am botting since release . no bans yet. never ever. i am just lucky and when i get banned i am unlucky. thats all. ur Michael J. Fox ideas makes me sick how kids are stupid these days


\

supertard.jpg
 
My 2 cents...At the last db update a wait timer has been added to db whenever you townportal, use a waypoint etc. to prevent bot from trying to perform an action while still trying to tp or do something else. I think the time that these wait timers allow to pass is the same every time...If I observed it correctly blizz could have searched for accounts that stay idle that amount of time after tp or use waypoint (for more than let's say 10 times per run to rule out legit players who might by mistake do that). It's an easy and extremely effective way to get us all since all demonbuddy programs do exactly the same thing. Also if they needed the bot to do this let's say 12 times per run to make sure it is not a legit player, it would explain why some gold farming bots in hell that do very short profiles (FoS + core of arreat for example) got away with it since they do not teleport enough times between entering and exiting the game. If I am thinking something wrong or some of my observations are wrong please correct me :) Let's hope buddy team can figure out what happened and how they got us!!
 
This banwave does appear to be a direct strike against Demonbuddy. I'm sure that if this was their objective, there are several signature patterns used by all Demonbuddy bots that could be tracked. I guess it was only a matter of time before they turned their focus and energy to tracking down the DB botters. Its probably not even that hard to do once the proper resources have been allocated to the task.
 
Status
Not open for further replies.
Back
Top