When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
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
Killer Perks: "Game Afoot" Obsession Change Does Not Trigger "Nemesis"
Description
When causing the Obsession to change with the perk "Game Afoot", the Obsession change does NOT trigger the perk "Nemesis".
Notes
"Furtive Chase" is not effected and is working as intended.
Repro Steps
- Launch Dead By Daylight
- Create a private match with at least 2 survivors
- Equip perks "Game Afoot" and "Nemesis"
- Load into the private match
- Locate the survivor that is NOT the Obsession
- Chase the located survivor to ensure "Game Afoot" triggers properly
- Hit the survivor with a basic attack (Avoid causing Obsession change via stuns/blinds)
- Ensure the survivor becomes the new Obsession
- Observe the perk icon for "Nemesis"
Repro Rate
5/5
Expected Results
The Obsession is changed on basic attack, the "Nemesis" icon shows the timer animation, the aura of the survivor is revealed to the killer, and the survivor is afflicted with the Oblivious status effect.
Actual Results
The Obsession is changed on basic attack, no change in the "Nemesis" icon, no aura is revealed, and no status effect is afflicted.
Build Info
- OS: Windows 10
- Platform: Steam
- Patch: 6.7.2
Attachments
Videos
"Game Afoot" x "Nemesis": https://youtu.be/7gND6qwmKj8
"Furtive Chase" x "Nemesis": https://youtu.be/8eugJczo2PU
Log File
Added using a different match. Hopefully the data is still good on another repro.
Comments
-
Issue is still occurring in live version 7.0.0 .
0 -
Issue is still occurring in live version 7.0.1 .
0 -
Issue is NO LONGER occurring in live version 7.0.2 .
0