http://dbd.game/killswitch
The regression events should be changed to a total gen regression cap per gen
The regression event counting method doesn't impact regression perks equally. Perks with low regression amounts are nerfed, e.g. Surge. A 2.5% regression shouldn't be treated equally as a 25% regression because it limits design space. There could be a point in the future where the devs make a 2.5% regression perk, and it will be terrible due to the regression event cap.
Perks that require kicking gens, e.g. Eruption, No Where to Hide, and Trial of Torment are nerfed. Perks that cause passive regression, e.g. Hex Ruin and Oppression, are largely unaffected when they should be accounted for since they still regress gens.
The total gen regression cap makes far more sense since it treats all regression perks equally and accurately factors for how much a perk impacted gen regression. It would account for all regression, including any form of passive regression, except missed skill checks. By cap, I mean relative to gen progression, e.g. a 100% cap means a gen can only regress 100% in total at most.
As for the cap %, I haven't decided but 150% is probably good.
Comments
-
that was my idea that you have 150% regression cap. the dev prefer the 8 regression instance system which is fine. it does same thing. they just need adjust balance on perks if one perk is not outputting enough regression.
0 -
Yes. This is a HUGE reason to run Ruin since I don’t think it’s considered a regression event. The gen simply starts regressing when survivors stop touching it. So with ruin you will still have infinite regression as long as you can defend the totem.
Ruin is probably going to be meta again.
0