The attached image describes the issue but I will reiterate it.
#To ensure fair team elo in 'captain mode' -the 'first pick' captain should NOT be selected randomly.
iron dagger
Basically some hubs with matchmaking get griefed by having the 'first pick' be assigned to the wrong captain - because it seems to be assigned completely randomly. This is an issue in hubs where there is a wide range of skill levels.
After picking the two captains, FaceIt should run a simple simulation. It would simulate two cases where each captain gets first pick and picks players in order of elo. It then compares the two cases and awards 'first pick' to a captain based on the case that had the closest average elo between teams.
This is the match in screenshot. It's not the best example I could find but it's the one I managed to take a screenshot of. Captain picks are not saved in post-match, unlike server or map vetoes.
There are much worse examples (usually involving player with 3,000+ elo) where the match could've been balanced, but isn't because the 'first pick' was assigned to the wrong captain.
stray nexus
elo doesnt matter that much, its a very small difference. Literally matter of few matches
iron dagger
elo doesnt matter that much, its a very small difference. Literally matter of fe...
It can be a difference of over 300 elo (between teams) with a 3000 elo player in the lobby - which is over 2 faceit levels. I've experienced that many times when queuing in hubs (Mythic Ruby/Gold). It is a big deal.
Either way, this change would only improve matchmaking in hubs. There is no drawback.
stray nexus
It can be a difference of over 300 elo (between teams) with a 3000 elo player in...
oh alright now i can see how it could make a difference on high levels