buzzkip
New Member
- Joined
- Jan 24, 2013
- Messages
- 67
A thought I had on Blizzard's latest Ban Wave. Honorbuddy may not be detected, at all.
I haven't used Honorbuddy in a while, and some may be able to counter what I'm about to suggest by simply saying the following Tripwire mechanics don't take place.
If the current and/or past Tripwire mechanic is to close WoW and stop/close Honorbuddy, here's my pretty simple suggestion as to how the Ban Wave gathered a target list.
Here goes:
Take a random day - Tripwire activates, WoW closes, Honorbuddy closes. To Blizzard your account just got recorded as going offline at the same time as they intentionally trigger Tripwire with a Warden pulse.
The list of accounts disconnecting will be HUGE. And will include THOUSANDS of legit accounts which coincidentally logged off.
Take another random day - The same Warden pulse occurs and Blizzard creates a new list.
The two lists are now cross-checked and removes all of the accounts from the first list which are currently online but didn't disconnect this time around.
Blizzard is left with a list which includes 2 occurrences of accounts which have been online and disconnected at the same time as Warden doing it's thaang.
The previous steps continue - Blizzard continues their sweep, collecting a strong target list of accounts effected by Tripwire activity.
Secondary data checks available to Blizzard can then be automated on the target list, for example:
With enough time and enough sweep parses, a solid Ban Wave list can be created and Honorbuddy may not even be detected.
Why hasn't other bots been as effected? They don't have the Tripwire which Honorbuddy has, that Blizzard may KNOW how to trigger. Honorbuddy may not be detected, just the Warden counter mechanics 'bateable'.
I haven't used Honorbuddy in a while, and some may be able to counter what I'm about to suggest by simply saying the following Tripwire mechanics don't take place.
If the current and/or past Tripwire mechanic is to close WoW and stop/close Honorbuddy, here's my pretty simple suggestion as to how the Ban Wave gathered a target list.
Here goes:
Take a random day - Tripwire activates, WoW closes, Honorbuddy closes. To Blizzard your account just got recorded as going offline at the same time as they intentionally trigger Tripwire with a Warden pulse.
The list of accounts disconnecting will be HUGE. And will include THOUSANDS of legit accounts which coincidentally logged off.
Take another random day - The same Warden pulse occurs and Blizzard creates a new list.
The two lists are now cross-checked and removes all of the accounts from the first list which are currently online but didn't disconnect this time around.
Blizzard is left with a list which includes 2 occurrences of accounts which have been online and disconnected at the same time as Warden doing it's thaang.
The previous steps continue - Blizzard continues their sweep, collecting a strong target list of accounts effected by Tripwire activity.
Secondary data checks available to Blizzard can then be automated on the target list, for example:
- 64-bit operating systems running 32-bit compatibility WoW applications.
- Accounts on the target list from the same IP Address, MAC Address, Customer Payment and/or Personal details.
- Similar activity; PVE & PVP Farming, Auction House & Bank Utility.
- Social Circle Links; targeted accounts which communicate with each other, in the same guilds, same realms, on Battle.net friend lists.
With enough time and enough sweep parses, a solid Ban Wave list can be created and Honorbuddy may not even be detected.
Why hasn't other bots been as effected? They don't have the Tripwire which Honorbuddy has, that Blizzard may KNOW how to trigger. Honorbuddy may not be detected, just the Warden counter mechanics 'bateable'.