players banned for queueing av with /script macro

[Badtank]

But they won't reverse the bans because it would make them look stupid or something.

I don't think the nost dev's need to do anything more then they all ready have to cause this to happen.

[tuscany]

This is certainly not an exploit. We used to do premade AV in TBC even.

Could someone quote the admins saying this is what the reason for the banwave was? I didn't see them mention it and am legitimately curious because, if there was a different reason for the ban, we deserve to know.

I don't want to get banned for doing something accidentally. I was kind of hoping we would be able to do premade AV like we used to do with addons.

edit: the proper thing for the admins to do in this case would be to show reconsideration given community discussion. it's certainly not an exploit, and if they did not want this in the game, they could have disabled it and rolled back their HK/honor rather than issuing a temp ban. That would even be a little much, but hopefully enough to satisfy the QQ'ers while still saving some face.

[Solliden]

Frankly, the underlying theme here is this server isn't meant for people who want to be competitive and progress through content. The BWL fiasco should've hinted at this. There's no place for good players on this server, the GMs want the casual audience. This has fuck all to do with scripts or proper queuing. Y'all need to take a hint and just leave.

[killuminati]

This is crazy.

I posted before that I actually acquired explicit permission from a retail GM back in... 2006 maybe to use Stinkyqueue. BUT the more I read, the more I realize how stupid this is and I'm glad they're not allowing people to use it.

I think they SHOULD explicitly inform players what is against the rules and what isn't in this regard. Particularly with LazyPig. AV was very rarely premaded on retail in my experience. My guild did it a couple times for fun after patch 1.13 or whenever honor became a currency.

I don't think people should have one week bans over this, but people are making a huge deal out of nothing as far as premading AV. It's a tryhard thing to do in the first place. Do you really need 39 people in vent with you? It's AV, get over yourselves.

[meyahx]

this server isn't meant for people who want to be competitive

What is competitive about using a macro to premade queue a AV? Get a grip nerd

[Stalk]

You could not premade Alterac Valley in vanilla World of Warcraft with a group queue. Some of the players that were doing this have claimed to have played on original WoW servers and should be well aware that queuing for AV did not work this way. The API call JoinBattlefield was disabled for AV on live servers.

http://wowwiki.wikia.com/API_JoinBattle ... did=184010
"Queue as a group if the battleground will allow it, which is currently everything except Alterac Valley."

Some players here like to cast the first stone at the server administration. However, most of us seem to be ignoring the fact that some of these bans went to players who had access to the test realm yet we do not know exactly if this issue was ever discussed between these testers and the server staff.

Bans seem a bit harsh though. However, resetting AV reputation and wiping any items gained from this ordeal seems fair enough to me after a clear warning has been given.

[Ultima]

http://wowwiki.wikia.com/API_JoinBattlefield?oldid=184010
"Queue as a group if the battleground will allow it, which is currently everything except Alterac Valley."

u got this in the wrong context and every programmer can confirm, i told u in anther thread already

Bans seem a bit harsh though. However, resetting AV reputation and wiping any items gained from this ordeal seems fair enough to me after a clear warning has been given.

inbefore any actions they just could have asked them to stop and they would have stopped for sure...

[sidesprang]

You could not premade Alterac Valley in vanilla World of Warcraft with a group queue. Some of the players that were doing this have claimed to have played on original WoW servers and should be well aware that queuing for AV did not work this way. The API call JoinBattlefield was disabled for AV on live servers.

http://wowwiki.wikia.com/API_JoinBattle ... did=184010
"Queue as a group if the battleground will allow it, which is currently everything except Alterac Valley."

Some players here like to cast the first stone at the server administration. However, most of us seem to be ignoring the fact that some of these bans went to players who had access to the test realm yet we do not know exactly if this issue was ever discussed between these testers and the server staff.

Bans seem a bit harsh though. However, resetting AV reputation and wiping any items gained from this ordeal seems fair enough to me after a clear warning has been given.

it was possible just look at posts from 2006 aka end of vanilla. http://www.skryer.com/forum/showthread.php?p=3852

[Nain]

lol

[PriestInOurTime]

If they don't want this functionality, that is fine even though blocking it isn't Blizzlike. But banning people for doing exactly what was done in vanilla and wasn't ever sanctioned in any way, shape or form is simply unreasonable. What's next, banning people for using Decursive? That might sound silly, but Blizzard didn't originally intend for players to make decursive even though the functionality was readily available, it was however tolerated and eventually changed to no longer be possible. Sounds eerily familiar doesn't it?

Banning players because devs feel that something is unintended even though it was tolerated and never changed during all of retail vanilla is frankly frightening. You can download an addon, use it as intended, and get banned. That should NEVER happen.

When the server announcement went out I assumed that players had used software to modify packets sent to the server or something. That had made these bans reasonable and even on the light side, as is though the bannings are a massive overreaction. This warrants a serverwide system message from the GMs to please refrain from using that particular API function in conjunction with AV and then hastily block it serverside. No bans, no permanent-record "warnings" on the accounts, just notification that the devs prefer to run the server with that functionality turned off.