Emongg suggested a role queue system where you have 3 separate SR’s depending on what role you play.
But unless the Wins and losses of your other hero roles affect the SR of your main role, then all you would effectively be doing is giving everybody in the game 2 extra smurf accounts.
Works for a MOBA, doesnt work on OW where you can switch on the fly.
Switching to a critical role might even give you a win but be horrendous for your personal stats per min, same otherwise. Someone can be ultra performing in a role that is actually not impactful because of the map or team mates and then lose, and the system will punish that person for it.
The moment you introduce 2-3 variables, it doesnt become 2 or 3 times more complex, its a geometric progression.
When switch happens, it is about tanks switching to other tanks and dps to different dps and so on. Hardly anyone goes from dps to tank unless the person who was tank attempts to throw the game by picking the extra dps and someone else is forced to fill the tank role.
Hi, flex player here.
I do, like every match.
I mostly tank and then support or the other way around. Sometimes people want to play GOATS and many DPS end up in the tank role. If then I see damage is missing, i often go from Tank to DPS.
Its not that uncommon so you can dismiss it in order to implement a system that will absolutely be flawed if the switch happens.
I also flex but flex by the aspect of filling, as I let my teammates pick first what they find comfortable. The only roles that are left for me to pick is either tank or support and it does remain the same in the entire game unless I insta-lock something else.
In my alt account, I ’ force ’ my way in dps role or else I will end up in the same roles again and again.
In specific rank range from Diamond and below, unless you force your way through and step on others’ selfless nature and willingness to win, you won’t play what you want. Meaning, if you won’t stick to your pick no matter what others say, you won’t play what you want. This is wrong.
If they don’t change any major stuff in comp this will be a downgrade. Entirely removing role switches in general will make you loose to counter some stuff. As for example Genji is really good on attack on for example Hollywood for particularly the first point. However he can be difficult on the first payload phase and he might be better of as a winston there. And for the last phase he could switch back to put more pressure on enemys during the engagement phase. The Problem is its not common to do those switches even though they are oftenly done in the pro scene. However roleque would force this to make the genji player not be able to switch at all. I see the downdraft but on the other hand i think the most common problem is that people just want to play a specific hero for a match. Therefore the best idea i think is having a a prematch lobby where you can get in touch with the people before entering a game, you might even include some playerbased rules , so if you go into a match you cant break those. Like lets say you want to have a fixed role que you could do it, but this also would allow switches in general. Its always better to have a strategie before randimly spawn in with 5 people which you know. I think this is btw. the road blizzard wants to take rather than hero bans and role select, since this is in the interest of most players, knowing what you have to deal with in a game.
Still dont see how its relevant.
Filling and Flexing are 2 separate things. Mostly all “fillers” are flex players but not all flex players fill.
Anyway, what is relevant is that given how that SR would track your hero usage, it is exploitable and flawed. That system works in Mobas, doesnt in OW. Point still stands.
You can have role queue with out role enforcment. While you can still have throwers and trolls like every game mode, it atleast would atleast set a reasonable expectation how each person will play while still allowing freedom of non-standard strats. (And ofc still allow switching)
No more 6 dps teams with everyone hoping someone else switches.
Exactly. There will be not-so-nice-people who queue with the ill intention to pick a different role than the one they are queueing for. But it’s the small price we’re paying to have a more flexible rolequeue system. Not to mention, like you already did, there already are throwers and alike in games so there’s really no point in restricting roles. All that would do is create the awful situation of playing against an enemy comp that requires you to have 3 tanks, DPS or healers while you don’t have the option to pick any more than 2 of each.
Trying to police smurf accounts is a fool’s errand. Unless you want to tie peoples’ accounts to personally identifiable information (like a SSN, which is probably illegal in most places) there’s never going to be a way to figure out who is who unless they’re stupid enough to stream. That’s why Blizzard doesn’t bother.
There are more directly gameplay-centric problems with Role Queue as it is, like the fact that being good with Zarya or Winston has no being whatsoever on whether someone is good with Reinhardt or Wrecking Ball. It’s far worse with DPS, where heroes can be good with a few DPS and hot garbage with 8.
What’s that? Neither your Junkrat or Mei can play a competent hitscan or Hanzo and the enemy Pharah is bombarding everyone uncontested? Your Zarya plays a solid McCree? Too bad, bucko.
Both of those issues are also present in regular matchmaking, even amplified. Because besides the chances of not having a specific hero (hitscan) of a given role (DPS) theres also the chance of not having any heros of a given role or too many. How many times did you have to endure a team consisting of 3 or even 4 players insinsting to play DPS? Or games where your only tank is a Roadhog?
Rolequeue, as suggested by me, isnt a perfect solution, but its certainly a better solution than no solution. And no, LFG doesnt count. Depending on the time of day theres hardly anyone using it and to quote my own post:
With rolequeue the chances of decent games are raised, not locked at 100%. But unless anyone comes up with a better solution I dont see any reason not to implement it.