MC-45116Second block standing Glitch through head bounce jump
The video below displays a glitch by which a player with jump boost 3 ends up standing on the second block down in a stack consistently through the holding down of the forward key, jump key, and sprint key simultaneously on a pattern of stacks seperated by one block and taking the shape of 3 x 3 structures with a surface superior to the line two blocks above the structures. Upon encountering the glitch, rapid jerky "jumps" occur until you release the jump key. Then it appears that the player is floating adjacent to the stack. In reality, the player is stood on the middle block.
See this video: https://drive.google.com/file/d/0Bx7E5slZlf3oUHV1YUU0UHZJM2c/edit?usp=sharing.
Created Issue:
Second block standing Glitch through head bounce jump
The video below displays a glitch by which a player with jump boost 3 ends up standing on the second block down in a stack consistently through the holding down of the forward key, jump key, and sprint key simultaneously on a pattern of stacks seperated by one block and taking the shape of 3 x 3 structures with a surface superior to the line two blocks above the structures. Upon encountering the glitch, rapid jerky "jumps" occur until you release the jump key. Then it appears that the player is floating adjacent to the stack. In reality, the player is stood on the middle block.
See this video: https://drive.google.com/file/d/0Bx7E5slZlf3oUHV1YUU0UHZJM2c/edit?usp=sharing.
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.