Kaneki needs to be killswitched (Serious Exploit)
Hi guys, I hope all of are doing well
I was playing survivor yesterday with my friends, and one of the matches were against a kaneki, and ok, nobody wants to play with the new vecna and I don't mind kaneki so much, but this match was really awkward because, every time he was vaulting right after me on pallets, I was insta dying, every single time, I wasn't trying to vault back, I was just going around the loop normaly.
I thought I was just bad at the game, but afterwards I played some kaneki matches to test this, and I was getting the same hits that my kaneki was hitting me on that match, and I was confused, I have a clip of me playing kaneki to give you guys a example.
As you can see, Renato didn't tried to jump back over me, he was just running from me, and suddenly he just dies, like, he instantly dies without any explanation, and this is not something rare, its very common.
I'm afraid once people realize this exploit, people are going to abuse this like crazy and the hate for kaneki is just going to increase, he is already a not very cool killer to go against to some people, and people will think this is a intentional mechanic of his and hate him way more.
I hope BHVR don't waste time on this and killswitch ASAP.
Comments
-
Dude. Your video is set to private. No one can see what you're talking about.
5 -
Now it should work
2 -
Hopefully this gets fixed, coz it happens when against Wesker too.
11 -
Licensed killers don't get killswitched, so just wait for the fix I guess.
4 -
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.
-40 -
Last patch you could revault inside Kaneki and Wesker, so they probably tried fixing the collision and ######### it up.
16 -
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.
3 -
Having played both killers after the patch it feels pretty absurd sometimes ngl
3 -
Maybe because something simular i have had when springtrap was released when I played kaneki so its just maybe bug or devs trying to fix something and coding kinda took it different way.
-1 -
They've said before that it happens both on Kaneki and Wesker, and for whatever reason it sounded like they had no idea how to stop it but i could be wrong, regardless the fact something so unintuitive has remained this long is very fitting for BHVR's skills
4 -
This is the Anti Vault back protection Kaneki and Wesker have this cause Survivors can slide into there hitbox while they are scampering to immediately vault back before the Killer can hit them so they added this damage state to prevent survivors from doing that.
However this never really happens on Weskers because his scamper is pretty slow and sure can just make distance while he's doing that.
Ghouls however is a major problem since he can keep you in place and Scamper 2x faster then Wesker not only that but also apply a 50% hinder debuff on the survivor and if the ping is bad your just always going to get hit by this move. This needs to be fixed.
11 -
This is literally the only killer they made changes for, bug fixes mind you, and they missed this?
Cringe, BHVR. That's cringe.
Post edited by ArkInk on13 -
That "bug" has been in the game since 9.3
Allegedly its a ping issue and not a "hitbox/mechanic" issue.
Even though this could've been avoided but not injuring survivors when near vaulting in the first place.
(Seriously, he does not need that on top of his free injury ans blight chase power)
7 -
I can confirm. It did happen to me too in my last match.
That doesn't look right…13 -
Okay, this is serious!
Exploits like this should NEVER be able to exist in a PVP multiplayer game.17 -
11 -
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 ❤️
0 -
Yeah, I have noticed it yesterday, it downs you even when you are not anywhere near the pallet.
I just can't be bothered to play against him. Give me The First to my lobby…
3 -
Yeah, I would get if he got Legion type of vault, but for some reason he has Wesker vault on steroids…
2 -
I wouldnt be this pissed if survivors got new ######### like this too, 2023 was peak even with blight n nurse 24/7.
4 -
I wonder how long it will take before they killswitch this. Have you tried other maps or only this map.
2 -
No guys, wait—there’s no bug, and no killer needs to be kill-switched or fixed. As you can see from Vecna’s perk, I recorded this video just a little while ago, and this survivor was not hit twice, exactly like in the video shown by the author of the post.
Here the video:
-14 -
Why should they killswitch something now thats a thing since his introduction?
-12 -
Because if players find out about this bug then they take Advantage of it. Its not to late to fix something that can be a problem
6 -
This content has been removed.
-
Somewhere someone has already mentioned that this isnt a bug. Thats why they wont do anything about til forever. Or at least as long as they can get money out of the sells.
-3 -
- I confirm, pallet vaulting is COMPLETELY bugged... and obviously killer players know it very well. Let's wait until Tuesday.
10 -
Why do you call it a bug?? It’s one of his features. It was bugged before, but when it was released it worked like this. Then it got bugged, and now it’s been fixed, but many times when you vault it doesn’t hurt you. It's a bug when it doesn't happen
-15 -
He didnt do this for 8 months since release.
6 -
This content has been removed.
-
latency??? He's far from the killer POV (the one that matters when talking about latency)
4 -
If it is a lag issue then its a bit wierd how this didnt happen until recently. (But then again dbd coding does all wierd things)
2 -
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.
-3 -
Obviously, because before it was bugged. Now that they’ve fixed it, this power is working properly. And it’s not always like in the video: when it was released, the hit worked; then after the nerf where it lost stacks when breaking pallets, it got bugged and stayed that way until the fix in the latest patch.
-9 -
It’s the tentacle, Maybe? But the devs have to explain btw
-2 -
And now explain to me why, in my video, the survivor wasn’t hit with two attempts, in the same way it supposedly happened in the OP’s video
-3 -
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.
3 -
This content has been removed.
-
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
4 -
This content has been removed.
-
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.
1 -
So they indeed tried to fix this scumbag exploit against Wesker and Kaneki.
MAYBE this is what broke his collision even further to allow easy Bug Techs.
One thing I can say is that I don't play Wesker anymore because of all his bugs, but I went on a forced 2 months break of gaming in general and just now I've decided to play ONE match as Wesker and in this ONE match I had the same issues as before: survs escaping his grasp like if I passed on a hole or terrain elevation IN PLAIN TERRAIN and a surv in the middle of the gap for a pallet to be dropped and I pass right through them.0 -
Bro, obviously everyone only posts the clips that annoy them, and I’m the only one posting a clip that shows the opposite. But trust me, that’s how it is. I’ve also, while playing against the Ghoul, managed to pass through the body with no collision and vault the pallet again.
So basically, there is no bug. It’s one of his features, an action tied to his power, and nobody is abusing it. It’s something that’s been fixed, but in any case it’s still a bit buggy because it doesn’t always injure, so I’d say case closed. Some people experience it, some don’t.
-3 -
I think it’s just a lag/ping issue — from the survivor’s point of view he looked farther away, but on the server side he actually wasn’t.
-3 -
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.1 -
This content has been removed.
-
Official source like current patch notes with bugfix claim this issue is fixed.
1 -
Apparently he was fixed does anyone notice any difference?
0 -
Idk I have this issue after springtrap release and than I havent got it when playing ghoul, sometimes the fixes wont make big difference.
0 -
Nop, he is Injuring anyways
0
