Please check if your issue has already been reported first!

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.
The second iteration of 2v8 is now LIVE - find out more information here: https://forums.bhvr.com/dead-by-daylight/kb/articles/480-2v8-developer-update

PC - survivor stuck on shoulder

Steelexxe
Steelexxe Member Posts: 2
edited June 14 in Bug Reporting

1: open game
2: select twisted masquerade killer
3: Find a match as ghostface
4:Downed and hooked first survivor
5:Mark Sable with exposed using ability
6:Down sable
7:pick sable up
8:as she's being picked up, spam remote hook before im blinded by the flashlight user
9:Get blinded, but dont drop or successfully remote hook sable
10:Try to hook, completely unable to. Assume sable is unable to wiggle

Perks (in order): Bitter murmur T3, Spies from the shadows T3, Distressing T3, Beast of prey T1
Offering: Screech Cobbler
No add-ons

Map: Lery's memorial institute

Managed to communicate the issue with the other survivors and we tested palette stun save and flashlight save, no successful drop. Attempted hitting and downing another survivor to fix it, no luck. Was able to pick up a second survivor while still holding Sable but did not try to hook. All functions were available to me as if I wasn't holding a survivor, including receiving invites and the event totem function.
Allowed to finish gens and opened exit gate for them. Sable had merged to my body as I could see her feet attatched to and moving with my attacking arm. When endgame timer ran out, she screamed like she had died, but she was still on my shoulder and counted as 'alive' and I was forced to disconnect to end the match.

I believe the issue was caused by spamming remote hook when i got blinded, stopping the forced drop but not registering it as a remote hook, either

1
1 votes

Duplicate · Last Updated

Thank you for taking the time to report this issue. This problem has already been reported and it's currently under review.

This discussion has been closed.