Quote Originally Posted by Cyphoner View Post
Well i am not sure whether they changed policy or not in specifics when it comes to multiboxing.
This in fact is a little scary.. The other day when i spoke with account support with a guy called Steve who also work as a gamemaster, told me that:

"Multiboxing is allowed, such as running several copies of the game - But automation such as some of the programs offer by sending a key to each and every window while not having to actually use that window is not allowed. That's when it becomes automation."

So i asked, well then, if multiboxing is allowed but not programs like isboxer, keyclone etc.. Then it's not really multiboxing is it?
Maybe i got the wrong idea of what multiboxing actually is but opening 2 windows to trade with yourself i.e is not what i refer to as boxing.

I tried to argue with him saying that i, a person, still have to sit and press the keys on my mainwindow for the other clients to do anything - They won't do anything at all unless i "tell them to".

But he didn't change his mind, it was, according to him something you could get banned for - Usually 3 hour only however since it is considered a "minor" offense, but repeatedly it may permanently close your account.

Regardless of how it is, i find it hilarious that they expect you to run i.e 10 clients and open #1 click a spell, open #2 click a spell, open #3 click a spell, open #4 click a spell, open #5 click a spell etc. and that it would otherwise be automation on window #2 - #9..
They didn't change their policy, and if they did, it wouldn't be a "secret". We would all know about it through a public announcement or a sticky in the forums. GMs don't have all of the answers and they can have a difficult time interpreting Blizzard policy.

Quote Originally Posted by Cyphoner View Post
I wonder though, is there actually a blue post saying that using programs like isboxer is fine? I've seen blue posts saying multiboxing is allowed but nothing about the programs sending the keystrokes to the other clients?

And if Blizzards definition of multiboxing is simply to run multiple clients but only control 1 at a time.. :-/
As it's already been stated, Blizzard isn't going to specify software that's legal for multiboxing because they have no control over it. If later today they said that Software-X was completely legit for multiboxing World of Warcraft, and tomorrow Software-X decided to add automatic delays to its features (which would be against Blizzard policy), then what does Blizzard do? Make a brand new announcement less than 24 hours later that they were wrong about Software-X and that people should stop using it immediately?

What if people only saw the first announcement, but not the second? Are they then at fault? If Blizzard began banning accounts that were using Software-X, how could someone prove that they hadn't seen the second announcement?

Blizzard can't police all the third-party software that's out there to make sure that it's "World of Warcraft Approved!" and they certainly aren't expected to. They keep their rules vague to make things a little easier for them, but unfortunately, this then leaves them open for interpretation by any idiot on the Blizzard forum that dislikes multiboxing.

Quote Originally Posted by Cyphoner View Post
Nothing except that most of the statements are from the stoneage, but i saw there was a "recent" one on page three, so no problem here, you?
Again, as stated before, their policy hasn't changed and Blizzard isn't going to put out bi-monthly announcements stating that multiboxing is still allowed. If the policy changes, you'll know it.

Quote Originally Posted by valkry View Post
I have that macro if you want it, but I'm pretty sure it is against the rules to use it so I would advise against it. I certainly haven't used it since being told it was not allowed about 4 years ago (back when the first big wave of bots started).
I'm almost positive that mass report macros were broken and the report function is now protected as of the latest patch (5.1). What that means is that it now requires a hardware event (e.g. a keypress or mouseclick from the player) and can no longer be automated through a /slash command.