.kate
Member
Hello mr yoshi and co.
This is what I see on my screen:
View attachment Deadlock - 2026-03-28 10-09-47 PM.mp4
On my screen this is where i start the parry:
This is where Geist swap goes through, 9 frames later:
Next frame I get swapped
Here's what the demo recording captured:
View attachment Deadlock - 2026-03-29 1-00-56 AM.mp4
As you can see, according to the server I counterspelled AFTER the swap went out.
On my screen I parried 9 frames before the swap hit me, which at 60fps comes out to 150ms. The game says my ping is 27ms, which means that
there is AT LEAST a 120ms delay between me parrying and the server registering that parry.
There is NO WORLD in which that is an acceptable amount of delay on i-frames and other inputs based on reaction time. On my end I was there, I was ready for it, I predicted it. I did it early enough to compensate for ping. AND EVEN AFTER ALL THAT the server just said "no".
Another melee related clip:
View attachment Deadlock - 2026-03-28 6-03-32 AM.mp4
VS what the server saw:
View attachment Deadlock - 2026-03-28 6-44-04 AM.mp4
As you can see, this one isn't even a delay.
The guy straight up just punched into my parry, both client side and server side, and it did not register at all.
There is something VERY WRONG with the way melees and parries are handled; way too often i parry predictively way before i should, and it STILL gets completely ignored by the server.
Yoshi pls fix this is unplayable
This is what I see on my screen:
View attachment Deadlock - 2026-03-28 10-09-47 PM.mp4
On my screen this is where i start the parry:
This is where Geist swap goes through, 9 frames later:
Next frame I get swapped
Here's what the demo recording captured:
View attachment Deadlock - 2026-03-29 1-00-56 AM.mp4
As you can see, according to the server I counterspelled AFTER the swap went out.
On my screen I parried 9 frames before the swap hit me, which at 60fps comes out to 150ms. The game says my ping is 27ms, which means that
there is AT LEAST a 120ms delay between me parrying and the server registering that parry.
There is NO WORLD in which that is an acceptable amount of delay on i-frames and other inputs based on reaction time. On my end I was there, I was ready for it, I predicted it. I did it early enough to compensate for ping. AND EVEN AFTER ALL THAT the server just said "no".
Another melee related clip:
View attachment Deadlock - 2026-03-28 6-03-32 AM.mp4
VS what the server saw:
View attachment Deadlock - 2026-03-28 6-44-04 AM.mp4
As you can see, this one isn't even a delay.
The guy straight up just punched into my parry, both client side and server side, and it did not register at all.
There is something VERY WRONG with the way melees and parries are handled; way too often i parry predictively way before i should, and it STILL gets completely ignored by the server.
Yoshi pls fix this is unplayable
