JavaScript is required to use Bungie.net

Destiny 2

Discuss all things Destiny 2.
Edited by ILyncher: 1/2/2022 5:00:58 PM
0

What’s the solution to Trials matchmaking???

As we know the content update to trials will be the witch Queen. That’s some time away, the loot/incentives to play are diminishing every week. This directly affects the player population. Less players every weekend, when a bad map is selected even less will play. This leaves a very concentrated pool left playing and even lower playing all weekend in flawless pool. Like this weekend gone for example 3-4 games in flawless pool was top 500 players. Also worth mentioning non flawless pool is quite bad now too. 1/6 win resetting or players waiting to play until the final day as the experience is too hard until then. It all negatively affects the playerbase. It’s a never ending cycle with this current system and it’s not working. We need a system that we can play anytime we want and not suffer from the lack of replayability, also feel a rewarding experience to play. I personally feel in an ideal world where the playerbase is thriving 500k+ every weekend flawless pool/solo playlist has a place to protect the casual playerbase. However, with the concentrated aspect I’ve already touched on it makes no sense to split the playerbase further and then again into sub platform pools too. It’s crazy to think we’re more concerned about play testing gamemodes instead of improving the player experience and retention of the playlist and matchmaking is the main solution. This will dictate whether the players come out with a positive/ negative experience and it needs to be addressed as it will impact players going in next week or potentially not at all for the rest of season. [b][u]Solution:[/u][/b] Here’s a Solution that could be used, it’s only an idea from my observations of playing. I know the main concern of the casual playerbase is that top tier teams farming them and making it impossible for them to progress for the rewards, So they will need to be protected too. The experience needs to be balanced on both sides for casuals & hardcore players [b][u]Solution 1 :[/u][/b] Have tiered loot system based on the card picked up at saint in the tower. The card will dictate the mm/reward pool. [u]Passage Of Fairway[/u] •Bronze tier rewards- up to 3 losses on a passage. Chance of an adept weapon to drop at the chest. [u]Passage Of Mercy[/u] •Silver tier rewards- current loot system. [u]Passage Of Legend[/u] •Gold tier rewards- random adept weapons dropped at chest. National rankings. To further expand on legend card- only flawless teams can acquire the passage. Increased loot rep & challenges, tied to allow the more competitive players to branch out of the main pool, leaving the top tier 3 stacks for high risk high reward setting. Legend passage has more strict performance based mm in it and only for the flawless players. Passage of fairway & mercy all in the same pool with light performance mm based on previous game performance like in week 1 of this season. [u]OR[/u] [b][u]Solution 2 :[/u][/b] One pool with light performance based matchmaking to improve the player experience from both ends. Simply opening up the matchmaking will have more people playing. However, counter will be the inexperienced players will find it harder with the current passage system for loot and getting the 7 wins for flawless. [b][u]Conclusion:[/u][/b] This is just ideas and something I feel is not talked about at all. We need a middle ground to improve the player population and it’s not going to happen without some players insight. The current system isn’t working. We all want to have the option to play with friends casually or in a more competitive setting. I think all of this can be done with the right concept. What would your solutions be? This concept needs some work but I think it’s worth a try over the current system. Thanks for reading.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon