Devs reverse Engineering?

[smitty]

Are the Devs reverse engineering anything new that changes to WoW? This is use to be a huge deal, now, it seems HB just gets updated to work with the new version and no investigation occurs. They should have developed a automated scan or some sort of script that can honestly pick out suspicious code then, investigate it. There use to be more downtime between patches and now, since HB has less downtime there are more ban waves.. I think the devs are missing a huge step in the life cycle of deploying the updated HB.

It is pretty bad when Ownedcore knows when HB is being detected before Bossland knows.

 

[Demondog70]

Are the Devs reverse engineering anything new that changes to WoW? This is use to be a huge deal, now, it seems HB just gets updated to work with the new version and no investigation occurs. They should have developed a automated scan or some sort of script that can honestly pick out suspicious code then, investigate it. There use to be more downtime between patches and now, since HB has less downtime there are more ban waves.. I think the devs are missing a huge step in the life cycle of deploying the updated HB.

It is pretty bad when Ownedcore knows when HB is being detected before Bossland knows.

The process use to be called Tripwire but it honestly is not working.

I too made note of how happy they are to update for new patch without care and attention to details of added counter measures by Blizz. Back in Glider days it was not unusual for us to be down a week or two with a major patch. Now because people scream because they can't make a million more gold the bot is brough back online early leaving us open to whatever. In November they clearly admitted to did not know or was unsure what caught us but they still brought the bot back online before knowing FOR SURE what it was and Nov 22nd happened. Far too careless if you ask me.

Let's get it straight we all know the risk of botting but carelessness is not a good reason.

 

[marrvin]

In November they clearly admitted to did not know or was unsure what caught us but they still brought the bot back online before knowing FOR SURE what it was and Nov 22nd happened. Far too careless if you ask me.

As far as I remember they did not "brought the bot back online". They actually left tripwired activated to prevent botting.
Because many user screamed "we don't care - please let us bot again" the implemented a way to let the user disable tripwire and gave a FAT warning that this is risky.

-- marrvin

 

[fantasydreaming]

They did that for a few days, then had a full release up. And 1.5 weeks later there was another banwave.

That said, it's hard to scan compiled code. Frankly it's amazing bots work at all, that's what got me into HB in the first place - amazement from the programming / computer science perspective.