Alliance war rankings

Joel92598Joel92598 Member Posts: 82
Can we get some input as to why it is okay that the 3rd place alliance is taking rewards from other alliances that deserve it? NATH should be a platinum alliance at best, yet they will finish the season at the #3 spot because of kabam's matchmaking system. They had such an easy schedule compared to the rest of the masters bracket and they would lose to all 20 other teams in masters. They only faced 2 teams in masters and lost both by heavy margins. Meanwhile the alliances at the top of masters rematch each other twice a season causing losses for them while NATH just coasts to the 3rd spot with over 150 deaths in the season. For reference, the alliances in first and second have about 20 deaths total for the season. Why can't matchmaking be updated? It should be based on standings and standings alone and don't allow rematches. This current algorithm needs to be updated because this same situation has happened before. Not sure why Kabam has ignored it for this long

Comments

  • Agent_X_zzzAgent_X_zzz Member Posts: 4,498 ★★★★★
    It’s pretty sad, this happens ever so often. With NVLN, utopia. gre/ Asian ally, and then 4loki one season. Matchmaking and map sucks
  • BeeweeBeewee Member Posts: 556 ★★★★
    NATH >>> GT40 & JA
  • VernVern Member Posts: 55
    I agree


  • OOzOOz Member Posts: 1
    Nath OP, 150 deaths deserves it over the several alliances that had 100-125 less
  • Navneet9Navneet9 Member Posts: 16
    Beewee said:

    NATH >>> GT40 & JA

    This is just the beginning.
  • pseudosanepseudosane Member, Guardian Posts: 3,978 Guardian
    luck is often a part of this game. NATH got that luck in spades this season haha. Good on them.
  • Joel92598Joel92598 Member Posts: 82
    @Kabam Miike @Kabam Zibiit can we get a response? The top aw community would like to know if Kabam is looking into this situation
  • SummonerNRSummonerNR Member, Guardian Posts: 12,733 Guardian
    edited April 2023
    Only was to successfully do Seasons, is to have Set Ranked Divisions each season (aka English Soccer Divisions), groups of 13 alliances each (by WR), where every alliance faces every other in that Ranked Division.

    Descending Divisions, 13 alliances each, and have to “Enroll” for each season (to avoid including dead or dormant alliances who happen to still have high WR).

    Division 1 — Top 13 alliances (top 13 by WR), Multiplier 10x.
    D2 — WR alliances #14-26, Multiplier 9x.
    D3 — WR alliances #27-39, Mult 8x.

    Descending down and down, etc, Multiplier starting to be more fine-grained, descending in lesser and lesser increments.

    During seasons, at much further down levels, where some alliance might start to become dormant mid-season, they could promote up a leading alliance from the next lower division to finish the season. And that would propagate all the way down, leading Ally in each next division gets bumped up mid-season. Etc. (but that probably wouldn’t ever happen up at the very top of the charts)
  • BeeweeBeewee Member Posts: 556 ★★★★
    I mean main issue is that tier 1 is just too large of a bracket when competing for top 20. Reduce its size by half and you basically remove shellers and lucky matchmaking. Not much rocket science to it
  • Saske97Saske97 Member Posts: 81
    edited April 2023
    Bumping this hoping for an answer from Kabam :#

    As others have mentioned above, I also think that removing repeated matches would be a good start to improve top war ranking. I don't see the point in getting the same opponent twice because in most cases it would be the same outcome twice. We fight at least 3 master opponents twice every season, sometimes more. Where is the fun in that? And how does that make sense?

    Please, remove repeat matches and adjust matchmaking parameters so only the alliances that actually deserve masters stay there and match themselves.

    I really hope it's at least something that it's being worked on behind the scenes for the future AW updates with 2 days attack and the other changes.

    Just don't ignore this.
Sign In or Register to comment.