Minecraft Ticks in PvP: How Fast Actions Really Work

Minecraft Java Edition normally aims to run at 20 server ticks per second. One tick therefore has a target length of 50 milliseconds. During each tick, the server updates the world, players, mobs, effects and cooldowns. If a tick takes longer than 50 milliseconds, the server starts falling behind.

This does not mean that each player can perform only one action every 50 milliseconds. A player can switch slots, use a block and attack very quickly. Minecraft sends these actions as separate small messages called packets.

From your input to the server

When you press a key or mouse button, your game client reads the input. It may show an animation at once, but the server still decides what really happened.

Input → packet → server check → state change → result

Slot changes, block uses and attacks are different actions. Java Edition 1.21.11 has separate packets and server code for them. The server can check your selected item, hand, distance, target, cooldown and the current state of a block.

The server is the final source of truth. If your client showed something that the server did not accept, the server can send a correction.

What happens with several actions in one tick?

Several packets can reach the server during the same 50-millisecond tick window. They are not merged, and they do not happen at the exact same moment. The server handles them one after another.

Imagine this order:

Switch slot → use block → switch slot → attack

If the server accepts all four actions, the block use can see the slot selected before it. The attack can then see the next slot change. Each accepted action can change the state used by the next action.

There are still clear limits. An invalid action may be ignored. One action can make a later action impossible. A first attack can reset the attack charge, so another immediate attack has much less power. The game tracks attack charge over time and resets it after an attack.

Two packets sent close together are also not guaranteed to be handled in the same tick. Their arrival time and the server’s current load still matter.

How fast can an anchor be?

A fast anchor is not truly instant. In Java Edition 1.21.11, the normal sequence is:

Place the anchor → charge it → switch item → explode it

The game client checks inputs 20 times per second. That means one client tick lasts about 50 milliseconds. Because the item switches and right clicks must happen in the correct order, the full sequence normally needs about two client ticks.

The anchor itself does not add another delay. As soon as the server receives the charge action, the anchor becomes charged. If the explosion action comes directly after it, both actions can even be handled during the same server tick.

Ping moves the whole sequence back in time. For example, with higher ping, the explosion appears later on the server. However, the server does not need to confirm every step before the client sends the next one.

Holding right click is slower because Minecraft waits before repeating the action. Fast anchoring therefore uses separate, well-timed clicks instead.

How attribute swapping fits into this

Attribute swapping means changing items so quickly that an action may use values linked to different item states. An attribute is simply a number that changes what an item can do, such as attack damage, attack speed or reach.

Changing the selected slot and attacking are separate actions. With very fast timing, equipment updates and attack checks may not line up as expected. Reports from some 1.21.11 Paper servers describe mixed effects from fast sword, mace or spear swaps.

This does not mean that two items are truly used at the same moment. It means that one part of the server may already see the new item while another value was set by the earlier state.

Attribute swapping is also not a safe rule that works everywhere. Server software, plugins, anti-cheat systems and later fixes can change the result.

Ping and tick timing

Ping is a rough measure of how long information takes to travel to the server and back. It does not show the exact delay of every single action. Minecraft’s own ping reply may also wait until the client’s next tick, so the shown value is not a perfect network measurement.

There is also a difference between a prepared chain and a reaction chain.

In a prepared chain, you send several inputs without waiting for the server. Higher ping may delay the whole chain, but the actions can still remain close together.

In a reaction chain, you wait to see a server result before performing the next input. Ping matters much more because the answer must travel back to your client first.

The real limits of fast PvP

Fast inputs cannot remove every game rule. Attack charge, item cooldowns, reach, block state, the selected hand and server checks still apply. More clicks do not automatically create more full-damage hits.

Server performance is separate from ping. A good connection cannot fix a slow server, and stable server ticks cannot remove a player’s high ping.

The best way to understand very fast PvP is simple: the client sends an ordered chain of actions, and the server checks each action against the state created by the actions before it.