Can we make failed grab fix as guaranteed hit?
When you fail grab on survivor, you will get auto-attack.
Problem is that it is not guaranteed hit and you can miss that. It happened to me several times already.
My newest fail resulted in getting normal hit instead of insta-down with Oni. Also really nice.
Either remove it, or just make that guaranteed hit.
I don't understand, why it is not guaranteed already. I obviously was in range for it...
Comments
-
Yeah I don't even know how it is not a thing, like, the server makes you hit, but the server doesn't apply the hit on the concerned survivor anyway, that's a weird design.
1 -
I think that instead of a guaranteed hit we should get a guaranteed grab, its so awkward to start a grab animation then stand still for 0.3 secs or so and then hit the air / survivor...
1 -
Yeah, problem is that this would kinda situations with pallets. High ping killers would grab you after 1 minute...
0 -
Yeah these are annoying. Had a blight who looked like he grabbed me off a gen but then it turned into a hit.
0 -
The grab effect is client side, your pc detects whether it should execute the grab animation, the server validates it and changes it to an m1 if it fails validation. If you made it a guaranteed hit, then you would essentially be letting the client decide when to hit a survivor.
I imagine it would be open to all kinds of exploiting. Server validation is a tricky beast, and even if this is the devs intention, I would expect it to probably take a while longer than the standard grab M1 they have implemented so far.
0 -
It is still downgrade. Server denied me insta-down, but I was able to start animation, so that means I had to be in range for normal hit at least.
0 -
you were only in range on your system, but on the server you could have been anywhere.
0 -
Pallet is only place where you can get denied hit, vault should not be a thing, or just let me disable it. It is almost never good for me.
0 -
Picking on helples christmas animals I see.
0 -
I just wanted Christmas dinner...
0 -
Yeah I don’t understand why it‘s not a guaranteed hit tbh. It really should be.
I remember one time I was playing ghostface and this happened to me at a window, it started a grab animation but changed it to a swing which subsequently missed.
So instead of being downed the survivor got away with Lithe and I ended up having to drop the chase because it wasn’t worth it anymore.
1 -
Yeah, one miss can lose you a game and what's most annoying, it's not even your fault here...
I lost that game as the Nemesis, because I didn't get that down -> new pop. He was dead on hook.
0 -
Server side validation is a mixed bag. It seems geared toward certain preset validations. Killers swinging at windows = killer side gets validated faster. Survivors dropping pallets = survivor side gets validated first.
When it comes to the grab animations I think the server/code hiccups and tosses the killers validation in exchange for the survivors movement inputs. This results in the animation playing for a small % of it's time, survivor moves, server validates the survivor "inputting a movement command", killer grab is unvalidated but the command of M1 remains so server back-ends it. Once it the animation is over the back-end log of the M1 press is validated on server side resulting in a often missed auto-attack.
0 -
Yeah, so their "fix" for canceled grabs usually doesn't work and only wastes your time.
It's ussualy bad even when you try grab survivors unhooking, because it's easier to bait M1. Before even if it got faked and canceled, you just had another attempt.
0 -
The whole premise is flawed.
If there's enough latency to cause the server to validate the grab, and to then reject the grab and initiate a swing instead, then there's enough latency for that swing to also be validated and certainly miss because the survivor is already long gone.
It needs to be a guaranteed hit.
1
