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

Wasn't Demonbuddy supposed to be the ''safe'' bot?

if a player runs lets say a Sakroth run,and the run time is 45 seconds every time
is not hard for Blizz to find out that you are using something automated,they dont need to check if you are doing it for days or for an hour

also,you will see many threads here from people telling that they got banned within 15-20 mins,this doesnt mean that its always true
dont forget that we can track everything about our products as well(including a session runtime)

So you probably know how many Sessions stopped after the banwave and you also know it is way more than the reported bans.
 
Although DB is a great bot, very safe when not over used as well as great support. I feel it lacks a few things which are needed to make the bot fantastic. These things would include; automatic profile switching to prevent easy detectability, and also more profiles.. So many Sark/Core/Goblins... it'll get suspicious.
plugin section "profile restarter" it does randomize profile
 
db is not save. with ib you can run core 24/7 a day 40sec games and instant logout and nobody who ran immortalbot only got banned yet. i dont know what it is but db right now is not safe. its not safe to run autoit script also wich im sure doesn't realy change any files of d3 too. so its up to the buddy team to fix this. right now its not safe even if you pretend it to be and it has nothing to to with your 24/7 hour farming complains.
 
As far as i've heard IB is down.

We cannot comment at this time and we will do so as soon as we can. We know this is not ideal

It doesnt make much sense if they let the bot go even when their site is down, it also doesnt make much sense if YOU continue to use the bot when their site is down. Not sure the situation but

Feels like trolls trying to advertise IB...
+1
 
db is not save. with ib you can run core 24/7 a day 40sec games and instant logout and nobody who ran immortalbot only got banned yet. i dont know what it is but db right now is not safe. its not safe to run autoit script also wich im sure doesn't realy change any files of d3 too. so its up to the buddy team to fix this. right now its not safe even if you pretend it to be and it has nothing to to with your 24/7 hour farming complains.

like the rest said, quit trolling, IB bans are all over the place you tool.
 
As far as i've heard IB is down.

It doesnt make much sense if they let the bot go even when their site is down, it also doesnt make much sense if YOU continue to use the bot when their site is down. Not sure the situation but

+1

My IB bot is still running and has been running for 4 days and 9 hours without a single crash. (24/7)
 
I ran IB bot 24/7 for 3+ months in core - I was banned a few weeks ago on 6 accounts. It is not the bots that are detected (anyone with half a brain understands that) it is the method of botting that is detected. The delay in game creation is what makes the botting less likely to draw a ban.

The IB users currently running and not getting banned probably have a delay in game creation set up. IB had that function for months now which allows for a random interval in between game creation and a random interval for leaving a game also. DB is now attempting to do this also... it should hopefully cut down on a lot of the bans. I believe the bans will start to slow down now with people who are already flagged previously still getting banned.

The bans didn't start until Blizzard put in the game creation detection method - we were botting for months with no issues before that. Now it seems that since implementing that all botters are getting banned.


A good way for hawker to test this would be to write a bot script that did nothing but login, join a game, stay in it for 10 seconds, leave, make a new game, and continue to do this until the account is banned. If it leads to a ban then it is clear that it is game creation that leads to the bans and not game activity.
 
A good way for hawker to test this would be to write a bot script that did nothing but login, join a game, stay in it for 10 seconds, leave, make a new game, and continue to do this until the account is banned. If it leads to a ban then it is clear that it is game creation that leads to the bans and not game activity.

Interesting Idea
 
I bought DB (3 license when on sale) so I would use it when immortal bot got banned or no longer updated. My three immortal bots still going strong without any interruptions!

By the sounds of it something is wrong with DB, especially when people are getting banned after only a couple of hours. Hopefully they fix it so the community can continue to enjoy buddy products.
 
IB is not caught YET because Blizz is focusing on Sarkoth/ZK/Core mainly.

worng.

all bots are banned already.

some of my friends got banned also with IB.


one lost over 40 accounts on 2 banweave within 2 week.

24 and 17 accounts.

there's random bans not banning all like in d2 11.11.08 where over 400k account got banned.

you just had lucky.


also here some of my mates got banned too ( no ah abuse ) only core
autoit = banned
macro = banned
Ib = banned
hellbuddy = banned
demonbuddy = banned ( only me 1 acc of 12 )
 
Its hardly to believe for me too, that Blizz only detects the 30sec run routine... From what I heard, Immortal is still the safest one.. I have two buddy running this one too... My best guild friend is running Immortal since beginning of June on two accounts and since 3 weeks nearly 24/7 - he is doin exactly 45sec core runs... He survives every banwave...

Maybe it really has something to do with the really often D3 crashes, that DB produces?
 
They aren't banwaving bots, they are banning based on behavior. When everyone is using the same profile and it has absolutely no randomization in it, this is what happens. Make your own profile or urge your profile makers to improve their profiles. It isn't a demonbuddy issue.
 
They aren't banwaving bots, they are banning based on behavior. When everyone is using the same profile and it has absolutely no randomization in it, this is what happens. Make your own profile or urge your profile makers to improve their profiles. It isn't a demonbuddy issue.

Oh look, someone with a brain.

IF Demonbuddy WAS detected, there would be a hell of a lot more bans at any given point. I know there seem to be a lot already now, but if it was a true detection; we'd see an actual banwave -- much like what happened to glider in 2008 (i think that's the right date).

Furthermore, look at the facts here. They did Autoit/AHK banwaves; bots that are impossible to detect with with Warden's current "restrictions". These programs themselves have zero interaction with the game itself; meaning there technically should be no way could be detected, other than by patterns. I'm not talking just AH bots here, i'm talking the Auto-it scripts for Sarkoth, zk, etc. If anyone doesn't that Blizzard isn't doing some in depth pattern detection then you are just an idiot. DB itself is NOT detected, it's people doing stupid shit that is. It's like saying a car manufacturer produces unsafe cars because some dumbass killed themselves while drinking and driving (or texting).

tyrone.webp
 
Last edited:
Well maybe they are to smart and dont want to take suspicius about detection...and make small waves...smart, pff.
 
Well maybe they are to smart and dont want to take suspicius about detection...and make small waves...smart, pff.

If they have the bot detected they don't want people botting so they will ban everyone flagged, and cause anyone who logs in with the bot to be instant banned. They aren't going to continue letting people "damage" the game.
 
You guys blaming profiles are absurd. Without random path generation we cannot make unique random profiles we have to make ones for STATIC areas and blizzard KNOWS this. This is a bot issue and DB has put us at a higher risk because of no random path generation.
 
Back
Top