I would like oqueue to filter out players based on class/spec.

What do i mean?

I mean that when I create a raid/rbg group I can filter out classes I don't need. 

For instance. My rbg group is almost full, we are missing a mage, and all we want is a mage. So i could uncheck the option "ALL" and check mark "MAGE"

That way this could clear backend messaging clutter and save all those poor mages from wait listing every single group in the hopes they get invited. 

As a wait lister

I could use the drop down menu for rbgs then checkmark a second option maybe called " groups that need me " and that automatically filters out groups that I am qualified for and that need a mage. 




More examples.  Lets say I am a guardian druid. I would pretty much be needed in every group, and it would make very little difference for me. lol. But lets say I am on my rogue. All of a sudden I find my self hitting wait list in very few groups, and getting invited more rapidly. 

The benefits to such a filtering feature are great I think.

Anyone else have any thoughts about cons or pros ?

Yeah i think it would be epic if I am looking at the RBG list and next to "qualified" is a second check mark called "Wanted" 

Like right now, that would save me the hassle of wait listing for 10+ rbgs in the hope they want my rogue, who rarely anyone doubles up on. 

What are your thoughts on this ? Tiny

Any thoughts ? A feature like this would make filling groups a lot easier when creating new ones. 

it's been discussed in the past.  two things come into play with this; one is payload size on the messages and two... the biggest hinderance.. it would be a protocol change which means it would be a mandatory update.  those are very disruptive and i try to minmize those as much as possible.  unless i can find a way to do it without a protocol change, it drops in priority

Adding it as a filter true/false requirement shouldn't require a protocol change.   

Perhaps make it a requirement filter, much like the already stablished ilvl/res/bg rating requirements, one more parameter added to the string. 
"class" 
 

to avoid a protocol change, it would have to be something the existing versions would ignore.

there are 11 classes and 3 specs (tank, heal, dps).  this would require at least 14 bits which i can squeeze into 3 characters

so the premade payload would increase by 3 characters.  might be ok.  but the trick is still how to shoehorn it in so the older version accepts it without breaking

then comes the UI updates to accomodate it.  not sure how to show it on the find-premade tab and i would have to change the create premade tab to allow the leader to specify it

Yes, You're right Tiny. The Find Premade, Create Premade and Wait List tab will need a bit of UI work. It shouldn't be a major overhaul though. 

The changes could include these new features:

• For the Find Premade Tab:
  The newest version would simply include a new checkmark box, next to the send beer and qualified checkbox. This checkbox could be called: "Wanted"
  When a user check marks the "Wanted" box it removes any premade from view where their role isn't needed. So if i'm on on my Rogue looking for an RBG, all of a sudden instead of seeing 40+ listings on a friday night, i now see ONE. (if lucky)
  And a "waitlist" button coloring/tooltip modification.
• For the Create Premade Tab:
  (this is probably the one with the most work needed)
  As a Premade creator the user in the newest version will now have two new filtering options: One for classes role,with the respective 11 classes and 3 specs sub filters, and a second one. The first one is self explanatory. However the second, and most important, would be the option to "Block Not Wanted Classes/Specs" This can be added in the UI as a checkmark like the "Enforce Level Blacket" one. 
  Now, the "Block Not Wanted Classes/Specs" is what will really make all the difference for the newer versions and allow for more backwards compatbility. 
• For the Wait list tab:
  In this tab the new change introduced would be two sub views. In the Find Premade tab there would be two new sub-clickable tabs. One called " General " and one called " Wanted ".   General will have any wait listers that do not meet the current wanted classes/specs. And the wanted tab will include those who you still need to fill your group and you want. Your typical Guardian, Hpally, etc...

Phasing out the older version users yet still keep them in the loop could be done with a system that could work this way:

The filtering of being able to wait list or not would be done locally at the waitlister's client. So when a person lfg in the newest version tries to wait list to a group where their role isn't needed what will happen is that they see the Wait List button grayed out, or yellowed out, your choice, to differentiate from the current graying out criteria. And upon mouse-over they would see a  tooltip that tells them why: " Role not needed " ( so if they are a shadow priest, maybe theys switch to healer and try to wait list to that group as healer)

As a Premade creator you will see names pop up into your General tab in one of two ways:

1. You didn't select the "Block Not Wanted Classes/Specs"  Option, and they are not what you said you wanted when creating a premade. 
2. They are running an old version of oqueue, and also don't fit your wanted criteria. If they did fit your criteria, they would be placed in the Wanted tab. 

Let me know what you think, any thoughts, concerns, comments.  I have more details for each section to make them more functional, but this is the gist of it. Long i know, I apologize, i'm just really passionate about this idea, and of course, love your oqueue. 

P.S: Can you tell I hate rbging as a rogue? Because i do, i hate it. I end up leading/creating 95% of all my rbgs because goodfucking luck finding a group that wants your ass. 

P.S.S: If you wanted to hard introduce it, you could make the new versions have a new single token authentication using the password feature that only new users enter by default. Although that would make all the old versions come up with " wrong password " when trying to wait list. 

+20 Heal Cast @ Tiny for LargeBlockOfText fire damage

Tiny just posted this over on the facebook: