Constructive discussion on how to improve Dynamic Que. (Fixing Que Times)
So now that the hammer has come down and RIOT has announced they will not be bringing back SoloQue, and are openly admitting they are having troubles solving the problems that persist with Dynamic que, I think we should re-direct our discussion towards helping RIOT come up with solutions to fix Dynamic Que. The system isn’t going away, so let’s put our heads together and start offering real ideas and solutions to make this game great again.
NOTE: Please keep all comments focused towards ideas RIOT can use for making Dynamic Que work. Negativity is OK so long as you provide ideas or solutions rather than just complaining.
That being said, let me start things off with one idea I had.
Role Selection & Que Times: Something I found extremely informative was that in the round table video, one of the lead designers Socrates used a “jar” analogy for how role selection effects que times. He basically said if you fill up 5 jars (roles) with marbles at different rates, and each time you have 1 marble in all 5 jars you take one out of each jar (matchmaking), what would happen? Eventually a jar would overflow (causing long que times), and thereby suggesting that other buckets that filled slowly would never have enough (fast/instant que times)
It appears their original theory for solving this was allowing people to choose two positions so that “it would even out the jars”. At first this seems like a good idea, but when there is a required position that is not very attractive in the first place (support), then a large portion of the people are double filling all the other positions while support (jar) remains relatively the same (percentage wise).
If you combine this with the fact that pre-made groups pull from the same jars, then you are starving the hard to fill jars even further. Creating a HUGE bottleneck.
It’s clear to me now that the reason SoloQue/Pick Order system didn’t have this problem with que times was due to the fact everyone was considered “fill”; you had no choice. So using the jar analogy, “all the jars would fill evenly, all the time”. I think RIOT understands this and that's why they are offering to potentially re-implement this feature as a backup solution in Diamond + games.
But remember this comes at a steep cost - frequently not getting your desired role. Which is a core problem RIOT is trying to solve with Dynamic Que.
So instead of reverting back to that system, let’s identify the real issue here: There is a role (jar) that is consistently, and notoriously un-attractive to a large majority of the playerbase – Support.
**RIOT - You need to fill that jar. **
No, YOU DO NOT need to force others into taking a position if they don’t want to (auto fill or pick order, ugh)
You need to make that position ATTRACTIVE. You need to change or offer something to support class that drastically widens the player base. That alone will do more for your que times than any algorithmic change or fine-tuning ever could. This will effectively keep all the jars more equally full, AND STILL allow people to have control over the roles they get; Because more players will actually want to play support.
**Using one last analogy: **If you are baking a cake, and you have plenty of sugar, butter, flour, baking powder and milk, but are short on eggs... You wouldn’t double everything else to compensate. You would go to the store and buy more eggs.
So here is a question for the boards: How can RIOT make the support position more attractive? What else do you think they can do to speed up que times (without sacrificing role selection)
That's it for now, I'll be writing some other posts soon tailored towards specific issues Dynamic Que is facing and possible ways to address it.
Thank you for listening.
[slayer-pantheon-thumbs]