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 these and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
We encourage you to be as honest as possible in letting us know how you feel about the game. The information and answers provided are anonymous, not shared with any third-party, and will not be used for purposes other than survey analysis.
Access the survey HERE!
Killer stuck trying to hook when sabotaging
Platform: PC - Steam
Description: When I sabatage a hook with the "Sabotage" perk, and de killer is just about to hook a carried survivor, he gets frozen until I fully sabotage it.
Steps:
- Survivor with sabotage perk
- Start sabotaging JUST before the killer hooks. Killer presses "hook" (spacebar I think)
- Killer gets freezed with the survivor on his shoulder until I finish sabotaging.
I will try to get a screenshot of the exact moment. [Edited to add screenshot]
]
Comments
-
I've experienced this myself and I really hope this is a bug and not a feature. Survivors shouldn't get any priority on hooking progress.
1 -
I have reported this bug before. Apparently he was ignored.
1 -
Screenshot of the bug.
The killer is stuck in that position until I finish the sabo.
I don't do it to bug them, I try so that they hit me to get mettle of man and I give the survivor some seconds to wiggle and escape with my breakout.
0 -
Doesn't seem priority.
I mean, if survivor is sabotaging the hook, I think it's ok for the killer not to be able to hook. I like the mechanic.
BUT what's happening here is that the killer IS STUCK. When he presses spacebar he FROZES util I finish sabotaging.
0 -
I think it's OK for the killer not being able to hook while sabotaging.
BUT what's happening here is that the killer gets FROZEN in front of the hook if he tries to hook while sabo. It only happens when he presses the button to hook when the survivor just started sabotaging. Like if both did at the same time but survivor input got first to the server.
0 -
Yes I know you can't hook while they sabo. The priority I mean is like the Hatch closing, where the server prioritize the Killer input.
0 -
Ah ok.
But if the server recieves both imputs, it will always recieve one before the other (usually killer's imput because he's usullay the host or something like that, I don't really know how it works).
Sof if it recieves on input first, the server doesen't need to prioritize, right? I really don't understand how that works.
0 -
I'm not a game developer but a web developer, the concept of any game using dedicated servers works like this:
"inputs" or any data works in a bidirectional way, the client can send any information to the server and the server can also send any information to their clients.
For example: If the "Survivor 1" drops a pallet on their game screen, it sends that information to the Server, then the Server will send this information to the other clients(Survivors and the Killer), and in their screen, they will see the pallet dropping.
But this is a very basic concept, there's a lot more going on behind the scenes, but this is how it sends and receives data. I think the way they can prioritize the Killer input is by everytime a Survivor send their input(if that input has priorities), the Server will try to wait some milliseconds to see if a Killer will send their input, if it does, it ignores the Survivor input and accepts the Killer one.
"Survivors shouldn't get any priority on hooking progress." So resuming, even if a Survivor sends their input to start the sabotage interaction, if the Killer pressed the button just a little bit late(needs to be lower than 1 second to make it fair), the Killer input should override that Survivor input and allow the hooking interaction to progress.
1 -
Great explanation.
Now I understand what you mean, thank you.
Let's see if the devs can solve this bug.
0 -
bumping since this just happened to me in 5.1.0
0
