BG Queue Assist AddOns

[MiRai]

Word on the street is that patch 5.1 has broken said add-ons. I'm sure we'll find out shortly if there is a workaround for this or if this is a permanent change.

Blizzard has mentioned before that they frown upon these add-ons, so this could be the end of them.

[daanji]

Yep. Looks like Blizzard changed the API slightly to break the JoinBattleField function.


The entire Battle ground PvP community is up in arms over oQueue being broken.

More details can be found here

1. TinyMasher's Thread Introducing oQueue (deleted)

2. Main Complaint Thread asking for a Response (UI and Macros Forum, thread is now capped)

2A. Main Complaint Thread asking for a Response Part 2 (UI and Macros Forum)

3. EU Thread

4. Tiny's EU Thread

5. Tiny's New oQueue Introduction Thread

6. Tiny's BG JoinBattleField Thread

7. GhostCrawler's Stance on Premades


Voice your opinion and let them know what you think of this change:

https://twitter.com/Ghostcrawler
https://twitter.com/CM_Zarhym
https://twitter.com/robpsimpson

Looks like Ghostcrawler already reponded with this

>Greg Street ‏@Ghostcrawler
>@Skyl3lazer I *think* that was an unforeseen consequence of a change we had to make to >prevent an exploit. We'll investigate more.

[ebony]

most the topics have been deleted on this.

[JohnGabriel]

Maybe just maybe it was an accident and blizzard will bring it back.

He would know if they made a change like that on purpose right?

Skyl3lazer ‏@Skyl3lazer @ghostcrawler Please respond, you broke oQueue


Greg Street ‏@Ghostcrawler
@Skyl3lazer I *think* that was an unforeseen consequence of a change we had to make to prevent an exploit. We'll investigate more.

[daanji]

Wow! Guess that means they responded alright.

Deleting all the topics threads sends a nice, clear message of "We don't care."

This will just enrage the PvP community more. I'm sure 10x threads have already been created in protest.

oQueue was recently featured on Reddit, so I'm sure the Reddit community will mobilize soon enough.


Hopefully Blizzard will at least have to acknowledge this.

[Khatovar]

Wow! Guess that means they responded alright.

Deleting all the topics threads sends a nice, clear message of "We don't care."

Or it sends a nice clear message of "don't spam create threads if there's already one on this topic." Considering 3 of the 4 threads you linked are still active, I'd hardly call that a great big FU.

[daanji]

Or it sends a nice clear message of "don't spam create threads if there's already one on this topic." Considering 3 of the 4 threads you linked are still active, I'd hardly call that a great big FU.

Well, it may be considered spam by someone who is not a vested member of the oQueue community, but I'd lean towards calling it a protest or a demonstration.

Blizzard has a history of ignoring the PvP community and omitting certain feature changes in patch notes without ever acknowledging them. In the past, it has taken formal protests (IE forum spam, as that is really the only method we have to be heard) to get a response from Blizzard or even acknowledged.

Sarcastic tweets from the Lead System Designer doesn't help in this regard.

I am against spam as much as anyone, but the oQueue community is very large and each individual finds out about the change in their own time and creates their own thread.
If you observe the threads, the majority of the posts are users who rarely visit the forums from a lot of different users. It is not a handful of people spamming the thread (except for the trolls, who seem to be very active).

Now, as to my comment on Reddit, it was more of an observation on that community. They have a tendency to mobilize on topics they feel passionate about, so I anticipate at least some organize response from those users. I am not advocating they do so as non-constructive spam is pointless. However, formal and organized protests can be useful. Blizzard values our feedback and opinion. Sadly, it seems the only way to get important community topics noticed is to be loud and verbal.

Case in point, Blizzard relocated the Leave Battleground button to be right next to the Show ScoreBoard button. Unfortunately, this caused people to accidentally click on the wrong button and get the deserted buff. The battleground forums were aflame with posts from tons of users who hated this change and wanted it moved. Blizzard did not acknowledge or respond to this issue that many in the PvP community felt was important. Yet, with 5.1 they finally relocated a button. Sure, it is a small change that only affect a small amount of people, but it does show that by protesting and making your opinion heard, you can influence the game.

[heyaz]

Hey. Relax.

Forums get flooded with garbage, threads quickly derailed and turned into flame wars, and a flurry of duplicate posts about the same issues. From a forum moderator's perspective, I can understand what may have happened to a lot of the threads. I would really try not to blow a gasket over what happens or doesn't happen in forum threads on battle.net, or anywhere for that matter.

Let's chill out a bit and wait for an official response? They already acknowledged they are aware of it. "Mobilizing" a bunch of internet retards and threatening to cancel your accounts and this and that isn't going to speed up their processes inside Blizzard.

They've removed/blocked API functions many times to stop exploits or other creative use of game mechanics by abusing the API, often times breaking legitimate addons they that they did not have a problem with. I'm hoping oQueue and other premade BG type addons were not a target... they really shouldn't be. I still remember when they broke Decursive in vanilla... on purpose, and it sucked by I understood why. I hope that wasn't the intention this time - to break addons.

Although I like oQ, have loved premades since Vanilla and used Premade AV Enabler and even led raids manually, ultimately we can survive without it. I really doubt many of you are going to cancel your accounts; it's hard to believe your entire reason for playing wow - leveling up, gearing, multiboxing, was to do AV rath strats using OQ endlessly... as fun as it is, there's plenty more to do...

[F9thRet]

And this ladies and gentlemen, is reason # 42 of why I love our community. I know exactly where Heyaz is coming from, from Moderating not just gaming forums, but Political forums, and everything in between.

But yeah, IT is a bummer, I was planning on throwing some Shamans together, and finish leveling them to 90 via BG's. Oh well, it happens.

Hey. Relax.

Forums get flooded with garbage, threads quickly derailed and turned into flame wars, and a flurry of duplicate posts about the same issues. From a forum moderator's perspective, I can understand what may have happened to a lot of the threads. I would really try not to blow a gasket over what happens or doesn't happen in forum threads on battle.net, or anywhere for that matter.

Let's chill out a bit and wait for an official response? They already acknowledged they are aware of it. "Mobilizing" a bunch of internet retards and threatening to cancel your accounts and this and that isn't going to speed up their processes inside Blizzard.

They've removed/blocked API functions many times to stop exploits or other creative use of game mechanics by abusing the API, often times breaking legitimate addons they that they did not have a problem with. I'm hoping oQueue and other premade BG type addons were not a target... they really shouldn't be. I still remember when they broke Decursive in vanilla... on purpose, and it sucked by I understood why. I hope that wasn't the intention this time - to break addons.

Although I like oQ, have loved premades since Vanilla and used Premade AV Enabler and even led raids manually, ultimately we can survive without it. I really doubt many of you are going to cancel your accounts; it's hard to believe your entire reason for playing wow - leveling up, gearing, multiboxing, was to do AV rath strats using OQ endlessly... as fun as it is, there's plenty more to do...

[valkry]

Hey. Relax.

Forums get flooded with garbage, threads quickly derailed and turned into flame wars, and a flurry of duplicate posts about the same issues. From a forum moderator's perspective, I can understand what may have happened to a lot of the threads. I would really try not to blow a gasket over what happens or doesn't happen in forum threads on battle.net, or anywhere for that matter.

Let's chill out a bit and wait for an official response? They already acknowledged they are aware of it. "Mobilizing" a bunch of internet retards and threatening to cancel your accounts and this and that isn't going to speed up their processes inside Blizzard.

They've removed/blocked API functions many times to stop exploits or other creative use of game mechanics by abusing the API, often times breaking legitimate addons they that they did not have a problem with. I'm hoping oQueue and other premade BG type addons were not a target... they really shouldn't be. I still remember when they broke Decursive in vanilla... on purpose, and it sucked by I understood why. I hope that wasn't the intention this time - to break addons.

Although I like oQ, have loved premades since Vanilla and used Premade AV Enabler and even led raids manually, ultimately we can survive without it. I really doubt many of you are going to cancel your accounts; it's hard to believe your entire reason for playing wow - leveling up, gearing, multiboxing, was to do AV rath strats using OQ endlessly... as fun as it is, there's plenty more to do...

I'm not too worried, seems they are aware of it and didn't intend for it to happen so fingers crossed they fix it back. As for decursive, I never used it, and I used to heal up to naxx back at lvl 60. Xperl, ktm and dmg meters were the only addons I used, then later pirate speak

Edit:
/click StaticPopup1Button1
/Click ExtraActionButton1
/click LFDRoleCheckPopupAcceptButton
/click LFGDungeonReadyDialogEnterDungeonButton

will still get your whole group to join a BG