Floating objects, when using command block setblock
I am testing the block with /setblock ~ ~ ~ saplings and ladder, but floating blocks
Step to reproduce:
- Command with /setblock ~ ~ ~ saplings/ladder
Result:
The objects was floating, when using setblock anything.
Test results as of 1.16.20
| Block | Floats when placed with /setblock |
|---|---|
| Saplings | |
| Ladder | |
| Lever | |
| Grindstone | |
| Crops | |
| Cactus | |
| Sugarcane (reeds) | |
| Bamboo | |
| Water | |
| Lava | |
| Torch | |
| Redstone torch | |
| Soul torch | |
| Item frame | |
| Kelp | |
| Cocoa |
Linked Issues
is duplicated by3
relates to3
Created Issue:
Floating objects, when using command block setblock
I am testing the block with /setblock ~ ~ ~ saplings and ladder, but floating blocks
Step to reproduce:
- Command with /setblock ~ ~ ~ saplings/ladder
Result:
The objects was floating, when using setblock anything.
I am testing the block with /setblock ~ ~ ~ saplings and ladder, but floating blocks
Step to reproduce:
- Command with /setblock ~ ~ ~ saplings/ladder
Result:
The objects was floating, when using setblock anything.
Test results as of 1.16.20
Block Floats when placed with /setblock Saplings Ladder Lever Grindstone Crops Cactus Sugarcane (reeds) Bamboo Water Lava Torch Redstone torch Soul torch Item frame Kelp Cocoa
is duplicated by
relates to
is duplicated by
relates to
Thank you for your report!
We're tracking this issue in MCPE-52857, 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Mojang Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit
Thank you for your report!
We're tracking this issue in MCPE-52857, 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:
📓 Issue Guidelines – 💬 Community Support – 📧 Mojang Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit
/setblock can be used to put blocks in all kinds of “illegal” positions, for example levers floating in air (MCPE-52857) or water in the nether. The reason why is that it skips the usual block checks and block updates that occur when placing a block. I’m not sure that’s a bug, since it is only possible with cheats and it could be convenient for map-making.
There is still an open report at MCPE-52857 that hasn't been updated in a while.
Thank you for your report!
We're tracking this issue in MCPE-52857, 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 expecting that the game would treat a player running the /setblock command as if the player destroyed the block? I don't think that's what on_player_destroyed is supposed to detect, nor is it how the /setblock command works.
In general, /setblock does not function as an in-world event, for example, setting a block does not trigger block updates around it. Although MCPE-52857 remains open, I think the general behavior of /setblock is intended because it likely calls the same internal function that allows the game to change block data without triggering further events, for example when generating structures.


The problem seems to be that the /setblock command does not update the placed block based on what is around it. However, the fact that some blocks instantly break suggests that the coding around this is not consistent.
Relates to MC-31100.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please add a comment or update the affected version field.
To make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Affects 1.19.30
Cocoa has regressed. Also affects frogspawn & possibly other blocks. Duplicated by
MCPE-162170.