Visit the Kill Switch Master List for more information on this and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
Get all the details on our forums: https://forums.bhvr.com/dead-by-daylight/discussion/436478/sign-up-now-to-receive-a-recap-of-your-2024-dead-by-daylight-stats/p1?new=1
When did they change Sole Survivor?
From what I used to remember was, even if you had tokens the perk would only light up when it was actually blocking auras. This gave a ton of useful information to guess what perks or add-ons someone is using, the same way distortion does when its triggered. But now the perk stays lit up the entire time once you get one token and gives no indication on whether its doing anything or not. Why change in the first place or revert it back to how used to work? Cause rn literally NO ONE uses this perk, which is a shame since its better than distortion in all of ways.
Comments
-
It was changed time ago no I don't know why they thought it was a good idea to change it when the version that only lit up when you were specifically meant to be seen instead of permanently was amazing
0 -
Neither I know why it says "quality of life change"
0 -
Saw this thing too, but I think it is unintended. Any mod or dev that can confirm whether this is how it's supposed to work or not? @Almo @Peanits @MandyTalk
0 -
Yeah they need to either change it back to how it used to be, lighting up only when it blocks auras. Or make it work more like distortion. It gives no info whatsoever on whether its helping you or not which is why no one uses it. Distortion does when it triggers and off the record you know you're safe as long as the perk is active.
0 -
Hey devs you got any plans in the pipe to buff or rework sole survivor? I already run distortion and off the record together, but I'd prefer to use sole survivor. But it given it gives no feedback on whether its doing anything or not is why I won't run it and no one ever does.
0 -
I think I heard from a YouTuber forgot which one now it was unintended change but no one knows why it hasn’t been fixed yet
0
