"YaeVizsla;c-1914299" wrote:
"No_Try;c-1914128" wrote:
I think the most common suggestion on the first MM brainstorming period was to look at multiple parameters in comparison. Whether we can agree on what those parameters should or should not be is another matter. But this one like all other brute force approaches are bound to fail because of that simple reason, it doesn't consider any of the intricacies of the game. And GP itself as a faulty measure couples with that fact.
"Multiple parameters" is not a suggestion. It is a lack of suggestion. The algorithm does look at multiple parameters already. But there's gotta be a weighting to them, and it's hard for us to assess on anything but the one principal parameter. And there always has to be a principal parameter. In this case, we're using pertinent GP.
What else does the matchmaking algorithm take into account? We do not know. And while you say pertinent GP is a poor measure, people cry foul because the most visible measures don't match up one-for-one, even things like number of zetas and number of G12s and number of +X speed mods (regardless of whether or where they're placed) which are also poor indicators in and of themselves, and become highly gameable if those are the principal matchmaking criteria. Or they point to, "Does my opponent have this one specific character I do not have?" as the principal indicator of whether or not a match is fair, which would be extremely gameable if it were made a hard line in the algorithm.
While GP is not a great measure, it's more difficult to game to such an extreme degree as some of the other suggested measures especially as the principal criteria.
There are improvements that can be made to the matchmaking algorithm and the GP formula. But it's been progressing along a reasonable course, and many of the other suggestions and non-suggestions would either be far more broken, far more gameable, or basically boil the mode to mirrors only.
Can you even be sure the algo is currently looking at any parameters beyond top X gp? I can give you concrete numbers what parameters to look at with what weighting and how much error thresholds if this was upto me, but it isn't. There doesn't need to be a principal parameters, an algo can simply check and match multiple parameters together with certain thresholds. i.e. consider a %20 threshold weighted in between zetas, g12, g13 and mod quality distribution (not the amount of speed of them), if need be this can be much more granulated with decreasing weighting to omegas and lower gear and the algo can balance loss in one parameter with gain on another (i.e. one player has less zetas but more g13s etc.)
Assuming that there really are different parameters applied behind the scenes right now, albeit softly (as said in one of the announcements I can't bother to find right now) they can simply dial the secondary weighting process up and that can also suffice too. And moving pertinent GP calculation beyond defense+offense slots can be nice, dunno where the sweet spot would be on that.
I'm all for keeping it as is and simply improving it, I don't think we are at a bad place at all right now, just a lacking one. If I did this from scratch, I'd simply revamp the GP tables all together to solve the problem once and for all, doesn't seem possible anymore as there are too many things attached to the initial abrupt GP calculation.
To reiterate for the last time, mods, g11-12-13,zetas and maybe omegas. No gp. Weighting doesn't need any use of gp at all. Current GP matching seem to have a very low threshold as pertinent GPs are almost a perfect match, that's not necessary at all as long as there's enough weight on other parameters and GP can only be used as a safety measure to avoid to far jumps. I bet if the above parameters nicely fitted between matches, people wouldn't care anymore if their opponents have +-250k gp.
And yeah, this was what the majority of what the talks consisted of when people were asking MM based on parameters-. The debate mainly relied on whether toon specifics should be involved, whether mods should be involved at all etc.