To answer your other questions, the functionality of the underside remains the same if the end portal blocks are accessed in a normal manner. The rest of the quote directly applies to this situation. This satisfies the condition in step 1, and the bug is triggered. Now I have yet been able to find why a player triggers teleportation even though they are one block below an end portal block, but as far as I can remember, a player's y position slightly jumps up immediately when they are pushed before being placed in a legal post-push position, as technically there is a collision into a (moving) block.Īssuming this is true, the player is placed in a position between the end portal block and end portal frame block right above the player's original position (which has slightly changed in either the x or z direction, but not fully). The player is dropped into the end at their previous position, likely causing them to fall into the void and dieĭoing this check before block collision functions are called (or at least also cancelling the dimension change) would solve the problem.This will include footage editing, brush technique, scrap kits, vector clipart, photo frames, photo albums, overlays and actions for Photoshop. The collision checks whether the player's move was invalid and reverts the player's position, but not dimension change (Bug 2) Videohive - Glitch Logo 45363756 After Effects Version CC Files Included After Effects Project Files.Even though the move is illegal, the end portal's collision function gets called and the player is teleported into the end (Bug 1).A player somehow sends a move packet that places them halfway between an end portal block and an end portal frame block.However, this check is done even if the player has been teleported by a portal block such as the end portal, which can lead to the following problem:
The NetHandlerPlayServer.processPlayer (MCP name) function checks if the player's bounding box is intersecting any blocks, and if it is, reverts the player's position to the old one. We can take a look at the description part of the first bug report written by Runemoro: This bug seems to be currently tracked as MC-123364 although a more relevant reproduction is MC-223409.
0 kommentar(er)
