MC-136709Blocks placed down in front of firing pistons cause a ghost block to be created
If you place a block right before a piston pushes forward, it will create a ghost of the block. This block will not react to anything, as (I believe) only the client thinks the block is there. if you try to place a block on the ghosted block, the ghost will become the block you tried to place down. It is worth noting that I was not able to replicate this in survival mode. When trying to pull these blocks with sticky pistons, they disappear.
Not sure if the pictures loaded right so...
Tnt does not react,
Also creates floating sand (also ghosted)
It seems to be the easiest to reproduce it with sand.
Here is a video showing the bug in action:
<video removed due to autoplay, see attachment instead>
Linked Issues
Normal
LowAttachments10
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
Created Issue:
Blocks placed down in front of firing pistons cause a ghost block to be created
If you place a block right before a piston pushes forward, it will create a ghost of the block. This block will not react to anything, as (I believe) only the client thinks the block is there. if you try to place a block on the ghosted block, the ghost will become the block you tried to place down. It is worth noting that I was not able to replicate this in survival mode. When trying to pull these blocks with sticky pistons, they disappear.
Not sure if the pictures loaded right so...
Tnt does not react,
Also creates floating sand (also ghosted)
Environment
Single player
Creative mode
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
Single player
Creative mode
If you place a block right before a piston pushes forward, it will create a ghost of the block. This block will not react to anything, as (I believe) only the client thinks the block is there. if you try to place a block on the ghosted block, the ghost will become the block you tried to place down. It is worth noting that I was not able to replicate this in survival mode. When trying to pull these blocks with sticky pistons, they disappear.
Not sure if the pictures loaded right so...
Tnt does not react,
Also creates floating sand (also ghosted)
It seems to be the easiest to reproduce it with sand.
Here is a video showing the bug in action:
Patrick McCarthy, could you use structure blocks to save the mechanism you've used to reproduce and attach the resulting .nbt file to this ticket?
relates to
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
If you place a block right before a piston pushes forward, it will create a ghost of the block. This block will not react to anything, as (I believe) only the client thinks the block is there. if you try to place a block on the ghosted block, the ghost will become the block you tried to place down. It is worth noting that I was not able to replicate this in survival mode. When trying to pull these blocks with sticky pistons, they disappear.
Not sure if the pictures loaded right so...
Tnt does not react,
Also creates floating sand (also ghosted)
It seems to be the easiest to reproduce it with sand.
Here is a video showing the bug in action:If you place a block right before a piston pushes forward, it will create a ghost of the block. This block will not react to anything, as (I believe) only the client thinks the block is there. if you try to place a block on the ghosted block, the ghost will become the block you tried to place down. It is worth noting that I was not able to replicate this in survival mode. When trying to pull these blocks with sticky pistons, they disappear.
Not sure if the pictures loaded right so...
Tnt does not react,
Also creates floating sand (also ghosted)
It seems to be the easiest to reproduce it with sand.
Here is a video showing the bug in action:
<video removed due to autoplay, see attachment instead>
![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
relates to
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
Duplicate of MC-136709.
Thank you for your report!
We're tracking this issue in MC-136709, 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.
Are you able to attach a video?
^ and if you can't provide a video was your TPS low (MC-133187)?
I tried to upload a video. It was too large. TPS was 4 ticks when I checked. This glitch has been around for a while, I just never posted anything. I really don't know when it started (which version).
TPS is usually 2 yes?
No, it's usually 20.
Oh xD
You mean where it says 5 ms ticks (now 5-6)
It isn't that hard of a glitch to replicate if it works for you. Essentially set a piston to a low speed clock, then keep trying to place a block (preferably sand) in front of it. If you use sand, do it in front of a gap/ledge. That way you can tell if it worked (otherwise it will fall).
– Correction:
Try to place the sand in front of the piston right before/as it is extending. if you click and nothing places at all, keep trying to place it slightly earlier each time.
No, to find what your TPS is type /debug start then after a while when the ghost blocks appear type /debug stop.
okay
Yeah, as I expected, didn't really depend on that. But it is normal 20.00 ticks per second
I think the only real way you can understand it is to get it to work for yourself. It is much easier after the first time (you get it down).
Is it possible for you to attach a screenshot of the issue so I can reproduce?
Finally just got the pictures to upload properly
They might help to give you a visual
That was good timing...
Is that helpful? If you get it to work let me know, and try placing a block on the ghost one. It will turn to the block you try to place.
Also this one is easy... it is not the same bug but a major one.
place a block down, any one as far as I'm aware, and then do this when standing on it
/summon minecraft:falling_block ~ ~-1 ~ {Time:200,BlockState: {Name: "minecraft:polished_andesite"}}
it has to be the block you are standing on (the id has to match)
it will also create an only client side issue
I've tested it on a small server before. My friends saw the blocks (possibly only sometimes I don't remember)
It creates an open space that is confused whether you can or cannot occupy the space.
a falling sand entity does fall. Also if you place something like tnt (then glitch it) it will be invisible and partially solid, and can be ignited
This one should be impossibly easy to replicate
I'm sorry, but I can't seem to be able to reproduce this issue. Am I doing this right (2018-09-03_17.07.47.png
)? Can you upload the video to a site like YouTube and link it here?
place a block one down in front of the piston so you can place it on a ground surface
that should totally help you
let me just say I appreciate your dedication xD that is almost if not impossible that way
Also don't forget to try the second one I mentioned. You should get it first try just copy and paste the short little command into your chat
and of course stand over the block of falling block choice
the block also doesn't have to float mid air; it can be on the ground
I just added a screenshot with a better angle.
Also this image is possible if one or more blocks of snow to form the golem are ghost blocks.
I still cannot reproduce I'll ask helpers and mods if they can. For the second one that you mention I'm pretty sure that would be
MC-72248.Just confirmed that upon reloading the world, the ghost blocks will disappear.
Yes, I just checked. That fits the description. Nice work!
Has this one with the piston to ghost block been reported?
... I just found out if you ghost a slime block, all of the blocks attached to it get ghost clones
update...
yeah there are some weird things going on using slime blocks. noting that
It is not
MC-54026since you are not using slime blocks and you said your TPS is 20.00 so not MC-133187.^ or better yet attach your world. If your world is too big, use a website like Dropbox and give us the link to download your world.
The ghosting with slime blocks issue is reported as
MC-54026.It isn't so much a mechanism. It is what I used to achieve it. It is a guide. Really all you need to do is place a block in front of a piston right as/before it is firing.
I believe this is a totally different issue with the slime blocks. I mean than the one reported before. The ghosted slime block tries to pull blocks along, also ghosting them (not yet figured out how consistently).
Is this a good setup?
If one of the mods can replicate this, make sure they do it with sand for a screenshot (should be floating and ghosted), or just a normal block then (try to) place another block on it (should become the block you placed on ghosted one).
I suppose
nvm no
set the repeaters to something higher
it is just so that you have time to retry for the next time it extends.
This might be possible in a server where a friend could power the piston for you, but the clock is the only way to do it by yourself
Delay of 2, 3, or 4?
The environment is suppose to contain PC details only. Also, thanks carpet0928 for trying to help.
Thanks for the Environment fix. The delay does not matter. Preferably something higher to make it easier for you. you could even have more than 2 repeaters if that helps.
The easiest setup to see if you got it right (in my opinion) is sand. So if you are trying to replicate it, it is easiest to use sand.
Again, I've got to thank you guys for being so patient with me. I'm glad you keep trying to replicate this. It just takes precise timing. Almost positive it is frame perfect to get it to work.
Can confirm, I think that I've gotten it to work!
Thank you!
I'm so happy that no one has to keep trying that for another hour xD
now try placing a block on the sand
solid prefereably
In fact, I've relogged and the ghost block disappeared as you've said it would. Will try again...
Alright, when I got the ghost block to pop back up, I tried to place stone on it, but the stone simply replaced the "block of sand".
Oh... woops
Well it should be much easier now that you got the timing
nice work!
now let me say now that nothing will update the block. it only disappears completely or is replaced
now if you like, to understand it better, you could try the slime block with it now. You'll have to place a block next to the place-down point
to see if it clones it as I said earlier
So I guess that's it! I truly can confirm this bug.
I truly appreciate how kind people can be on this bug tracker, it means so much. It's not every time that you get to go out of your way just to make someone's day, so those opportunities are so valued. Thank you all for your great effort, keep up the good work!
Yay! I am happy. Yeah it has been in the game since I don't even know when.
carpet0928, can you provide a video so I can reproduce? I'm probably not timing this right...
Yeah, there are a lot of weirder things that come from interactions with these ghosted blocks, but it would never happen without the bug in the first place. So it of course should be under the same thing.
It is a very precise timing as I'm sure carpet0928 could tell you. With 30 fps on MC and recording, I don't think it would be of much help. Also it is difficult for me upload anything because of the file size restrictions.
But some tips...
hmm...
try placing it when the piston is extending. Then, because obviously that won't work, make it VERY slightly earlier each time. until you get it.
If you place a normal block instead (PLEASE USE SAND), try slightly later.
Also... you can push ghost blocks with other ghost blocks (and normal ones)
Forgot to mention this... supporting the only client side (theory), entities other than the player will appear to land on the sand blocks, but a moment later show that they never actually interacted with it (they fall through it). Observers also do not detect when these ghost blocks are moved, but do detect when they are replaced with normal ones.
[Mod] Asteraoth, I don't think I have any software capable of recording Minecraft gameplay.
My advice is to just keep trying, but if it is too frustrating, don't worry about it. Carpet already got screenshots other than the ones I provided. And he knows how to replicate the glitch consistently.
Are you guys clicking the piston's head or the block in front? I'm not giving up yet.
The block in front. That is why earlier I said to place a block down to place on a "ground block"
you can also place on the side of a block but I find it easier on the ground
I wish you luck. Let us know when you got it. Screenshot club too; gotta join it haha
Click on the lime block.
Unrelated but, I also reported a very strange bug of sorts involving blocks and entities reverting to where and how they were before. It didn't include all blocks in the area strangely. broke/changed half of my command block system Anyway, I haven't had any word on how that progress is going. Not that it is a big deal, but if you can, could you ask about it? The only thing I'm concerned about now is whether or not I can use the world, or if I should leave it alone until I have more information on how to handle it.
Can confirm, too. I only managed to get it to work with sand, tho, which seems really strange to me.
<video removed due to autoplay, see attachment instead>
Also the things you are discussing here are normal properties of ghost blocks, which is a result of them being client side only.
Sand does not fall, because only the server removes the block from the world and spawns a falling block entity.
It's gone after reload because the server does not save it to the world as it doesn't really exist.
I think you guys have done a fantastic job of replicating this, and also simplifying my explanation of it. However, you can get it to work with any solid block that does not get destroyed by a piston attempting to move it. For some interesting results, I'd suggest slime blocks (very strange)They appear and disappear after being pulled by other slime blocks (Upon updating the area the blocks were in)
Additionally, while server-side entities (not the player), cannot actually interact with the ghosted block, it is clear that any blocks thatare affected by gravity are held up by ghost blocks.They are not and only appear to be momentarily Ghost blocks also do not cause updates ex. observers, BUDs. Only replacing the ghosted block with another will cause an update.Just some fun thing to mess around with, I'm sure there are some things I missed, but most of the major things are covered.
*Note: I tried to get a video of the crazy train of ghosted slime blocks (and other attached blocks), but could not get the video to work.
I've saved the structure that I've used to reproduce to a datapack (datapack_MC-136709.zip
) in case anyone has trouble trying to reproduce this issue in the future.
Confirmed for 1.14.2 Pre-Release 2.
Apparently confirmed for 1.17.1, see
MC-240815which seems to duplicate this bugpost here.Note that with the setup in linked bugpost, several blocks get ghosted.