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

1/3 Banned just now

no they have ignored my suggestions for it because they could care less about updating it to be safer. They will tell you botting isn't safe you will get banned. Well sure when your bot makes it obvious what you're doing.




its common sense that if you wont lose your acc you shouldnt bot
as there are always possibilities to get banned


its not rocket science


about your suggestions
who told you that your suggestions are correct and we are going to adopt them?
how comes you know better about warden safety etc?
 
Last edited:
You were botting 24/7 and supervising it 80% of the time? so for 19.6 hours a day you supervised your bot?

BTW IB uses hacks, and ALOT of people on the recent banwave (about 70%) were/had used IB the last week
 
no they have ignored my suggestions for it because they could care less about updating it to be safer. They will tell you botting isn't safe you will get banned. Well sure when your bot makes it obvious what you're doing.
You are fully able to make a pretty random profile easly. You could add unsafeRandomDistance to the moveto tags and you can use DBE use make a coinflip which route to take... You cant blame it on developers or ever the DB team because its there...
And if i were blizzard and i was going to ban people, i would go after profiles or time or anything like that. I would go after things that applys for both ah botting and botting the play. ECONOMICS! Ive stated this over and over. People doesnt seem to understand how easy it is to find cheats in a game based on economics! How do you think the goverment find people who cheat with economics in real life? Figure that out if you can...
 
You were botting 24/7 and supervising it 80% of the time? so for 19.6 hours a day you supervised your bot?

BTW IB uses hacks, and ALOT of people on the recent banwave (about 70%) were/had used IB the last week

yah ... 80% , My brother works during the night and I use the PC during the day.

I know how IB works ... I've been using IB since day 1 ...
 
its common sense that if you wont lose your acc you shouldnt bot
as there are always possibilities to get banned


its not rocket science


about your suggestions
who told you that your suggestions are correct and we are going to adopt them?
how comes you know better about warden safety etc?

He never said that.

However, since the recent bans seem to be hitting specific profiles, clearly they are detecting a pattern of sorts in the profile and/or bot. If it was strictly the combat routines, entering and leaving the game, games per hour, etc. then you would see a lot more bans than just specific profiles. Hence, it seems logical that they are running some profiling on specific zones and if they see you do the same thing 100% of the time over X games it has to be a bot.

Personally, I randomize all my profiles and run at least 6 variants at any time, switching zones and variants every couple of hours. It would be nice if DB would take any given profile and automatically randomize any x,y,z moveto statements as well as any waitTimers. Maybe you don't think it helps, but it doesn't HURT and it's not that hard to do.

If you guys truly know how warden works and insist that running any profile is not inherently detected, then why are we seeing any bans for folks running 4 - 6 hours? Running the same long running zone over and over is humanly possible for 4-6 hours. You don't see people complaining about getting banned doing that, that weren't running a bot. I can see anyone running 24/7 being at high risk no matter what, likewise if you hit the input limits, but I am a bit surprised to see anyone running 4-6 hour LONG profiles and getting banned.

Bottom line is the more you run a profile the greater the chance that they detect a pattern. Eliminating all patterns is important.
 
He never said that.

However, since the recent bans seem to be hitting specific profiles, clearly they are detecting a pattern of sorts in the profile and/or bot. If it was strictly the combat routines, entering and leaving the game, games per hour, etc. then you would see a lot more bans than just specific profiles. Hence, it seems logical that they are running some profiling on specific zones and if they see you do the same thing 100% of the time over X games it has to be a bot.

Personally, I randomize all my profiles and run at least 6 variants at any time, switching zones and variants every couple of hours. It would be nice if DB would take any given profile and automatically randomize any x,y,z moveto statements as well as any waitTimers. Maybe you don't think it helps, but it doesn't HURT and it's not that hard to do.

If you guys truly know how warden works and insist that running any profile is not inherently detected, then why are we seeing any bans for folks running 4 - 6 hours? Running the same long running zone over and over is humanly possible for 4-6 hours. You don't see people complaining about getting banned doing that, that weren't running a bot. I can see anyone running 24/7 being at high risk no matter what, likewise if you hit the input limits, but I am a bit surprised to see anyone running 4-6 hour LONG profiles and getting banned.

Bottom line is the more you run a profile the greater the chance that they detect a pattern. Eliminating all patterns is important.
unsafeRandomDistance...
nuff said
 
those of you guys that were banned running CORE + FOS, whos profile did you use and which version of that profile?

thanks!
 
unsafeRandomDistance...
nuff said

is the usage unsafeRandomDistance="15" and then it will pick some random distance within 15 of the given moveTo statement? I tried it out and I can't tell if it is working or not. The logs still show the exact x,y,z specified in the moveto.



Update: got it working. It appears the attribute needs to be the last attribute of the moveto tag. I also changed it to 10 instead of 15 and it appears to be working now.
 
Last edited:
is the usage unsafeRandomDistance="15" and then it will pick some random distance within 15 of the given moveTo statement? I tried it out and I can't tell if it is working or not. The logs still show the exact x,y,z specified in the moveto.



Update: got it working. It appears the attribute needs to be the last attribute of the moveto tag. I also changed it to 10 instead of 15 and it appears to be working now.
Told you!
 
Can I see a example .xml with this unsafeRandomDistance in it? so I can see how it is done? ty.
 
Here is how the tag needs to look:

<MoveTo questId="1" x="2937.846" y="2360.149" z="0.1002804" pathPrecision="7" unsafeRandomDistance="15" />
 
wouldnt be hard for blizz to track a bunch of accounts doing the same thing over and over, and then they use similar pathing....

i dont get why everyone is still using these stupid ways of botting.

champion farming all the way.
 
wouldnt be hard for blizz to track a bunch of accounts doing the same thing over and over, and then they use similar pathing....

i dont get why everyone is still using these stupid ways of botting.

champion farming all the way.

Ya because people haven't been banned using champ farming. /sarcasm off.
 
Ya because people haven't been banned using champ farming. /sarcasm off.
Since no one have yet reported that they leveled a account by hand, had their account never linked to other already banned accounts and only been using any of the champion farming profiles.
If you look the last 5 pages ALL ban reports are either leveling or GPH! Some bans when they used champ hunt, but had recently used sarkoth.
So you can be as sarcastic as you want.
 
Since no one have yet reported that they leveled a account by hand, had their account never linked to other already banned accounts and only been using any of the champion farming profiles.
If you look the last 5 pages ALL ban reports are either leveling or GPH! Some bans when they used champ hunt, but had recently used sarkoth.
So you can be as sarcastic as you want.

And you can make excuses and pretend any botting is safe all you want.
 
And you can make excuses and pretend any botting is safe all you want.
Well since we have a huge amount of people doing different champ hunting profiles and ONLY GPH profiles gets banned. I dont see your point here?
 
setting a higher pathPrecision as well as increasing your kill and loot radius will also create more random movement in scripted path profiles...

They added the unsafeRandomDistance based on a thread I made as well as others crying; they listen but they aren't going to hold your hand and they aren't going to do something because one person asked for it. To have a new feature added the feature should add more than it takes away, make sense, and be something the team or community deem a worthy task....

saying I told them blah blah blah isn't going to work in your favor or in favor of your "feature" even if the buddy team is pretty tolerant of trolling

anyway do you blame the car dealer when you crash the car? no, only under very specific cases can you blame them. To the best of my knowledge there is only one case where we can blame DB and that is when warden detects and bans everyone by detecting the injection and hooks used to psh pop jmp etc
 
Back
Top