This is a bug, not a suggestion. I am simply suggesting a fix for this bug.
From NetHandlerPlayServer:
d9 = d6 - this.player.posZ;
d11 = d7 * d7 + d8 * d8 + d9 * d9;
boolean flag = false;
if (!this.player.isInvulnerableDimensionChange() && d11 > 0.0625D && !this.player.isPlayerSleeping() && !this.player.interactionManager.isCreative() && this.player.interactionManager.getGameType() != GameType.SPECTATOR)
{
flag = true;
LOGGER.warn("{} moved wrongly!", (Object)this.player.getName());
}
this.player.setPositionAndRotation(d4, d5, d6, f, f1);
this.player.addMovementStat(this.player.posX - d0, this.player.posY - d1, this.player.posZ - d2);
The position seems to get reverted right after the teleport: this.player.setPositionAndRotation(d4, d5, d6, f, f1); Removing that line fixes the problem. Disconnecting right after changeDimension (by setting a breakpoint) causes the player to have the dimension changed but not the position, which could even be abused intentionally by some players.
Yes, I just figured it out how to do it:
1. Build this:
[media]
2. Stand on the block right next to the corner of the end portal
3. Place a bed on the block you're standing on (so that its corner touches the corner of the end portal), and you should be inside the bed block (this is another bug, I'm guessing)
4. Sneak to the left edge (in the image) of the block the bed is on
5. Once you're right at the edge, try going back into the bed block, still sneaking. You should see your player jumping backwards while you hold W as the server cancels the move events.
6. Move along the bed's edge towards the portal (at an approximately 10-20 degree angle towards the bed). Make sure you keep getting the jumps back as you move which show the collision checking code is being activated.
7. When you eventually reach the portal block, you should get teleported into the end, but at your current coordinates. It might not happen on the first attempt.
Ok, it's fixed
Ok
I did. Also, you have to re-join the game to see the blocks glitch
Ok then.
For this one it's only ONE hopper and any item, not a clock and a chest under the hopper.
This is NOT the same ticket, MC-5998 needs a chest to work, and works only with the clock. This happens when an item is thrown on the edge of a hopper.
Works with any item, it usually happens when throwing the item on the edge of the hopper. No chest is needed.
Also happens when flying right after sprinting
The Crtl-F3-C key combination doesn't work on all keyboards. This seems to be a keyboard limitation, and not a Minecraft bug. Try checking if you're able to press all three keys at the same time using this tool: http://keyboardchecker.com/. I'm not.