Banned my 4shaman.

[Shodokan]

First, (to everyone) I just don't understand how hard it is to not mention specific bots by name. People are posting names of bots like it's pertinent information when it isn't. It's always been a rule on this site to keep the names of bots off of this forum and that rule hasn't changed. It's honestly becoming tiresome continuously having to edit out the names of bots in other peoples' posts and I'm just going to start completely deleting entire posts because people can't follow the rules.

EDIT: Apparently Khatovar was reading my mind. o.O


Second, (to Shodokan) the bots in question that were mostly targeted in this banwave read the game's memory and unlock Lua code that Blizzard has specifically and purposely protected -- All of which ISBoxer has absolutely nothing to do with, so you can stop your comparison right there. Programs like HotKeyNet and AutoHotKey have much more "functionality" in this department than ISBoxer ever has, but both of those programs are viewed as legitimate multiboxing programs on this forum.

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

/castsequence reset=0.5 0,0,0,0,0,Judgment
/castsequence reset=0.5 0,0,0,0,Crusader Strike
/castsequence reset=0.5 0,0,0,Exorcism
/castsequence reset=0.5 0,0,Judgment
/castsequence reset=0.5 0,Divine Storm
/castsequence reset=target/15 Crusader Strike,Judgment,Inquisition,Exorcism,Templar's Verdict,Word of Glory,Crusader Strike,Judgment,Divine Storm,Exorcism,Templar's Verdict,Divine Storm
/cast Avenging Wrath
/cast Execution Sentence
/cast Guardian of Ancient Kings
/startattack

[MadMilitia]

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.

[Khatovar]

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?

Steps are no different than using Swapactionbar. I can throw all my spells/macros on slot one of every bar in game and tack /swapactionbar on and 1 is suddenly hitting a different macro every time.

As far as the "do not advance for" thing, I'm not particularly for the ISBoxer version of it, but you can still duplicate a version of it using armor slots via the ingame macros or by using nulled castsequences with a reset conditional that you call in another macro further down your sequences such as -

Macro 1

/castsequence reset=target Corruption, nil
/swapactionbar 1 2

Macro 2 {or 8 or whatever}

/target pet
/targetlasttarget
/cast Shadow Bolt
/swapactionbar 1 2

Easy-peesey.

Having used these setups on solo toons that I didn't want to set up a HKN script for, the only difference is it's way easier and more elegant to do it externally, especially with multiple toons. All things considered, I don't find those actions grey at all since they are functionally identical to actions I can take with the ingame tools.

People get caught up in banwaves and people get it cleared on appeal. Some people also assume that multiboxing is a get out of jail free card for breaking other rules, but they never want to admit that.

You yourself claim that you've been contacted recently by GMs after you've been reported all week, so I'm far more of the mind that a ban wave was in the works and GMs trying to rush through confirming or clearing the who-knows-how-many reported and/or flagged as hacking/botting accounts {which we all know is what multiboxing gets reported as} and slack-assed the check so they could move on to the next ticket.

It's not "people got banned for boxing" it's boxers getting caught up in a banwave. That doesn't instantly equate to us doing anything that is automatically flagged, it could just be manual reports and lazy or uninformed GMs, like it usually is.