Hi,
BubbaDad,
Smuht is right on?player reports are deadly...
To keep from drawing player reports, Honorbuddy has built 'non-compete' logic into many of the quest behaviors, and the target selection logic. This may cause an occasional delay during questing while we wait for the competing player to clear the area. But, "stealing" another player's mob or quest objective is a great way to get reported quickly.
In GB2, you want to keep the "ninja nodes" feature turned off for the same reason.
There is also
very strong evidence that you reporting other players
for anything, sends a snapshot of critical information to Bliz along with the report. In short, if Honorbuddy is
or has been attached to the WoWclient when you report another player, you have just reported yourself also.
So, think twice before reporting the 12yo at Crossroads for foul language, or an inappropriate name.
Anything.
The second way is...
Bliz is stepping up their WoWserver-side detection game. Since the 1970's, very good pattern recognition algorithms have been available to recognize common characteristics in groups. Examples include:
Obviously, we do not know what specific algorithms Bliz employs, but we do know they have them available (and obviously use them). Some of the algorithms can be done in (semi-) 'real time', but the vast majority require post-processing. This means there will be a lag of 2-4 weeks or longer, as they run the algorithms on the WoWserver-side logs they've accumulated.
Thus, when you are banned, there may be a significant time gap between when you are detected and when the ban is effected.
Honorbuddy steps up its game each time we figure out what's going on. Examples include:
- "Randomization factor" in Gatherbuddy2 to defeat LCP and other path detection algorithms
- Variant pathing in the Honorbuddy ground navigation system to defeat LCP and other path detection algorithms
There are many many other techniques that we won't discuss, but these two are largely known by the Community?so, we're not really giving anything away.
Another way is Community members actually report themselves...
by taking a screenshot with the WoWclient and uploading it to a public forum (including thebuddyforum.com). The WoWclient inserts watermarks that contain
steganographic information about your WoWaccount and lots of other stuff a botter would not want Bliz to know. This is easy to defeat → use a third-party screen capturing tool like Lightscreen or Greenshot. The trick is to know that you need to use such a tool instead of the WoWclient's builtin facilities.
Or, you install a plugin that uses the WoWclient's chat facility to communicate with other bots. This is how other bots have gotten caught on at least two different occasions. Honorbuddy is not immune to this, since we allow third-party plugins to be written and deployed. It is up to the Community member to evaluate the safeness of each plugin they choose to install.
Or, they respond to a soliciting post to form that botting guild, or arena 2s/3s team. The soliciter can easily be a Bliz employee lurking in our forums using social engineering to get botters to report themselves.
Or, botting for 10 hours without taking a single (simulated) bio-break.
Despite the tools Honorbuddy employs and makes available, it is still up to the Community member to 'bot smart'. This means actually configuring GB2 to use a meaningful value for GB2's "Randomization Factor". Or, combat routine writers not doing inhuman things like 'instant interrupts' 100% of the time. Or, plugin writers not using the WoWclient's builtin LUA screenshot functions, or transmit information using the WOWclient's builtin chat channels.
Botting is a dangerous (but wildly fun) sport. But, it boils down to each Community member to 'bot smart'. Botting is not a click-n-go activity, unless you want to be banned immediately. Think twice before each plugin, combat routine, etc. you add to Honorbuddy.
cheers,
chinajade