7/7 banned US

[gnomegawd]

A few of the accounts were 1-2 weeks old, rest were months old and had 1600+ hours on them.

6 different ips for the 7 accounts. No VMware or anything.

So in summary, i'm not exactly sure how they are banning at this point; maybe through waypoints order in the act? I'm going to assume they added some additional pattern detection type stuff.

So you use ***** split, but, how are you changing the MAC ID of every ip? Does that software also do that? Do you actually do 8 installs of D3 or did you copy clone, and or just running from same D3 folder?

I know some of these questions perhaps are odd, my main question is MACID how did you change that, and I know there is software 'SMAC' will provide this ability which I don't bother to use unless a machine gets banned.

If I re-rolling with doing as little as possible, ie; "format, install, prep, perhaps hard drive change out for / during this machines bot life, add hardware network card swapping away from the onboard NIC. I will even change swap around video cards, and flip flop cpus so the same machine config doesn't happen during next bot reincarnation. This probably sounds paranoid, but one can not be to careful.

or ftm used an rt trace back to your new'ish' ip's or attempted to connect/scan from an external source to your destination to confirm/test security?

 

[Splitty]

Sorry 2 hear about the ban, but thanks for sharing your information. I learned quite a bit from this thread.

 

[redphoenix]

Sorry for your loss, and glad to see you bounce back! I would be interested in seeing different ways to change HWID.

Firstly using VM and then isboxer.

I run 4 teams of 4 so using isboxer and would like to change the ID. Maybe look into getting behind a *****.

Thanks for your guide if you decide to put something up.

 

[vicesandy]

Sorry for your loss, and glad to see you bounce back! I would be interested in seeing different ways to change HWID.

Firstly using VM and then isboxer.

I run 4 teams of 4 so using isboxer and would like to change the ID. Maybe look into getting behind a *****.

Thanks for your guide if you decide to put something up.

With isboxer u cant change MAC address. U can change the IP on host but all the rest will follow.
VMware is the only one I know that allow u to change MAC address. But it takes a lot more resource to run.
I m running 3 account on VMware, same IP but changed MAC address and D3 registry.
Expanding to 10 bots, about to buy some private IP.

 

[vicesandy]

I love this attitude! I got hit last night for 6/6 and today I have 6 more going a couple at 60 and the rest will be there soon, thankfully my local Target store had 6 in stock.

Bans are imminent and when they happen you get back on the cash cow and ride it.

being banned is part of the cost. I started with 3 accounts and 2 of them were banned 2 days after reaching lv 60 about 2 month ago.
So pretty much I started with one account. Now I have 3 accounts (the most my I3 can handle) + 2 CD keys and $600.
Buying a new computer and expanding to 8-10 accounts hopefully by the end of this month.

 

[eastg2]

I don't understand why you people are talking about things such as your MAC Address, and diffrent HWID's. Does the warden function look outside of Diablo's proccess? Because thats the only way your MAC address/HWID would come into play?
Also, when bouncing my diablo procs through 25ms socks, I get a 100+ MS latency increase in game, dunno whats up with that should be a lot less imo.

 

[gnomegawd]

Because bluzzard knows your system hardware config look in you d3 folder there are files containing this and when error logs are generated it sends these to them... also do not rename error report .exe that would be flagged.

 

[vicesandy]

I don't understand why you people are talking about things such as your MAC Address, and diffrent HWID's. Does the warden function look outside of Diablo's proccess? Because thats the only way your MAC address/HWID would come into play?
Also, when bouncing my diablo procs through 25ms socks, I get a 100+ MS latency increase in game, dunno whats up with that should be a lot less imo.

I was botting 2 accounts on 1 desktop and another 1 on laptop. All the same ip. The 2 account on desktop got hit and the one on laptop survived. That's why I change my Mac address on my current computer. And if there is a way warden really detects db we will be all out of business.

 

[harleystcool]

i'm just gonna bot 24/7 and with 4 bots all on the same ip, and hopefully i blizz won't ban me, as i'm to lazy to learn all the mumbo jumbo lol

 

[harleystcool]

hey car guy you planning on making that guide for multiple bots with different ip's? i run 4 atm and make 12 games each per hour, and from your prevous posts you said you've played enough to notice that ip's and bans are linked together, which got me abit worried as i've only been running all 4 for a few weeks, alll 24/7

 

[carguy]

hey car guy you planning on making that guide for multiple bots with different ip's? i run 4 atm and make 12 games each per hour, and from your prevous posts you said you've played enough to notice that ip's and bans are linked together, which got me abit worried as i've only been running all 4 for a few weeks, alll 24/7

I am; just got distracted with Halo 4 as of late

Anyway, here's the gist of it. More details later:

1-Create copies of the d3.exe; as many as bots you have. Rename them like d3-1.exe, d3-2.exe etc.
2-Setup Isboxer to point to each different exe, for each different bot (called characters in isboxer). If you don't have isboxer that's ok. You can still make different folders for each d3, or use some other program that allows you to run different d3's from the same directory.
3-Download the program called pro xycap (no space),
4-Set up your new pro xy ip addresses in pro xycap, then assign one pro xy per d3.exe you created earlier.
5- (optional) Setup a relogger(like drelog) to start and bot.

It sounds complex, but the hardest step by far is getting drelog setup. Just make sure you test out all your IPs you are given ahead of time (assign an ip to a d3 exe, then launch that exe one at a time and make sure you can connect/login).

 

[un4given]

I am; just got distracted with Halo 4 as of late

Anyway, here's the gist of it. More details later:

1-Create copies of the d3.exe; as many as bots you have. Rename them like d3-1.exe, d3-2.exe etc.
2-Setup Isboxer to point to each different exe, for each different bot (called characters in isboxer). If you don't have isboxer that's ok. You can still make different folders for each d3, or use some other program that allows you to run different d3's from the same directory.
3-Download the program called pro xycap (no space),
4-Set up your new pro xy ip addresses in pro xycap, then assign one pro xy per d3.exe you created earlier.
5- (optional) Setup a relogger(like drelog) to start and bot.

It sounds complex, but the hardest step by far is getting drelog setup. Just make sure you test out all your IPs you are given ahead of time (assign an ip to a d3 exe, then launch that exe one at a time and make sure you can connect/login).

Nice info dude and sorry for your loss.

I wonder using different MAC addresses really helps. The only way for blizz to detect many clients are running from same MAC is that each d3 client get and send default NIC mac address of the pc to the game servers. And I think its unlikely that blizz try to send explicitly hardware info of all player clients to its servers.

 

[FrenchBot]

I am; just got distracted with Halo 4 as of late

Anyway, here's the gist of it. More details later:

1-Create copies of the d3.exe; as many as bots you have. Rename them like d3-1.exe, d3-2.exe etc.
2-Setup Isboxer to point to each different exe, for each different bot (called characters in isboxer). If you don't have isboxer that's ok. You can still make different folders for each d3, or use some other program that allows you to run different d3's from the same directory.
3-Download the program called pro xycap (no space),
4-Set up your new pro xy ip addresses in pro xycap, then assign one pro xy per d3.exe you created earlier.
5- (optional) Setup a relogger(like drelog) to start and bot.

It sounds complex, but the hardest step by far is getting drelog setup. Just make sure you test out all your IPs you are given ahead of time (assign an ip to a d3 exe, then launch that exe one at a time and make sure you can connect/login).

What about Agent.exe ? Did you make it bypass through ***** too ?
If you didn't it might be the reason why all accts got banned, no ?

 

[Deebs86]

Hey carguy have you find a decent guide for pro xycap? I haven't found one of much use.

Is the hostname the ip address of the p r oxy you are using?

It seems simple but I am not sure I am doing it right, create a p r oxy, set rule to redirect through that one, then choose your d3 exe? Is that it?