4 years ago
Grand arena matchmaking
I’ve got to say the matchmaking in this game for TW and GA are TRASH, especially since they nerfed every non GL counter. Before the nerf if someone had more GL’s than you you still had a chance to win...
"Rath_Tarr;c-2300778" wrote:"nottenst;c-2300743" wrote:"Rath_Tarr;c-2300716" wrote:"nottenst;c-2300678" wrote:
The whole point of matchmaking should be to make a competitive match between the two sides. If you can tell just by running the numbers through a discord bot that one side will blow the other side away, then the matchmaking is deficient. It is as simple as that.
While it might be good for a quick laugh to be able to blow the other side away in GAC or TW it does not make a for a satisfying battle on either side. The best experiences in both of these are when the match is close. If they incorporated the number of GLs into the matchmaking algorithm it would make the matches closer.
If you are relying on discord stat bots to determine win / loss then you have already failed. I don't even bother with them because they don't tell me what I need to know and I have finished Kyber in every single GAC.
The point of roster management is to effectively use your resources so that you can have a fun and productive experience across all game modes, including GAC. You don't have to min-max your roster to be effective but you do have to pay attention to it.
Making special allowances for GLs is the start of a slippery slope. If people are matched based on number of GLs then what about other "unbeatable" squads? Shouldn't lower GP players be matched on whether they have GAS? DR+Malak? Padme? JKR? Geos? Phoenix? Where does it end and who decides what is fair?
The discord bots apply more to TW than GAC to see how many GLs each guild does have. A quick look at the roster in GAC is good enough. The point is that a simple tool is out there that could make better matches.
The nerfing of the GL counters already took things beyond any slippery slope. It is extremely easy check that even CG developers could use to make better matches.
My current opponent and I have the same number of GLs, however I have JMK+CAT while he does not and I also have Executor while he does not.
I can block him in squad, fleet or both. Is that not unfair? Should the matchmaker not also take into account the types of GL on each side? Whether both players have Executor or not?
A blocker is a blocker, regardless of whether it is a GL or not."nottenst;c-2300743" wrote:
I didn't notice, but was the GP of the nerfed characters correspondingly reduced? If not, they should at least have done that.
Was the GP of GLs and their prerequisites reduced when they were beatable by far more easily acquired characters which cost a fraction of their MM GP and resource investment?"nottenst;c-2300743" wrote:
The point about the GLs is that they want it so that only GLs should be able to defeat GLs. That is their current design, so they should take that into account in the matchmaking. It should be an extremely simple concept to grasp without worrying about other ramifications.
No. The point is that a blocker is a.blocker, regardless of whether it is a GL or not. Ignoring that fact merely reveals the selfishness of the demand to treat GLs differently. But accepting it and attempting to factor in all potential blockers in matchmaking is an exercise in futility."nottenst;c-2300743" wrote:
For lower GP players there are a lot more divisions, so it could be that balancing those previously "unbeatable" squads might not as big a deal.
Which squads/fleets should be considered blockers and in which divisions is far from a trivial question. Moreover any such assessment is highly subjective and no matter the outcome, will almost certainly lead to even more complaints. Not to mention the additional algorithmic complexity required and the likelihood of introducing other problems in the process.
Or players could simply take responsibility for managing their own rosters.
Discuss and share your feedback on Star Wars: Galaxy of Heroes with fellow players.
78,398 PostsLatest Activity: 2 years ago