Forums are in read-only mode.

Bug: OQ keeps setting my Battleground rating to 550

Every time I make a premade, it gives me an error, saying I don't qualify, even if I leave all the requirements at 0. When I look back, its changed the battleground rating to 550. How can I fix this? I've tried logging, reloading UI, reinstalling OQ, nothing works.

Also, when i scroll over raids that I'd normally be quallified for, it says my rating is too low, so I think other people might be having the same problem.

it sounds like you might be a bit confused.

raids don't use ratings. rbgs and arenas usually do.

if you jump into vent, maybe i can help clear up any confusion

wow.publicvent.org : 4135 room 0

He isn't confused. Several are having the same issue, myself included.

With no data, or even a 0, in the "rating" portion of the "create premade" for a raid set up my toons are "not qualified" because "rating is too low." It seems to also be stopping others who "don't qualify" for this mysterious rating to wait list.

I have tried removing the saved variables, fully unpacking/installing, and various toons with the same result on all of them. This started after I personally updated to the newer version.

Doing some test premades with the following data on this:

Without changing anything on the left side of the panel, only changing the Premade Type, and having all ilvl, resil, rating, description blank, with enforce level bracket checked, the following is noticed:

Premades are fine for Arena, Battleground, Challenge, Misc, Questing, Rated BG, Roleplay, Scenario

Premades are "rating too low" for: Dungeon, Raid

Sorting with "qualified" checked filters my own premades out if set to Dungeon or Raid under these conditions.

no, kreskell was not confused... it was a bug that pops out if you have no pvp rating. this was due to a new capability i added that allowed you to see the lowest ilevel in a premade. in order to do that, i had to reuse a data field that is used for mmr rating for non-raid groups.

thanks again, kreskell for helping me find and stomped that bug.

you'll find the update in 1.9.7a ... now available

Tested update, works fine now