The point of concern that I brought up here is that you’re trying to shoot for confirmation bias and use information that doesn’t suit the demands of what you want it to be to try to make claims it cannot.
The fixation you present is assuming the crux of the matching is on you personally and then derive information only about yourself to suit the claim of that demand and thereby ignore any other relevant information in the matchmaking to try to argue confirmation bias.
I’m not acting like there’s a ‘magical explanation’, but to people who deny possibilities, then yea, stuff suddenly seems like ‘magic’ when it comes to explanations they don’t want to hear.
The causation and correlation of what you want to deride (bad people in your matches) is coming from MMR appraisals from a system that’s not only optional, but is bad at anything beyond personal progress and sweeping generalizations from large sample sizes.
If you were so concerned why “why blizz matches” then you’d be posting information from the game itself:
-account levels
-match history ( win/lose streaks may shift confidence)
-be explicit about team pairings
(HoTS adjusts mmr estimations for groups in ways HoTSlogs doesn’t)
If hotslogs shows 8 or 40 games for people that had more than that, then the apprasial isn’t going to be great.
Similarly, if they seeded for hots confidence a year ago, and only just came back to the game, then that’s information relevant to their skill level that mmr estimations for quick match that likely aren’t going to be shown by looking at stat pages from HoTSlogs.
The point being: Hotslogs has lots of errors and doesn’t tend to paint a reliable picture for those looking to scrutinize particular details from it. eg: on 3/27 I lost 160 mmr points for Qm because of the “season transition” that ya know, doesn’t happen for QM.
Estimation jump hit all sorts of ways on these transitions when people don’t have a game played to show for it, but its part of the corrective assumptions Hotslogs makes to suit the demands of seeing matches that are made where it doesn’t know if it exceeding queue time perameters, had team mmr adjustments, and a number of other details that do influence the actual match maker.
and none of that has anything to do with whether or not these players should be matched, but rather the point is the sort of resources you’re trying to use to make a claim as a means to circumvent the stuff that actually does influence that sort of thing.
If people want to point out issues of the flaws of the system, then they should use the evidence from the system for those claims instead of something else that happens to suit what they expect. Its like the joke/story of the guy who’s looking for his wallet under a streetlight, not because that’s where he lost it, but because the lightning is better there.
a lot of these mmr-rant topics generally ignore the details of the other players in the loop to figure out how much of an outlier something might be, or other factors to influence it – maybe the lemon in question had a good streak, maybe they had a bad, maybe the mmr over estimates are influenced from another year, mode or the like.
But that’s not the sort of details people are going to convey cuz they don’t care to look into those sort of details. But the trouble is, having more details helps because there’s plenty of examples of the 1500++ lvl accounts that play like they’re never touched the game themselves, and then there’ s the gm smurfs with lvl 1 rerolls that stomp qm games for whatever reasons.
The functional concern is expressing details pertinent to the match making if your concerns are about the match maker rather than trying to rely on reactive estimations that sometimes toss in or take a couple of hundred points to simulate adjustments it wants to account for existing, but can’t apply on a game-to-game basis.