Momentum

Hit reg

Knockback

Methods

Why movement changes effective reach

Effective reach means the spacing at which you can actually win the next hit. Your survival attack ray does not grow when you sprint. The client traces from your eyes toward the visible target’s hitbox and rejects entity intersections beyond three blocks. Aiming steeply upward also spends part of that distance vertically, leaving less horizontal range. There is no velocity-based reach deduction in this targeting routine.

Two players do not see the same moment

Your own movement is simulated locally. Other players arrive through server updates, and their displayed positions interpolate toward those updates. The server’s entity tracker also quantizes movement coordinates in 1/32-block steps. That quantization is not an extra 1/32 block of guaranteed reach. The important distinction is that your current position and the opponent’s displayed position can represent different moments.

When you run toward someone, your locally simulated position is farther forward than the position they have received for you. If they approach more slowly, their older position is only a little farther away on your screen, while your older position can be noticeably farther away on theirs. Your crosshair can acquire them before theirs acquires you. Backpedaling reverses the relevant displacement: the older position they see can be closer than where you have already retreated. This is a timing advantage, not a change to either player’s permitted ray length.

A simplified spacing calculation

Consider a level, straight approach with the same hitbox geometry on both sides. Let d be the present eye-to-near-hitbox gap, uA and uB the speeds toward each other, and τA and τB the effective ages of the displayed remote positions. Ignoring changes in velocity and interpolation details, a useful approximation is:

• A’s displayed gap ≈ d + uB × τB.
• B’s displayed gap ≈ d + uA × τA.

For an illustration, take d = 2.60 blocks, A moving at 5.6 blocks/s, B at 2.0 blocks/s, and both displayed remote positions about 0.10 seconds old. A sees roughly 2.80 blocks; B sees roughly 3.16. A can acquire B while B cannot yet acquire A. The 0.10 seconds is an assumed display age, not a formula equating ping with interpolation delay. These numbers illustrate the mechanism; they are not a server reach formula or a guaranteed advantage.

What the server does with the attack

Client targeting is only the first gate. The attack request identifies an entity; the server then processes it against its own state. In the Spigot 1.8 reference, the use-entity handler checks the target, line of sight, and a broad squared-distance bound before calling the attack routine. That guard is not the client’s exact three-block eye-to-box ray, and does not grant a legitimate client a longer ray. Combat plugins and anti-cheat can impose additional checks.

Damage eligibility is another gate: hurt resistance can reject an equal-or-weaker follow-up even after an attack was targeted. Movement updates, attack arrival order, immunity, and subsequent knockback therefore affect who receives damage and whether the other player can trade. The attacker’s screen does not have unconditional authority over the result.

How this sustains a combo

After a hit, keep enough forward movement to meet their displaced hitbox near your reach boundary, while leaving them too far away in their own view to answer first. A W release resets sprint and helps regulate that gap; holding it too long can lose the chase, while moving in too soon gives them a counterhit. Their return to zero velocity does not automatically end the spacing advantage: their position, elevation, displayed information, and the next attack opportunity still matter. If both players instead have perfectly current positions and identical level geometry, speed alone cannot create an unequal static reach limit.