This is an exercise, which can potentially create balancing iterations we can play around with on UAT. None of this is scheduled to happen; this is more how you work internally. You discuss, dig into data and numbers, throw around ideas, then determine if some are valid enough to go to UAT. Scream While Dying (TM) Purpose: While you are dying, you get to scream, shout and bash your keyboard, instead of screaming after you died in a way not clear to you, and then scream after you died. It is as simple as it sounds. I've gone through this exercise in many games while consulting and games I run myself. The psychological effect of the two scenarios is undeniable. While you still usually end up dying in before and after the changes, you inherently feel like you had a fighting chance. This means drastically increasing survivability, which can be done through quite a few ways. We want to get people to propose balance changes so they get annoyed less by dying. Opportunities: Scream while dying Lessens the impact of the most time-sensitive systems Latency has less effect Factions and classes have more room to differentiate themselves with the added stat range The long time-to-battlefield is not as frustrating (other projects, such as vehicle stats and spawning, fewer tanks, more epic) Mods can be much more effective and give choice of playstyle, You will in most cases not change the outcome of all battles but the following opportunity for differentiation in faction and classes might. Risks: You end up bored to death waiting to die, there is a lot of factors that might create temporary OPs but that's always Mods and LP costs need more work, Ruin the game. But all changes can do that. So we test out iterations on UAT. Exercise framework This is not to debate if Scream While Dying (TM) should be done, it is to propose how to do it. After a solid suggestion sheet of changes is created, and rounds of testing, we decide if we deploy an iteration to UAT at all. This is also not a screaming contest between ideas; it is brainstorming, meaning all suggestions are valid, no matter how bad. You get no engineering time; you can only mess with the stats (unless I deem it worthy enough to override other things in dev). Suggestions can be long, and you can copy the sheet for your group to work, marking changes in red. Here is the most recent stats overview. This is the external master, and we'll update it: http://bit.ly/2j1Zvpl Enjoy the exercise and speculation, stay very very far away from salt and personal attacks. I'll temp ban you without hesitation for ruining the exercise. The suggested format in replies is; "This has X and Y while that has Z and Q. If we change X to the values Ö, Ö1, and Ö2 on the variations, it will become a valid choice." Again, brainstorm, suggestions, enjoy the exercise and opportunity, don't be Angron.