Gen regression perks should not count towards the 8 gen regression event limit.
If you’re a killer who intends to 3 gen from the start, this change prevents you from forcing a 3 gen because kicking a gen 8 times during a match doesn’t happen organically most of the time. Kicking a gen 8 times most likely means you’re trying to force a 3 gen.
The problem is that if you’re a killer that uses perks such as Surge, Pain Resonance, Eruption or Pop Goes the Weasel then reaching 8 regression events isn’t hard because if the gens regress whenever you proc such perks, it counts as a regression event. So even if you never intend to 3 gen, you’re getting punished for using regression perks.
Now imagine you have Pop Goes the Weasel, Surge, Eruption and Pain Resonance. You kick a gen that has 50% progress to proc Eruption. You down a survivor which procs Surge. You hook the survivor on a scourge hook to proc both Pain Res and Eruption. That’s already 4 regression events and 3 are from the perks themselves. Then if you want to proc Pop that’s a 5th regression event. You are now left with 3 more regression events simply because your perks count towards the limit. This basically means that you can use your perks at most 2 times per gen.
This needs fixing. Regression perks are constantly being nerfed. Please make the perks not count towards the regression event limit.
Comments
-
BHVR doesn't want you to use too much gen regression perks, so you have to try other perks.
Don't rely on regression perks.
1 -
Then BHVR should make more useful perks. Then BHVR should nerf gen rushing.
1 -
The regression caused by this stacked slowdown would realistically result in the gen losing at least 50% progress (flat 5+8+10+20+20% of whatever is left). It is more than fair that this eats up a lot of regression events as that is a hefty amount of regression.
0 -
The issue is that if the gen that gets regressed doesn’t have much progression in the first place. Let’s say the most repaired gen has 10% progress. It gets hit by surge, then I kick for Eruption, then survivors repair it to 10% while I was chasing someone, then I down the survivor I was chasing so surge procs again, then I pain res that gen because it’s the gen with the most progress since survivors insist on repairing that one particular gen. So many regression events on a gen with barely any progress and when the gen will actually have tons of progress, I won’t be able to do much to the gen because it will be blocked quickly.
And now let’s say there’s a gen with 5% progress that I regress with Surge. Then the survivor that works on that particular gen repairs it to 5% but I down another survivor so surge procs again on this gen. That’s 2 regression events on a gen with barely any progress.
The big issue is that regression events get wasted on gens with little to no progress and I can’t even control it.Post edited by iamvladd2000 on1
