Is there an IP ban?
- Thread starter alakelsms
- Start date
BotOperator
Well-Known Member
- Joined
- Jan 17, 2012
- Messages
- 5,648
- Reaction score
- 74
No one can answer this 100%. Blizz can check if on the same IP other accounts are online and then ban those too.
If you don't want to loose an account don't bot and never connect a non botting account with a botting account in any way.
No ip sharing, no trading, nothing.
Btw. same question was answered minimum 100 times on the board already
If you don't want to loose an account don't bot and never connect a non botting account with a botting account in any way.
No ip sharing, no trading, nothing.
Btw. same question was answered minimum 100 times on the board already
There are white static IPs and white dynamic IPs, the static white ones never change, only 1 person has the IP in the entire interwebz. However he can ask his ISP to change it and then the old IP could be assigned to someone else (innocent). White dynamic means and IP is assigned every time your router initializes, so say you get 127.0.0.1 once and then the next day it will be 127.0.0.2 and someone else will have 127.0.0.1. Then there are NATted IP addresses which use one white static/dynamic IP for many users of their network. TLDR IP bans are fcking bullshit, they may be applicable in smaller communities, small servers, where you can ban whole subnetwork and not care, do that in MMO and that's a huge playerbase minus.
But they can try and fingerprint your hardware and also payment info may be flagged.
But they can try and fingerprint your hardware and also payment info may be flagged.
Deathleecher
New Member
- Joined
- Mar 23, 2013
- Messages
- 21
- Reaction score
- 1
I can tell you for sure you're other accounts are safe as long as you didn't bot on them.
I have botted several times before on 1 of the 3 game accounts I had under the same battle net account. As the account I botted on got banned my other accounts were still fine.
I have botted several times before on 1 of the 3 game accounts I had under the same battle net account. As the account I botted on got banned my other accounts were still fine.
Demondog70
Active Member
- Joined
- Feb 17, 2013
- Messages
- 568
- Reaction score
- 63
It could be a MAC Address ban or a Hardware ID ban. IP address can change. It's not as safe a ban for Blizz as banning based on the other two and those accounts would have used the same Mac Address and Hardware correct?
Demondog70
Active Member
- Joined
- Feb 17, 2013
- Messages
- 568
- Reaction score
- 63
This makes more sense.
Demondog70
Active Member
- Joined
- Feb 17, 2013
- Messages
- 568
- Reaction score
- 63
How to change Hardware ID and Mac Address ID
HardwareID Change:
Change Hardware Id (HWID) [Offical Microsoft Program] [2016] - YouTube
Mac Address Change:
How to Change MAC Address (Windows) - YouTube
HardwareID Change:
Change Hardware Id (HWID) [Offical Microsoft Program] [2016] - YouTube
Mac Address Change:
How to Change MAC Address (Windows) - YouTube
When the term IP ban is used by multibotters, is quite often not referring to a straight-up , sensu stricto, IP ban. IP's are easily changed. And furthermore, they would use it to flag accounts, but manually checking them would be a necessity.
It's normally used to define any sort of linkage between several computers that were intended to separate bot accounts, which could be using even different IP's; the methods that Blizzard uses to flag accounts are unknown to us (It could be any or several of dozens of Hardware ID's , network Identifiers, Wow installs, MaC ID's , etc)
Right now Blizzard is (also in this aspect, sigh) ahead of botters. Both the most common obfuscating methods, including VPNs and Virtual Machines, and of course changing the basic ID's is proving to be ineffective. Nothing is effective when software detection happens, but taking that instances of detection apart, classical hiding methods are not proving useful either.
Take into account that, as explained in the vids, those spoofing tricks are not changing the real, Hardware link IDs for both your HDD (which is the HWID) and MaC address. The fact that you can return to default values is a clear proof. And the "default" information is also easily obtainable, so if I were Blizzard, I would use it.
Nothing is safe anymore. It never was, but now it's even more unsafe than ever. Blizzard position against Bots has taken a really harsh step forward, and their methods used and account actioning patterns prove it.
TLDR; check ban reports. Don't use the bot if you have a Main account in the same household OR benefiting from the bot accounts in any way, cause the danger that you'll lose it has gone to almost non-existant to almost sure.
It's normally used to define any sort of linkage between several computers that were intended to separate bot accounts, which could be using even different IP's; the methods that Blizzard uses to flag accounts are unknown to us (It could be any or several of dozens of Hardware ID's , network Identifiers, Wow installs, MaC ID's , etc)
Right now Blizzard is (also in this aspect, sigh) ahead of botters. Both the most common obfuscating methods, including VPNs and Virtual Machines, and of course changing the basic ID's is proving to be ineffective. Nothing is effective when software detection happens, but taking that instances of detection apart, classical hiding methods are not proving useful either.
Take into account that, as explained in the vids, those spoofing tricks are not changing the real, Hardware link IDs for both your HDD (which is the HWID) and MaC address. The fact that you can return to default values is a clear proof. And the "default" information is also easily obtainable, so if I were Blizzard, I would use it.
Nothing is safe anymore. It never was, but now it's even more unsafe than ever. Blizzard position against Bots has taken a really harsh step forward, and their methods used and account actioning patterns prove it.
TLDR; check ban reports. Don't use the bot if you have a Main account in the same household OR benefiting from the bot accounts in any way, cause the danger that you'll lose it has gone to almost non-existant to almost sure.
Last edited:
I bet you attached the bot at 1 point. You dont have to press start on the bot to get banned. Once you inject in to wow (on startup of bot) you are screwed.
Aion
Well-Known Member
- Joined
- Jan 18, 2011
- Messages
- 3,907
- Reaction score
- 105
If you are afraid of getting the bot attached to Honorbuddy, but you still have to share the same computer between bot and non-bot accounts, there is one stable solution:
Play the non-botting characters only on the 64bit WoW client. Honorbuddy will never attach to it, even by mistake!