No wintergrasp battles as multibox on ICC

[agenis]

Hey guys, since today multiboxers seem to be unable to join Wintergrasp battles on the Icecrown server with more than one character. While I can see the benefits of this change, I don’t understand why the Warmane staff failed to announce it.

Will this change make its way to the other servers too?

Share your opinions — is this the beginning of the end of open-world multiboxing on Warmane?

[DarkPaladinS]

its really good if they did so now actual players can play the game

[nqkvomomiche4]

The problem is not wether it should be prohibited, IT SHOULD. Problem is why they are doing it now when horde is after YEARS dominating WG in prime hour?!

[Ltyrantboxing]

this is Great, waiting for Warmane to ban Multiboxing completely.

[Obnoxious]

While I can see the benefits of this change, I don’t understand why the Warmane staff failed to announce it.

Always so easy to push blame for your own shortcomings.

[Bxera]

Always so easy to push blame for your own shortcomings.

I can understand the reason it was done without prior notice, given what happened last time.
Everyone should just be happy it’s not a blanket block/ban, but only when queue is full.

[Baartleby2]

I can understand the reason it was done without prior notice, given what happened last time.
Everyone should just be happy it’s not a blanket block/ban, but only when queue is full.

Basically nothing has changed. Every multiboxer/premade queues with macro spam. This will have minimal impact. Should rather have x-amount of multiboxers allowed per WG instead. Would probably be hard to implement, but it would make WG more fun.

[Leondrea]

Massive W from Warmane for this change. They finally have listened to their players.

[Obnoxious]

Basically nothing has changed. Every multiboxer/premade queues with macro spam. This will have minimal impact. Should rather have x-amount of multiboxers allowed per WG instead. Would probably be hard to implement, but it would make WG more fun.

Can "the macro spam" hide the fact they are all coming from the same machine?
It's a rhetorical question, before you actually try to answer. If they did that, multiboxers would also routinely be breaking the five simultaneous characters limits as well. Even with that aside, it's an official limitation for joining that, so players finding a way to break that would be liable to be reported.

[Baartleby2]

Can "the macro spam" hide the fact they are all coming from the same machine?
It's a rhetorical question, before you actually try to answer. If they did that, multiboxers would also routinely be breaking the five simultaneous characters limits as well. Even with that aside, it's an official limitation for joining that, so players finding a way to break that would be liable to be reported.

No, and I may be misunderstanding the rule change then. I thought it meant that the multiboxer wouldn't be able to queue like "normal" players once the battle started, and people were standing in queue, waiting for someone to leave.

If it only allows multiboxers to fill up spots when the WG isn't already full, WG will improve ten fold. This is a good change, imo. And long overdue.

[micrologusk4]

Couple of things to notice here:


First, momentum of the change is troublesome. Change comes less then a month of alliance getting camped by horde premdes in prime hours. That hasn't happened last few years. People were missing WG on aliance for years because of multiboxers. It makes horde players feel like their efforts are being sabotaged by administrative decisions.

Second, change won't fix problem of ADDON/MACRO being used by premades to get priority que over regular non-premade players.

Third, change benefits side that is more PVP populated. Horde was largely dependant on multiboxers. Now multiboxers will be able to join only when there is under 120 people in que and there is no way to decide which multiboxer gets inside which basically makes them unusable.

Fourth, If horde pvp guilds decide to swap to aliance now because of this change, how will you deal with inbalance? People were complaninig on missing que because of multiboxers for years on aliance and nobody cared to do anything about it.

Fifth, you are straight forward lying about making announcement before implement change because checking /devlog you can see post was made on february 12 and change was already active last evening (11th).

[agenis]

Always so easy to push blame for your own shortcomings.

Maybe not everyone is checking on the devlog changes everyday? Also, funny how you just ban people for staff disrespect while disrespecting members of the community, then you just delete all theirs and yours replies.

[Obnoxious]

First, momentum of the change is troublesome. Change comes less then a month of alliance getting camped by horde premdes in prime hours. That hasn't happened last few years. People were missing WG on aliance for years because of multiboxers. It makes horde players feel like their efforts are being sabotaged by administrative decisions.

You're free to "feel" however you like - about an unambiguously positive change for the general players, on top of it. We won't entertain conspiracy theories.

Second, change won't fix problem of ADDON/MACRO being used by premades to get priority que over regular non-premade players.

This isn't what the change is about.

Third, change benefits side that is more PVP populated. Horde was largely dependant on multiboxers. Now multiboxers will be able to join only when there is under 120 people in que and there is no way to decide which multiboxer gets inside which basically makes them unusable.

Your reliance on multiboxers isn't something that should be taken into consideration. Regular players were being left out because of too many multiboxers. Take your complains to the people overdoing it.

Fourth, If horde pvp guilds decide to swap to aliance now because of this change, how will you deal with inbalance? People were complaninig on missing que because of multiboxers for years on aliance and nobody cared to do anything about it.

That isn't a concern for this change or something that should stop it from happening.

Fifth, you are straight forward lying about making announcement before implement change because checking /devlog you can see post was made on february 12 and change was already active last evening (11th).

Don't call me a liar. That's something I don't take lightly, as you will realize as soon as I'm done with this post.
Your inability to understand time zones and the fact server time could already be the 12th when the devlog was posted isn't my problem, just like neither is you reading what wasn't even typed.

[Obnoxious]

Maybe not everyone is checking on the devlog changes everyday?

Maybe everyone shouldn't make claims about "failure to announce" if they aren't.

Also, funny how you just ban people for staff disrespect while disrespecting members of the community, then you just delete all theirs and yours replies.

Good thing that you found it funny. You can be part of the joke too, it's easily arrangeable. You're on the right track already.

[thebotz]

Small question about this - if a multiboxer successfully joins the battle due to there not being 120 people in the queue at the start of it, will they then be allowed to stay no matter how many people queue up later during the battle, or does this new system actively remove them once the battle becomes full?