Moving blocks do not tick past the world border, causing them to stay offset when pushed by a piston
The bug
Moving_Block do not tick past the worldborder causing them to stay offset / create a ghost block when pushed by a piston.
This seems like a regression of MC-54366
Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Code analysis
Based on 1.11 decompiled using MCP 9.35 rc1
The method net.minecraft.block.BlockPistonBase.canPush(IBlockState, World, BlockPos, EnumFacing, boolean) only tests if the position of the block to move is inside the worldborder, but not if the new position is inside it as well.
The reason why the piston_extension tile entity is not removed is because the method net.minecraft.world.World.updateEntities() removes only invalid tile entities inside the worldborder.
Linked Issues
is duplicated by42
- Unresolved
Marcono1234- 28
- 22
- Confirmed
Low
- Platform
- Block states Rendering
- moving_piston piston world-border
1.8.7 - 1.21.1
1.8.7 15w47c 15w51b 1.9 1.9.2 16w15b 1.10.2 16w42a 16w43a 16w44a 1.11 1.12.1 1.12.2 1.13 18w30b 1.13.1 1.13.2-pre2 1.13.2 18w48a 18w48b 19w08b 19w09a 19w12b 19w13b 19w14a 19w14b 1.14-pre2 1.14-pre3 1.14-pre4 1.14-pre5 1.14.4 1.15.2 20w18a 1.16.1 20w28a 20w30a 1.16.2-pre1 1.16.2-rc1 1.16.2-rc2 1.16.2 1.16.3-rc1 1.16.3 1.16.4-pre1 1.16.4-pre2 1.16.4-rc1 1.16.4 20w46a 20w48a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w08b 21w11a 1.17-pre2 1.17 1.17.1 21w37a 21w43a 1.20.2 1.20.3-pre2 1.20.4 24w12a 1.20.6 24w18a 1.21.1
Created Issue:
Pistons fail pushing blocks trough worldborder
This seems like a regression of
MC-54366Pistons can somehow still push blocks trough the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
This seems like a regression of
MC-54366Pistons
can somehow stillpush blocks trough the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.This seems like a regression of
MC-54366Pistons still try to push blocks trough the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
relates to
is duplicated by
is duplicated by
This seems like a regression of
MC-54366Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Pistons fail pushing blocks through worldborder
is duplicated by
is duplicated by
This seems like a regression of
MC-54366Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Code analysis
Based on 1.11 decompiled using MCP 9.35 rc1
The method net.minecraft.block.BlockPistonBase.canPush(IBlockState, World, BlockPos, EnumFacing, boolean) only tests if the position of the block to move is inside the worldborder, but not if the new position is inside it as well.
The reason why the piston_extension tile entity is not removed is because the method net.minecraft.world.World.updateEntities() removes (for whatever reason) only invalid tile entities inside the worldborder.
This seems like a regression of
MC-54366Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Code analysis
Based on 1.11 decompiled using MCP 9.35 rc1
The method net.minecraft.block.BlockPistonBase.canPush(IBlockState, World, BlockPos, EnumFacing, boolean) only tests if the position of the block to move is inside the worldborder, but not if the new position is inside it as well.
The reason why the piston_extension tile entity is not removed is because the method net.minecraft.world.World.updateEntities() removes
(for whatever reason)only invalid tile entities inside the worldborder.
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Pistons fail pushing blocks through worldborder, creating ghost blocks
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
The bug
Pistons fail pushing blocks through worldborder, creating ghost blocks.
Moving_Block's do not tick past the world border causing them to stay offset when pushed by a piston.This seems like a regression of
MC-54366Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Code analysis
Based on 1.11 decompiled using MCP 9.35 rc1
The method net.minecraft.block.BlockPistonBase.canPush(IBlockState, World, BlockPos, EnumFacing, boolean) only tests if the position of the block to move is inside the worldborder, but not if the new position is inside it as well.
The reason why the piston_extension tile entity is not removed is because the method net.minecraft.world.World.updateEntities() removes only invalid tile entities inside the worldborder.
Pistons fail pushingblocks throughworldborder,creating ghost blocksMoving_Block do not tick past the worldborder causing them to stay offset when pushed by a piston
The bug
Pistons fail pushing blocks through worldborder, creating ghost blocks.
Moving_Block's do not tick past the world border causing them to stay offset when pushed by a piston.This seems like a regression of
MC-54366Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Code analysis
Based on 1.11 decompiled using MCP 9.35 rc1
The method net.minecraft.block.BlockPistonBase.canPush(IBlockState, World, BlockPos, EnumFacing, boolean) only tests if the position of the block to move is inside the worldborder, but not if the new position is inside it as well.
The reason why the piston_extension tile entity is not removed is because the method net.minecraft.world.World.updateEntities() removes only invalid tile entities inside the worldborder.
The bug
Moving_Block do not tick past the worldborder causing them to stay offset / create a ghost block when pushed by a piston.
This seems like a regression of
MC-54366Pistons still try to push blocks through the worldborder, however they stay at the position they were as some kind of "ghost" blocks (very likely the piston_extension block, which the client still renders, however it doesn't exist anymore, /testforblock returns air). After reloading this area they are gone.
Code analysis
Based on 1.11 decompiled using MCP 9.35 rc1
The method net.minecraft.block.BlockPistonBase.canPush(IBlockState, World, BlockPos, EnumFacing, boolean) only tests if the position of the block to move is inside the worldborder, but not if the new position is inside it as well.
The reason why the piston_extension tile entity is not removed is because the method net.minecraft.world.World.updateEntities() removes only invalid tile entities inside the worldborder.
Moving_Block do not tick past the worldborder causing them to stay offset when pushed by a pistonMoving blocks do not tick past the world border, causing them to stay offset when pushed by a piston
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
However, this issue is a Duplicate of MC-82010.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Duplicate of MC-82010, for future reference, bug reports are only accepted in English.
Do not duplicate your own report. Instead, next time go to MC-82010 and comment that it is still an issue in 1.13.2.
Thank you for your report!
We're actually already tracking this issue at MC-82010, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue in MC-82010, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Can this issue also be reproduced without using MC-82010?
Thank you for your report!
We're actually already tracking this issue in MC-82010, so I've resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
If the reporter was referring to the worldborder, then this is MC-82010.
Duplicate of MC-82010
MC-82010 does describe the issue with ghost blocks.
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-82010, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Duplicate of MC-82010
Duplicate of MC-82010
Thank you for your report!
However, we are already tracking this issue, and this report is a Duplicate of MC-82010, which is a report that has not been resolved yet.
If you want, you can upvote the parent ticket, and enable watching to receive any updates about it - if you believe you have any information that may be important for this issue, please leave a comment on the parent. Please also use the search function in the future to prevent duplicate reports.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord
Duplicate of MC-82010
This ticket should most likely be resolved as a duplicate of MC-82010.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Duplicate of MC-82010.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-82010.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-82010.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicate of MC-82010.
Duplicates MC-82010 Not sure about the kick issue because your game is modified.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Duplicate of MC-82010.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're actually already tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any additional information to the main ticket it would be appreciated.
Please be sure to use the search feature before creating a ticket to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Mojang Support – ✍️ Feedback and Suggestions – 💬 Mojira Discord
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote or any additional information to the main ticket it would be appreciated.
Please be sure to use the search feature before creating a ticket to see if the issue has already been reported.
Quick Links:
📗 Tracker Guidelines | 🛠 Community Support | 📧 Mojang Support | 🔑 Account Support | ✍️ Feedback Discord | 💬 Mojira Discord
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
When pushing a shulker using a piston next to the world border, the piston glitches into the shulker.
How to reproduce
Start by summoning a shulker using the following command:
/summon shulker ~ ~ ~ {NoAI:1b}
- Place a piston next to the shulker in an attempt to push the shulker outside the world border.
- Place a block of redstone to activate the piston and observe.
Observations and Expectations
Observation: Piston seems to glitch inside the shulker when pushed next to the world border.
Expectations: Piston shouldn't glitch inside the shulker even if its forbidden for the block/mob to exit the world border.
Notes: Discovered while testing MC-271320.
Relates to MC-82010.
Using a piston to push a block next/outside world border glitches the block and disables block's outline.
How to reproduce
Teleport to the world border using the following command:
/tp 299999999 256 299999999
- Place any block 1 block before the world border
- Place piston to push the block to the world border and break the piston afterwards.
- You will notice that the block's outline is completely gone even though the block still acts like a block after glitching.
Observations and Expectations
Observations: Block's outline completely disappears after pushing outside world border.
Expectations: It should still appear even after glitching since it stills acts like a block.
Notes: Relates to MC-82010.
Thank you for your report!
We're tracking this issue in MC-82010, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
This is a duplicate of MC-82010.


Your summary and description contradict each other.
I changed the description
Confirmed.
Confirmed for 1.9
Still in 16w15b
Confirmed for 1.13.2-pre2.
Cannot reproduce in 1.14 pre-5. It seems to be patched.
Pistons pushing blocks through worldborder (1.14 pre5).mp4
@ZeNico13
From the looks of your video, your worldborder is not perfectly aligned to a block boundary, while the worldborder may not always visually line up perfectly with the edges of blocks, any blocks that it partially includes are treated as being within the worldborder. This means that you weren't actually pushing the blocks outside the worldborder.
Confirmed to still be in 1.14.4
Not sure if it's in the 1.15 snapshots
Can confirm in 20w51a.
Ghost blocks also occur adjacent to the worldborder, if another block is pushed into them but then removed. They will remain visual as long as the world is loaded, and visually disappear but still remain when reloaded. Only upon moving the worldborder the block will become valid again.
This also applies to slabs and stairs being pushed into each other, producing visual double slabs/stairs from different, overlapping materials.
Not sure if this helps, but the block will disappear if tnt tries to explode it.
Just saying.
It is not a ghost blocks. It is a "moving_block". When a piston push a block, it creates a "moving block" outside of the worldborder.
Can confirm in 1.17.1
That was already marked as affected.
I would like to ask that we rename this bug report from: Pistons fail pushing blocks through worldborder, creating ghost blocks to Moving_Block's do not tick past the world border causing them to stay offset when pushed by a piston
Cause the current title is completely inaccurate