On my 555 mage I've been trying to get into some normal 10/25 Garrosh kills on oqueue. I have qualified checked, and yet for some of them I get an error when trying to queue saying "not qualified: raid lockout". Now, I understand how the raid lockout is supposed to work in oqueue. However, my particular issue is that my mage HAS no lockout for SoO this week. I'm 0/14 for this week. Why am I still getting raid lockout errors on some of the ones I queue for? I'm running the latest version of oqueue.

Do the leaders of those premades also have 0/14 lockout? If you have 0/14 lockout, and the leader of the premade has 2/14 lockout. You now have a conflict. The lockout works boths ways, where if the leader has a lockout of 5/14, then if you have a lockout of < 5 || > 5 then you now have a conflict.

Hmm...that would make sense, except I'm currently queued for Garrosh kills where raid lockouts are showing as 13/14 without an error. I have had a few give me a not qualified error though, even though my item level is at or above what's listed as the minimum.

I'm honestly not sure why the lockout would be set to work both ways. If I've killed nothing in normal SoO this week, then theoretically I could get into any normal SoO raid on oQueue, provided I meet the other requirements (item level, class, etc). If it's intentional by design I believe it should be re-examined.

i have allways "raid lockout" problems when i already killed a few bosses and I try to join a list where the premade contains the information [0/14] so "none of the bosses killed yet" but curiously in the premade description is the info "at JUGGERNAUT" for example (or "at KOR'KRON" and so on)... Of course the program is functioning very well and is checking if i have the right with 5 killed bosses to join the list where the next boss to kill is the 6th one - Juggernaut! The program checks not the info "we are before Juggernaut" but the information in the "blue bracket" and that should be [5/14] !! but IN THE 60% OF CASES where premades are not at the first boss there is still [0/14] ... That means it is impossible to come on the wait list when this field was not updated everytime when a boss was killed and the info remains [0/14]. The only people that can join these lists are those who didn't killed any bosses !! they can join the list and begin with Juggernaut... This means there are premades that are waiting for 1 person to join because one left after a boss kill, and the only people who are comming are wondering why is not immerseus the actual boss like in the description [0/14] and then they leave.

I think it's a design issue: when creating the premade, the creator fills in the fields Type: Raid, Subtype: SoO of course... but if you want OQ to not check raid IDs/boss down, you must leave the subtype empty. This should be made clear somewhere, maybe with a pop-up, or just add a "Garrosh only" subtype ?

I'm still getting this issue. i cant que for Garrosh even though I'm not locked out to him.

Why on earth would a raid lockout conflict happen if your 0/14 and RL is 1/2/3 etc/14 ? that would not be a conflict.

Is there some sort of issue as to why it does this .. or cannot be fixed?

this happens all day on all of my chars now .. how can one just disable these lockout checks in the first place assuming the RL was lame enough to select soo subtype.

Trying to do siege on 1 char and garrosh on a few others and every group is raidlock conflict when there is no conflict at all.

also, lets not get started on haveing a H lockout and joining a normal (or is it all the same problem)

It is a great mod and all but since these lockout checks have came its been a massive pain in the ass and nearly unusable except for fresh runs now.