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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Honorbuddy Announcement 21th May 2015

Status
Not open for further replies.
i think honorbuddy wont be back that this is just a troll thread to see how many views to get D
 
So if you think its trolling, go somewhere else. And the week doesn't end until Sunday night at 11:59:59 pm, so....
 
Im wondering whether the developers have looked at the battle.net app to see whether blizz could possibly have coded any malware or detection code into it, reason being is that a lot of botters have that open and running before starting the game or the bot.
 
Im wondering whether the developers have looked at the battle.net app to see whether blizz could possibly have coded any malware or detection code into it, reason being is that a lot of botters have that open and running before starting the game or the bot.
the bnet app is already known to include certain maleware detections
 
i'm a little bit disappointed by this statement,

a malware really? it sounds like all these really bad and horrible theory we can read on the forum since the wave, not to mention the 64bits one, but as developper come on you can think better.

my only guess and hope is this statement is a smoke screen.
 
In my opinion honorbuddy got detected because of Warden. Honorbuddy reads and modifies the games memory in order to do certain actions in the game (for example cast a spell). These kind of things where an external application accesses the games memory can simply be detected with an anti-cheat-system. Take Valve's VAC3 for example.

I'm not an expert on this topic and I clearly have no idea how Honorbuddy is secured against those things but I'm following the CS:GO cheating quite a bit and there developers have to make huge workarounds (polymorphism, unique executables, driver protection, idk...) to keep their hacks undetected. Maybe reverse engineering the recent Warden update might help understanding what has happened?

Edit: Getting detected because of CTM and 32bit is rubbish. The error rate is way to high and Blizzard would lose a lot of reputation if they banned legal players.
 
My 2 cents (Not that they mean much.)

1. 32 bit client is easily detected since you have to manually change it to make it 32 bit.

2. Being that I only use Enyo and Custom CRs, I believe the overlay's are a major issue and should be removed. This is something recently added and its also how the PR ban hammer happened.

3. I'd like to see 2 different versions of HB. One that is like an Enyo stand alone, only used for rotation botting, and a second version for questing, pvp, farm ect. This way if another ban happens, if people choose to only use one or the other, you can narrow it down to which is being hunted if only 1 of the 2 get banned. If both get banned, then its because they are using HB source to detect it.

4. They banned by IP. Once confirmed 1 account was using, they just banned all of the accounts linked to that address. My GF and my Roommate both got their accounts banned (they don't have HB on their computers) along with 4 other of my accounts (2 that I haven't used in over 3 months).

4. In order to remove all doubt, if you have already been banned, you will have to wipe your computer and change your static IP to make sure that whatever was on your computer is gone and you aren't linked to your banned account. Personally there are plenty of ways to detect someone using HB since an employee of blizzard could easily be on the forums and get access to all the code they need to do a "search and destroy" action on any code being run identically to what is coded in HB.

5. Personally I figured HB was perfectly safe for how I was using it (just as a rotation bot), however I was wrong. I made the decision to use it on my main account and I paid the price. I will be buying another account and will be using HB once it is up and running. If I get banned again oh well. However it is my choice to do so. I will stick by HB as long as it is in production.

Thank You
 
Story from someone who was not banned. Here is what I was doing and what I noticed at the time of the bans:

As someone who uses a different program for rotations mainly for when I'm feeling lazy (I usually do better than my bot does...) here is what I experienced the night of the bans. Hopefully it will shed some light but who knows!

I had a rotation bot loaded but not running the night of the bans. I tabbed out several times in order to start combat logging for my raid and noticed my Battlenet client have several small (10-25 Mb) downloads. I have automatic downloading turned off, so it still asked me to manually click the download symbol. I relogged wow without a rotation bot loaded because I find random hot patches without notes to be suspicious. This happened 3, maybe 4 times over the time I was logged on (about 7pm-1am EST). My MS was actually a little high that night also (possibly unrelated but I was at about 200 world when I'm usually at 25). Anyway, I was running combat logs, usual addons, and no bots injected after about 9pm EST.. Then I log on the next day and hear about the banwave. :(
 
In my opinion honorbuddy got detected because of Warden. Honorbuddy reads and modifies the games memory in order to do certain actions in the game (for example cast a spell). These kind of things where an external application accesses the games memory can simply be detected with an anti-cheat-system. Take Valve's VAC3 for example.

I'm not an expert on this topic and I clearly have no idea how Honorbuddy is secured against those things but I'm following the CS:GO cheating quite a bit and there developers have to make huge workarounds (polymorphism, unique executables, driver protection, idk...) to keep their hacks undetected. Maybe reverse engineering the recent Warden update might help understanding what has happened?

Edit: Getting detected because of CTM and 32bit is rubbish. The error rate is way to high and Blizzard would lose a lot of reputation if they banned legal players.

Warden is joke, when you compare it with VAC3. There are ways how to completely disabled it. And yes, HB is secured against warden.

Story from someone who was not banned. Here is what I was doing and what I noticed at the time of the bans:

As someone who uses a different program for rotations mainly for when I'm feeling lazy (I usually do better than my bot does...) here is what I experienced the night of the bans. Hopefully it will shed some light but who knows!

I had a rotation bot loaded but not running the night of the bans. I tabbed out several times in order to start combat logging for my raid and noticed my Battlenet client have several small (10-25 Mb) downloads. I have automatic downloading turned off, so it still asked me to manually click the download symbol. I relogged wow without a rotation bot loaded because I find random hot patches without notes to be suspicious. This happened 3, maybe 4 times over the time I was logged on (about 7pm-1am EST). My MS was actually a little high that night also (possibly unrelated but I was at about 200 world when I'm usually at 25). Anyway, I was running combat logs, usual addons, and no bots injected after about 9pm EST.. Then I log on the next day and hear about the banwave. :(

I logged of from raid 10mins before banwave. I was using Enyo with CR on WoW client, that wasn´t updated via Battle.net app since 6.1. Also my bot didn´t have problem with running.
 
Last edited:
So no clue on how? No x64? No closing to non users?

Yea fool me once....

I guess It allows you to start making money again asap right? Our accounts are paramount EXCEPT when it comes to taking extra time and measures to do so...

HB for suicide accounts at best in its current state. This happens again and you'll lose whoever you guys have left. I strongly advise/encourage you to do some major updating.
 
For me this comes as close to the worst news possible - HB team without a clue on what actually happened. In my eyes, this completely destroys the market for anyone who value their account (Yada yada, don't bot bla bla, I know). For instance Raidbot users.

Less of an issue for farmers I guess ...

Me agreeing with nom? You know shits hit the fan when..
 
I could be wrong, but it seems like running the battle net app might have been the way to scan our pcs. Cause there was an update and license agreement a day or so before the "event" and then oddly enough there was another battle app update a day after. Thoughts???
 
Status
Not open for further replies.
Back
Top