GA Algorithm - Worse Than Before??
So I was excited that the GA matchup algorithm was going to be improved. I was also excited for GAC to start (correctly this time). The I go into my first round matchup... The person I am against...
Forum Discussion
"YaeVizsla;c-1897583" wrote:"Nikoms565;c-1897522" wrote:
Seriously? Discord apps can check mods - how hard would it be to code them within certain ranges of each other?
Checking mods and matchmaking based on them are two entirely different things.
And if you give significant weight to the number of high speed mods as a determiner of how many effective units you can field, you've created an exploitable loophole in the system where units who don't care about speed mods- Baze, Droideka, Mission, Big Z, some Chewie builds, Resistance Trooper, Sith Trooper, Nest- become disproportionately beneficial in a way that the matchmaking algorithm would fail to account for.
This is not a failure of the matchmaking algorithm. You're just looking for an excuse to play the victim.
Apparently so are the several hundred people flooding the forums and Reddit with similar matchup concerns.
In the first (failed) launch of GAC, there was a guy in our bracket who had a 6* Traya, no Malak and no DR. Many of the rest of us had 2 (2 had all 3) maxed. And the differences in mods, g12, zetas, etc. were all way off compared to previous iterations of GA. I'm not "playing the victim". I legitimately think something is wrong with the matchup calculations.
The "new" algorithm has created far less even matchups within a given bracket than the previous one, as evidenced by the numerous screen shots (both in-game and from Discord) showing a much bigger discrepancy in matchups.
