Nothing you do is going to matter if you don’t address the underlying issue. No game mode changes, no proximity buff, not even moving snipers and shotties to primary and giving them elemental damage with high-caliber ricochet explosive rounds that create an area of effect with masterwork range will help. Heck, you could give us all 900 rpm Black Spindles that fire Gally rounds, and the next day we’d be right back here complaining because the underlying problem is your network architecture, netcode, and almost complete lack of exploit detection. I mean, yeah, you enhanced the reporting mechanic, but we both know you can’t rely on people knowing the difference between a cheating and bad netcode. Well, we *could* know quite a bit more if we had been given PRIVATE MATCHES at the turn of the new year! D1 helped us overlook the natural imbalance these issues created, because everything else was fun. There’s some fun in D2, but it dies off quickly, because in the end we’re shooting at the same stuff and somehow the raid becomes more of a grind than a challenge, and, much like real schools, you don’t reward teachers to teach. Well, you might bend over for YouTubers and OpEds, but they aren’t in the trenches in numbers, are they? There was a precursor to the fall of subscriptions/followers, which led to lower users, and that’s where your real problem is. And now, everyone who’s left has been forced to segregate into a skills-based caste system, a trend that is reinforced by paid-carries and elitist LFG reqs. Fundamentally, all your challenges are related and all your solutions are sound, but only in isolation. The problem is they create disjoins among the application domains, which translate to immediate disjoins in the user-base. In that case, given finite resources, you can only do one of two things: create two high-level domains, PvE and PvP, to maintain the integrity of the edges in each; or overhaul the network structure, using PvP to relieve the strain on PvE edges. Otherwise, your current roadmap will only encourage further isolation, attrition and segregation among users. Finally, I realize some of your challenges may be due to an inherent downside of Agile. One thing I’ve noticed no one admit to about Agile is that it assumes you start with a viable release that meets the needs of your market, a minimum viable product, or the specs for one from stakeholders. You don’t have that. That is, if you’re going to revert from version N to version 0, then you need to confirm V0 specs with your stakeholders. You didn’t. You just descoped arbitrarily. So, if you don’t start with an MVP, while each sprint looks great on paper, you’re actually working against the grain, continuously sacrificing either technical debt, bug fixing or product enhancements, where the process of accomplishment actually works against you because you got the start of the process wrong. Agile doesn’t really allow a natural course correction. Planning A includes a retrospective that you never have time to implement, and if you use Jira, you’re in a workflow that forces you to show progress, so you Won’t Do or On Hold and toss it all in a Backlog that won’t become relevant as your product or codebase moves further and further from your stakeholders’ use cases.