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

Ban Theories and Ban Waves

Is it just me or does it seem like 8/10 bans people are running AGB? DB is not detecable but maybe something the AGB does/leaves in memory autoflags.

BTW changing the game name, also changes one of its tags of running processes. I have mine changed to AOL instant messenger for that exact reason. Prob doesn't do anything but it cant hurt

:rolleyes: sigh, you dont think just VAULTING everywhere over and over again for 150games per hour gives it away???
 
:rolleyes: sigh, you dont think just VAULTING everywhere over and over again for 150games per hour gives it away???

DH weren't the only people/class banned. plus to think everyone is using the same combat profile is silly.
amount of games per hour is a different story. 150/hr is asking for it anyways
 
but there was no ban wave at 02 / 03.08. at night or?

i "only" see 15 ban threads today -.-
im sorry for all that been hitted ;-/
in the morning at 6 o?clock there was a announced server restart -.- my stomach felt a bit strange...before i saw all these ban threads -.-
 
We will see more bans today once people wake up, but my guess is from looking at the ones now most will be from Sarkoth and some from Champion. Just waiting on mine to get hit for doing core 24/7. Kind of ironic, but I fell asleep last night without turning them on.
 
people gettin banned so fast within a few hours on a fresh accounts leads me to wonder if the diablo client / agent.exe / etc, is sending information to blizzard? And if so, what kind?

What I'm wondering, is if each Diablo client has a unique ID attached to it, so even if we hide behind different VM, PVN, mac address, they will still realize that it's a botter making new accounts and logging in from the same location.

so after your first ban, it would lead to quicker future bans because you've already been flagged.


People are getting banned way too fast, on every profile, and every kind of bot. I've read so many different reports...

They've got to have some efficient way of detecting us because it is definitely not random.
They have a paid team who specialize in deterring cheaters, and these people aren't just sitting on their ass doing nothing. They are actively coming up with methods to combat us, it's sad that they are always a few steps ahead of us, and any notion of random bad luck is just their way of throwing us off and to keep us guessing.

edit: i mean, how else do exploits and bugs get hotfixed so fast? No doubt they are scanning cheat/bot forums for information daily.
 
Last edited:
so after your first ban, it would lead to quicker future bans because you've already been flagged.

You mean flagged via association to the Main account + Paypal account (since it's the only way to sell legit on the RMAH).

I had less problems with World of Warcraft when selling gold to China Agents.
 
Alot of people who got banned and re-bought accounts seem to be getting banned again straight after even after going thru the effort of changing i.p, hwid, etc.
There must be some information getting sent to the server we are missing..
 
You mean flagged via association to the Main account + Paypal account (since it's the only way to sell legit on the RMAH).

I had less problems with World of Warcraft when selling gold to China Agents.

No, that's not what I mean but that is one of the obvious ways.

What I meant was, flagged from association from being logged in through the same diablo 3 client. My guess is that each installation of diablo 3 has a unique ID. I have no proof of this, just a hunch.
 
No, that's not what I mean but that is one of the obvious ways.

What I meant was, flagged from association from being logged in through the same diablo 3 client. My guess is that each installation of diablo 3 has a unique ID. I have no proof of this, just a hunch.

I'm too tired to requote but the unique ID regeneration which I already did is mentioned in my thread which is useless (didn't prevent Round 2 and 3 bans):
http://www.thebuddyforum.com/demonb...ch-rnd-delays-norm-champ-day-1-quick-ban.html

since you already did all those, i can't say there is no way to avoid ban wave :(
 
Last edited:
No, that's not what I mean but that is one of the obvious ways.

What I meant was, flagged from association from being logged in through the same diablo 3 client. My guess is that each installation of diablo 3 has a unique ID. I have no proof of this, just a hunch.

Then get WireShark and start analyzing data. ;)
 
Maybe their claim is true that DB itself isn't detected, then again, maybe the way it runs/reads stuff is on blizzards end.

For example, a level 1 toon freshly made with pickup enabled on the profile starts brand new game to level up. Once stash is full, it teleports back to town even though you don't have teleport available yet. Ooooo. How is it retrieving/sending the teleport command without it currently being available yet on a fresh first game made (not joining any public/friends game).

It's doing something that is humanly impossible at that point.
 

nice to know blizzard has alot more shit to deal with. apparently the hack happened AGES ago, they just found out on aug 4th and decided to wait.

makes you hope that more staff will be dedicated to fixing this and securing b.net since sc,wow,and diablo information was compromised.

-
on a side note to this thread topic, i wonder if anything commonly found in the ban reports, has people using plugins/tools/mod that violate any of the most common warden memory scans

Code:
0x00996210 0007 - [MAPHACK]     GetMinimapMarker
0x00943cd0 0009 - [HACK_CMD]    ConsoleInput
---------------------------------------------------------------------------
0x00748800 0014 - [HIDE CRASH]  ExecErrorReport
0x00717ed0 0014 - [HIDE CRASH]  UnhandledExceptionFilter
0x004a4730 0007 - [???]         MenuCallBack
0x00458100 0010 - [PKT SNIFFER] ParseServerMessage
0x003cbe61 0008 - [PKT_SNIFFER] SendMessage
0x00351bb0 0010 - [???]         GetEntityName
0x0032d286 0014 - [MAPHACK]
0x0032d22f 0015 - [MAPHACK]
0x003299d0 0015 - [MAPHACK]     IsMinimapMarkerVisible
0x002d8761 0009 - [MAPHACK?]    Target check crap
0x00263f30 0008 - [HACK_CMD?]   ChatMsg
0x0020dea0 0012 - [PKT_SNIFFER] SendClientAction
0x0020999d 0011 - [PKT_SNIFFER] Intercepting client action
0x0017f860 0017 - [BOT]         RenderGameFrame
0x0017cdc0 0010 - [BOT]         Intercept action on entity
0x00150a00 0008 - [???]         Window stuff
0x000c7700 0009 - [???]         GetEntityAttrib
 
Screen Shot 2012-08-22 at 9.49.54 PM.webp

You've been warned .. this simply says everything about bans .. although most of us wont see it coming..
 
Way, way to many BAN reports. I suggest stopping Zark profiles.

Could they have added some type of profile detection method in the most recent patch?

Agree really there's nothing stopping blizz from signing up to this forum (as they are going to court with DB) downloading everything and picking it to pieces then just waiting for ppl to start using same parth more then once, for the pass 3 weeks I've just been use a combat bot, which in its self could still be risk as I'm fighting the same way every fight, but hey only time will tell
 
Back
Top