Lagback/zh

回弹是指玩家被传送回之前的位置。它可以被利用于卡进墙壁或以类似卡角的方式跳得更高，尽管这些做法在多人服务器上可能是禁止的。在本文中，我们主要关注1.8的单人模式，但大多数信息都与多人模式和1.9+相关。

以下是已知的回弹触发因素：

• 卡在一个方块中。
• 与船相撞。
• 在蜘蛛网中移动过快。
• 以足够的速度在潜行时降落
• 以极快的速度(例如速度100)通过步行辅助移动。
• 靠着墙快速移动。

常规解释

触发回弹有两种方法：

• 与碰撞箱相交（卡在方块中，或与船相撞）。
• "错误地"移动。

第一种方法是无需解释的。

关于第二种方法，我们必须首先了解玩家的移动是如何在服务端处理的(即使是在单人游戏中，游戏也运行在一个集成的服务器上)。每过一刻，客户端就会计算玩家的下一个位置，并向服务器发送一个数据包。服务器通过从玩家的最后一个位置重新计算来验证玩家的移动，理论上两者计算结果应相同。然而，服务器不会消除玩家移动的副作用，这可能会导致玩家预期和实际位置之间的差异。如果两者之间的水平距离超过 0.25 m ，那么这种差异就会被认为是显著的，在这种情况下，玩家会被回弹至他们之前的位置。

在验证之前未消除的副作用包括：

• onGround 着陆时被设置为 true (这会改变潜行的行为)。
• inWeb 在与蜘蛛网碰撞时被设置为 false。
• 当与墙壁或天花板发生碰撞时，各种 collided 被设置为 true。

总之，玩家的移动每刻计算两次，但第一次计算的副作用可能会影响第二次计算的结果。如果玩家移动足够快，服务器就会认为玩家移动错误，从而触发回弹。

特殊触发的解释

与碰撞箱相交

玩家不应该移动到一个碰撞箱中。但是，服务器在每个方向都有 0.0625b 的宽容度，这意味着玩家的边界箱可以与方块的"表面"相交并正常移动。如果玩家进一步向内移动，就会触发回弹。

如果玩家已经完全进入方块的碰撞箱，则玩家在移动时不会回弹。

与蜘蛛网碰撞

当与蜘蛛网碰撞时（在滴答结束时检测，但在玩家的上一个位置），玩家的 inWeb 被设置为 true。当玩家移动并且 inWeb 为 true 时，它会立即被设置为 false，并且蜘蛛网的效果会应用在玩家的速度上。这会导致原始计算和重新计算之间存在差异，如果满足足够的速度，则会触发回弹。

在潜行时从高处落下

此变种是通过掉落和潜行实现的，具有以下要求：

• 水平移动速度超过 0.25m/t。
• 落地前至少在地面上方一格（在 1.11+ 中为 0.6 格）。

The minimum jump height required to achieve at least -1m/t of vertical speed is -7.3125b. An easy setup to try this method is -9.5b. You are not required to time the sneak exactly, but sneaking too early will significantly reduce the player's horizontal speed.

Sneak Glitch

A sneak glitch (or shift glitch) happens when the player sneaks while landing on an edge, which causes them to fall anyway (this was fixed in 1.16.2).

When performing a sneak glitch, the server's expected movement for the player is different from their actual movement. Here's why:

• During the original calculation, the player is sneaking but not "on ground", hence they move past the edge. However, they still land, which sets onGround = true.
• During the recalculation, the player is now considered "on ground" before actually landing, which changes the behaviour of sneaking: they can not "fall off the edge", despite not being at ground level.

With at least 0.25m/t of horizontal speed and appropriate placement, performing a sneak glitch can therefore trigger a lagback. After being teleported back to their previous position, the player is now able to jump. The resulting jump looks similar to a blip-up, in the sense that the player can start jumping mid-air. Here is an example:

Some jump heights do not work. This is still being investigated.

Code

In singleplayer, lagbacks are caused by this section of code (heavily simplified, we ignore exceptional cases such as flying, sleeping, teleporting, respawning, mounting an entity...):

//in NetHandlerPlayServer.java
public void processPlayer(PacketPlayer packetIn)
{
    double posY_original = this.playerEntity.posY;
    this.lastPosX = this.playerEntity.posX;
    this.lastPosY = this.playerEntity.posY;
    this.lastPosZ = this.playerEntity.posZ;
    double next_posX = packetIn.getPositionX();
    double next_posY = packetIn.getPositionY();
    double next_posZ = packetIn.getPositionZ();
    float yaw = this.playerEntity.rotationYaw;
    float pitch = this.playerEntity.rotationPitch;
    if (packetIn.getRotating()) {yaw = packetIn.getYaw(); pitch = packetIn.getPitch();}
</div>

    <div lang="en" dir="ltr" class="mw-content-ltr">
//checks whether the player is starting from inside a collision box: in this case, there is no lagback
    boolean noCollisionInside = worldserver.getCollidingBoundingBoxes(this.playerEntity, this.playerEntity.getEntityBoundingBox().contract(0.0625, 0.0625, 0.0625).isEmpty();
</div>

    <div lang="en" dir="ltr" class="mw-content-ltr">
//begin movement verification
    double deltaX = next_posX - this.playerEntity.posX;
    double deltaY = next_posY - this.playerEntity.posY;
    double deltaZ = next_posZ - this.playerEntity.posZ;
</div>

    <div lang="en" dir="ltr" class="mw-content-ltr">
if (this.playerEntity.onGround && !packetIn.isOnGround() && deltaY > 0.0)
        this.playerEntity.jump();
    this.playerEntity.moveEntity(deltaX, deltaY, deltaZ);
    this.playerEntity.onGround = packetIn.isOnGround();
    
    //calculates error between the expected and actual positions
    double errorX = next_posX - this.playerEntity.posX;
    double errorZ = next_posZ - this.playerEntity.posZ;
    double error_squared = errorX * errorX + errorZ * errorZ;
    boolean movedWrongly = (error_squared > 0.0625 && !this.playerEntity.theItemInWorldManager.isCreative());
</div>

    <div lang="en" dir="ltr" class="mw-content-ltr">
//sets the player to their actual position, and checks for collisions
    this.playerEntity.setPositionAndRotation(next_posX, next_posY, next_posZ, yaw, pitch);
    boolean next_noCollisionInside = worldserver.getCollidingBoundingBoxes(this.playerEntity, this.playerEntity.getEntityBoundingBox().contract(0.0625, 0.0625, 0.0625).isEmpty();
</div>

    <div lang="en" dir="ltr" class="mw-content-ltr">
//detects an error: player moved wrongly, or moved inside a collision box
    if (noCollisionInside && (movedWrongly || !next_noCollisionInside))
    {
        //lags the player back to their previous position
        this.setPlayerLocation(this.lastPosX, this.lastPosY, this.lastPosZ, yaw, pitch);
        return;
    }
</div>

    <div lang="en" dir="ltr" class="mw-content-ltr">
this.playerEntity.handleFalling(this.playerEntity.posY - posY_original, packetIn.isOnGround());
}

Note that the handling of fall damage is not processed if the player gets lagbacked. This may cause the player to suffer unexpectedly high fall damage when they eventually land. Since 1.15 (when the boat fall damage bug was fixed), jumping resets the player's fall distance, which can be abused to survive high falls when combined with lagback.