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

"Safer" botting questions.

HB8240E15

New Member
Joined
Jun 15, 2011
Messages
22
Reaction score
0
Hi, forgive my ignorance here, but I was wondering if it was possible to make botting "safer" by using a proxy, hardware ID masking, a virtual box, MAC spoofing or something like that? Obviously, it wouldn't prevent you from getting banned, but it could at least give you plausible deniability in the event that it does occur (Oh no, I was hacked! Give back account pls). Would this even be feasible? I would really like to get back to using HB, but the warden upgrade makes me a bit nervous.

If this is possible? And if it is, do you think it would actually be useful? Just hoping to get some insight.
 
Last edited:
The word that you used that is blanked out, it is a ticking time bomb, even legit players get banned using vee p n's. The word is blocked as it is not to be used in discussions on these forums
 
no, its not worth using things to mask your network location, in fact it can probably make it worse, blizzard seeing a user jump around the world by changing ip's and mac addresses. not only that but you dont know what other people are doing on those networks. really i dont think blizzard cares. your better off running a less complicated setup.
 
The word that you used that is blanked out, it is a ticking time bomb, even legit players get banned using vee p n's. The word is blocked as it is not to be used in discussions on these forums

People do use them and they do get banned. They are usually using a known service. There are ways to successfully use them but, as CodenameG said, the return in that effort is probably not worth the trouble. I do use them but i also have been a network engineer for 20 years and know what i am doing.
 
Thank you for the responses. So, to clarify, there is no realistic way mask identity or to gain a layer of plausible deniability in the event that you get banned, correct?
 
no, because in the end they know what account is logging into their system. and really, your trying to protect the account, Masking your identity (ip spoofing and tunneling) doesn't help with that. if you want to protect your account, bot smart. also, if you get banned because of detection, they at that point know a bot is running on your account, and your account is just as screwed, even if you say "well someone hijacked it" but if your always logging in from random ip's, if they go and check it they arent going to be able to see that someone from china hijacked it, its just going to look like normal usage.
 
Last edited:
Just to clarify, using any technique to mask your IP is only beneficial (theoretically) if you have mutliple accounts and you are trying to isolate them from a GM banning all accounts associated with an IP address. That is not to say they are banning by IP address as that is well discussed here as being impractical. This is based on the conclusion that this is how some people have been banned.

If you are only botting one account, there is absolutely no value in doing it.
 
but they only ban the actual account that was botting. they would never do an ip ban in normal botting cases. for them to do an ip ban for all accounts, you would have to be running at least 50 accounts and even then, you would actually have to get the attention of a GM, to investigate all these issues and for him to decide all accounts on that ip are in fact botting. even in cases where you have multiple accounts on the same battle.net, only the account in question is banned, not the others.
 
I've only really heard of them banning linked accounts if you are/they think you are selling gold.
 
Think of this.

You're a blizzard GM. You see someone reported "Botter 1" for botting. You inspect them, at IP 127.0.0.1, and see they're playing normally. You then see the reported IP was 192.168.1.1. You realize "Hm, that's a large change, even if it's in the same city, a dynamic IP only changes the last range of numbers..."

You see the player reported from 192.168.1.1 AGAIN. And inspect him at 127.0.0.1 again.

At this point, they know you're doing SOMETHING wrong, and you're using a *** to cover it. They can do one of two things.

Wait for your account to jump on 192.168.1.1 and inspect you, or just ban you for account sharing due to you logging in from widely varying IP's at any time.

Not to mention that in the TOS/EULA, ***'s are banned, so they can just ban you for using one.
 
Think of this.

You're a blizzard GM. You see someone reported "Botter 1" for botting. You inspect them, at IP 127.0.0.1, and see they're playing normally. You then see the reported IP was 192.168.1.1. You realize "Hm, that's a large change, even if it's in the same city, a dynamic IP only changes the last range of numbers..."

You see the player reported from 192.168.1.1 AGAIN. And inspect him at 127.0.0.1 again.

At this point, they know you're doing SOMETHING wrong, and you're using a *** to cover it. They can do one of two things.

Wait for your account to jump on 192.168.1.1 and inspect you, or just ban you for account sharing due to you logging in from widely varying IP's at any time.

Not to mention that in the TOS/EULA, ***'s are banned, so they can just ban you for using one.
Using a *** is not against the ToS. It's just not supported and will probably red-flag you more than the average user.
 
Navy got it right. V-p-n services are useful when running a big number of accounts , to differentiate between the groups.
I can't deny CodG when he says an ipban is only likely to happen with a big number of accounts ( 50 or whatever)and that blizz will only ban offending accounts. But sharing IP with a botting account will flag every account in that IP, for posterior checks. Thats how you see reports from the same person saying 1/20, in 2 days 9/20 and in a week 20/20.
If you ever want to use a v-p-n service for masked botting, those two words are a must: dedicated whitelist. Anything else will probably be worse than not using the service. Plus, an instantly disconnect program for when the *** is down or any issues happens is a must, or you will probably lose your accounts when it happens.
 
Back
Top