Kaneki needs to be killswitched (Serious Exploit)

Its not an exploit its a feature him being that far from the pallet when getting damaged is because latency. If Kaneki vaults over a pallet or a window that survivor is close enough so their models collide will cause lose of one health state.

This isn't a new thing, it's been in the game for ages (probably since the chapter launched).

It certainly looks and feels like an exploit but you'd expect it to be fixed by now if it was. Given how terribly designed this killer is, it's hard to say if this is intentional or not.

There is a betahub thing open for this bug no videos have been uploaded yet so may help help to pop the videos on there ❤️
https://app.betahub.io/projects/pr-5642738318/issues/969?search_element_id=969&search_input=ghoul

Yeah, I would get if he got Legion type of vault, but for some reason he has Wesker vault on steroids…

I wonder how long it will take before they killswitch this. Have you tried other maps or only this map.

Why should they killswitch something now thats a thing since his introduction?

latency??? He's far from the killer POV (the one that matters when talking about latency)

I have seen it happen before this up tick of cases happened. It was not common but it could happen when there was bad latency. Still did not know it has become this common after the patch as I have not played Kaneki or played against him yet in this patch. My original post is like fifth post in this topic so was just stating where I have seen it happen but still I would not myself classify this as an exploit as the original poster states in the tittle but it indeed seems to be a bug. The reason why I would not call it an exploit is the fact that its part of the normal gameplay loop that Ghoul goes through and is done in almost every match he is played in but its clearly a bug of the amount of people stating it happening and seeing more videos about it.

Good point but in the match where I recorded this, my ping was ~30 ms and the killer’s was ~60 ms (I grabbed a lobby ping screenshot too).

My connection is stable fiber; I sit around 20–40 ms in general.

Yes, netcode can make things look weird sometimes… but 30 vs 60 ms does not explain taking a health state at clear distance with no visible contact, especially when I’m not vaulting back and I’m not hugging the killer’s model.

Saying “it doesn’t happen in my matches” doesn’t prove anything except that you personally didn’t reproduce it.

Bugs like this can be conditional (timing, animations, server state, map geometry, interaction order, etc.). Multiple people in this thread have already reported the same thing, and there are multiple clips now.

Also: I’m not interested in turning this thread into a “teach me the exact setup so I can test it” situation. That’s how issues like this turn into publicly abused tech.

If this becomes widely known how to trigger it reliably, you’ll see exactly what happens in Dead by Daylight every time something is abusable: people flock to it, matches get miserable, and then suddenly Behaviour Interactive is forced to act.

I agree it’s sad, but that’s been the pattern.

my comment was miss-interpreted by many. I meant, it could not be latency if it looks weird even on the killer POV, the hitbox is just too big

Gotcha, thanks for clarifying 🙌 Yes, I initially read it like you were using latency as the explanation. We’re on the same page then: if it looks wrong even from the killer POV, “latency” isn’t a real answer here.

Being mistaken is human; repeatedly changing the explanation to whatever is convenient is something else.
Going from “case closed” to “still buggy” to “lag” reads like damage control, not a good-faith argument.

Provide an official source for “intended,” or stop dismissing evidence you can’t refute.