Quote Originally Posted by Shodokan View Post
Actually it did not unlock LUA code after the second iteration to my knowledge, there was an original banwave for it in 2010 which did that after which it moved to memory reading and external if/then statement coding.

I don't use AHK or HKN so I only draw comparisons to how i have seen people set things up and how people have helped others set things up.

SOMETHING is setting off a false positive, because these bans were NOT done by gms watching accounts/players they were automated bans. My bet with ebony's case is that a GM was making sure that one didn't fall through the cracks that showed similarities to functionality it provided after she was possibly reported. (I've also been contacted by gms in the past two days while leveling new dks and know i've been reported multiple times in the past week while leveling characters up.). Hell I didn't even know there was a banwave for those bots until i read that people got banned for boxing apparently here.

I love ISBoxer and what it has allowed me to do but I'm not going to sit here and say that there is absolutely zero similarities between the bot's functionality and that of ISBoxer's (And AHK/HKN for that matter now that you mention it).

ISBoxer is NOT a bot, we all know this... but is auto-reconfiguration of buttons pressed in an order via a single button(step 1: 1, step 2:2, step 3:3 all while pressing 1) really not the least bit of the grey area we all knew it was from the beginning? I mean we have had that discussion here before no?

Just some food for thought and nothing more.

Example of a macro

Nah, for the simple fact that regular players use such macros as a convenience to actually piano mashing their fingers into cripple status.

WoW is overly complicated in the toolbox for every character and those macros save us from crippling ourselves. I see them as accessibility for if they didn't exist, I surely wouldn't be playing the game.

When I do box, my characters use those kind of ingame macros. You can't put interrupts in them and expect to do very well. Interrupts fall outside of the rotation and as such, remain outside of those macros for maximum effectiveness.

Even if you had say, a 5 box with an interrupt chain you would find that it'd rarely if ever be effective in combat with other players. For the simple fact that it isn't on demand but queued. I can't tell ya the number of times queuing things like spell interrupts has been a really bad idea. I've done it, wiped because of it. It works in rare occasions where the clock strikes 12 and doesn't work anywhere else.

These guys are no doubt using some kind of memory reading bot to read when cast events are taking place. Think about it. It'd be very easy for Blizzard to detect who is calling protected functions outside of protected scope. Simple by recording stack calls for players at random when reports happen.

As some others have said, I take it with a pinch of salt whenever someone says they weren't doing anything against the ToS or 'I was just multiboxing.' Sorry, I don't buy it. I do multibox on and off but more than enough to where if multiboxing was a bannable offense I'd be long gone.