Honorbuddy Announcement 21th May 2015

I only played from the 1st to the 6th and got banned, so something for sure happened in that time frame. Before the bann I didn't play for over 6 months.

 

I use the hacks over at ArtificialAiming and had the same thoughts about whether they could implement the same kind of hooks and protection as they have had in the past, but even with this there have been several occasions across several different games and anti cheat engines where they have been detected. I think it's just one of those things that you've got to accept, if you cheat you have to expect to pay the price for it. Lets hope the new and improved tripwire will keep us safe for the next few years like it has already up until the past week.

 

i know the risk im not even complaining but that would be a nice feature im a hardcore cheater i cheat since 2009 2008

 

Well my plan is "let the other guys play and get banned until they figure out what the bann trigger is".. then I might bot again.

 

Can't be bothered to wait, got nothing to lose other than 12 quid each time at the moment on my new accounts. I'll take that risk because WoW to me is nothing without HB.

 

Meaning anyone who uses it is just going to be a guinea pig until they realize what happened.

Can't fix something if you don't know what is broke~

 

botting for 6mo inbetween bans is a very good amount of time to get away with it. I'd be more than ok with that

 

For those who think that they've bunned us for kicks profile, garrison farming profile etc - this is not true. I was using only pvp paid routines with Enyo, never AFK BG botted, only manual movement, nothing like "instant trinket" or insta kick in cast. All my character profiles were self-adjusted for my purposes. And I had only 1 account with 5 hand-levelled 100 lvl chars which was banned 13.05. So there were only bot detection or player reports possible.

 

a real botter knows instantly who is using kicks profiles its i can see many people using questbot profiles of kicks standing in the same path for a few seconds to wait til the npc spawns running in the same path at the same spot in a line ofcourse you know they are botters we should have Randomize hotspots in the quest profiles and not like 3 4 guys running in the same direction

 

just make 2 differnts HB one for chinese game style and one only running enyo for rotations. out there there are many that ONLY are in need of that option to keep playing wow.
my two cents

 

It's true, but I've never used any kicks profile for questing or levelling Only CRs.

 

thats why Randomise hotspots would be better people shouldnt move in a same line direction and then when their is a real player flying on the area to look for botters to report them then we are scrwed

 

I'll bot on an alt account but never on the same computer as my main. Lesson learned. But is Bossland telling the truth about what they did or what they found is the question.

 

From everything that I've read it's a software detection of the bot being injected to the WoW process, it makes no difference whether you were sat with it injected in the middle of nowhere when they ran the scan to check who was botting, if you had it injected you got caught.

I'm actually quite intrigued to see what happens when we get back online and start botting again, I got caught in the glider ban-wave which I believe was a similar time in May, a few years back and it was fine after that. Obviously legal reasons caused MDY to shut it down eventually but it seemed to work soon after the ban wave without any detections, whether that was due to them making changes or just blizzard not pulling the trigger on another ban-wave we'll never know.

 

and we will start again....

 

that's a shitty speculation and goes directly against everything HB devs have being saying for years. In USA at least Blizzard CAN NOT introduce "malware" that "scans everything on everyone's computer". and if they could I seriously doubt they would given the unreal outrage that would produce, as shown numerous times by other companies trying the same shit.

The tripwire monitors changes to the warden (and game client, though that's never updated live without a patch). Blizzard has not used the warden to detect major bots for many many years. Warden is for hacks and kiddie-scripted bots. Blizzard HAS used warden-like functionality *inside* the game .exe (slipped in there during a regular patch), which is how they got Glider a couple of times. But that should be noticeable as well, especially after a week's investigation.

My "speculation" is that this is all server-side. Same way you couldn't fly around in MoP gathering herbs and ore for more than a couple of hours a day without getting a ban within a few weeks. HB always said this was all 100% reports and greediness etc, but please. There was something detectable from logs in GB2's behavior, all the random hotspot generators etc didn't do shit to address that, and once blizz ran thru all the logs of accounts farming for several hours a day they could reliably separate the humans from honorbuddy.

They finally invested enough money into automatically scanning logs, and the HB client is doing something that's detectable on their end, without actually detecting it on our computers.

Anyhow this is all guesswork. Thank you buddy team for being honest that you have no clue wtf happened, but this WAS directed at HB and no other major bot, and this DID get a vast amount of HB users, perhaps 100% and they just haven't yet banned 100%.

For those planning to restart botting - don't use on main accounts, I hope that's obvious. I expect another banwave in 6-8 weeks, and so on forever.

The real miracle here is that they came up with the 6 month suspension idea. as annoying as that is, it's NOTHING compared to getting perma banned on a 10 year mythic account, no warning

 

While you're right to a certain degree, I very much appreciate Bossland for being honest. Respect and thanks to the whole staff.

 

hope so

 

Maybe I should sell my account, start a fresh one incase.

 

How bout remove pvp afk, problem sorted..