Really guys? I know this is the end but did you have to just dig at us for supporting you?

Interface: 60000

See this is what people have hated about you. Yes, you made a service people are thankful for but your attitude, nonsensical additions, and bloat followed by new releases just to add something nobody wants is the reason I'm glad Blizzard took this over.

I guess I'm thankful that enough people used something like this to get them (Blizzard) to take notice but I can't help but think that if you weren't so stubborn and actually made a non bloated product, this might still be around.

Sorry but people like you make me mad. You got banned for a reason and not a BS one or you would have petitioned and got back your account, not create a whole new account.

Face that doing something bad got you banned and accept it and the loss of dkp, etc.

If you don't have the latest oqueue, that's what's happening. 1.9.7b us what you need to be running. If you are still getting the error then this version has the same bug in it.

I think this is broken by allowing BG ratings to dictate raid requirements. PVP should not be allowed as a condition for raiding.

Looks like it was a cache issue and new files not forcing a css overwrite. I cleared my cache and it is working ok now.

Your CSS is horribly broken on the new site layout and everything is crashing into each other on your forum layout.

Disable auto invite.

I clicked on a raid in oqueue and went afk after not thinking they were inviting (like 15 minutes). I had closed the oqueue window and thoguht nothing about it. I went afk after that 15 minutes and came back about 30 minutes later to find I was in the raid.

Can you let us know if there is a way to prevent auto inviting? There should be a request to join that you can accept or decline but it should not just auto join you. that's slightly distrubing and intrusive.

Not sure if you are willing to make any changes now that Blizzard has pretty much shut you down once wod comes out but I wanted to see anyway.

Oh and the having battlenet "friends" be added even when the addon is disabled is pretty much just wrong.

No, your ilvl is not sufficient to get you into heroic raiding for soo. It;s not that you are invisible, it that you aren't meeting whatever requirement the raid leader requires.

Heroics generally require around 570 to start

My suggestion would be to curtail the use of scorekeeper or at least allow it to be disabled. The anciallry feature of oqueue are causing latency and fps issues as well as the yet to be resolved issue of battlenet going offline when switching to alts.

Seeing how almost everyone uses oqueue for making groups and raids, can we work toward being able to control the aspects we do not use but tend to eat away at limited resources?

What does this have to do with oqueue aside from this person using the addon? Why should they have to share with anyone? They are carrying out a contract with another person and simply creating a raid to facilitate it.

I agree with Alcance, anyone who pays 10k for a flex run is an idiot.

With 1.9.4 my fps has taken a hit. When disabling oqueue via "go dark", my fps jumps 10-20 frames.

I posted separately but when changing characters, battle net goes down every time now.


Oqueue still blocks the ability to right click and report a player.


That's pretty much the issues I see with the latest version and oqueue in general.

Battle net goes down when switching characters

With 1.9.4 it seems that everytime I switch to another character on my account, battle net goes down. I have tested for a few days now by making sure oqueue is disabled in addons on all charcters and do not have any issues. As soon as I re-enable oqueue and swap characters, bnet is reported as down as soon as I change to another character.

While this has gone on off and on for several verions, it seems that 1.9.4 does this every time now.

I do my best to keep my battle tag friend list to 6 or fewer so the friends list is never too large. It seems that something in oqueue and switching characters is causing the disconnect with bnet.