MC-263062Trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed
The Bug:
Trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed.
Suspicious gravel and sand are destroyed when they fall. This makes it so that the player must be cautious when brushing, as one wrong move could result in the suspicious blocks being destroyed. Having suspicious gravel generate floating within trail ruins doesn't seem right, because as soon as these blocks receive a block update, they will fall and be destroyed.
Here is an example:
Seed: 8565983754514446683 Coordinates: /execute in minecraft:overworld run tp @s 13610.58 87.00 12688.70 -475.34 -21.90
Steps to Reproduce:
- Generate a world with the seed provided above and teleport to the given coordinates.
- Look closely at the floating suspicious gravel block.
- Take note as to whether or not trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed.
Observed Behavior:
Trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed.
Expected Behavior:
Trail ruins would not be able to generate with floating suspicious gravel blocks. This would make it so that suspicious gravel wouldn't be unintentionally destroyed.
Linked Issues
Attachments2
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
Created Issue:
Trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed
The Bug:
Trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed.
Suspicious gravel and sand are destroyed when they fall. This makes it so that the player must be cautious when brushing, as one wrong move could result in the suspicious blocks being destroyed. Having suspicious gravel generate floating within trail ruins doesn't seem right, because as soon as these blocks receive a block update, they will fall and be destroyed.
Here is an example:
Version: 1.20 Pre-release 7Seed: 8565983754514446683 Coordinates: /execute in minecraft:overworld run tp @s 13610.58 87.00 12688.70 -475.34 -21.90Steps to Reproduce:
- Generate a world with the seed provided above and teleport to the given coordinates.
- Look closely at the floating suspicious gravel block.
- Take note as to whether or not trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed.
Observed Behavior:
Trail ruins can generate with floating suspicious gravel blocks, causing suspicious gravel to be unintentionally destroyed.
Expected Behavior:
Trail ruins would not be able to generate with floating suspicious gravel blocks. This would make it so that suspicious gravel wouldn't be unintentionally destroyed.
![[Mojang] Moesh](../../../data/avatars/users/10122.svg){kind=small}
Normal![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
![[Mojang] Billy Sjöberg](../../../data/avatars/users/42806.png){kind=small}
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
is duplicated by
This issue was discovered when testing MCPE-178015
Relates to MC-263062
[Mojang] Billy Sjöberg said, the block doesn't fall until a neighboring block is updated.
When the sand or gravel is generated floating it never falls no matter how many random gameticks pass.
However, when the suspicious sand or gravel is generated floating it will fall after some random gameticks which is also different from Java Edition
Analysis
Here is a video that shows the issue MCPE-178020.mp4
| Sand generated floating | Sand suspicious generated floating | Gravel generated floating | Gravel suspicious generated floating |
|---|---|---|---|
not fall  |
fall  |
not fall |
fall |
Steps to reproduce:
- Import world ( Suspicious gravel and sand bug.mcworld ) and enter
- teleport in coord
/tp -416 66 -205
- Wait two minutes
Observed behavior:
Gravel and sand suspicious block, falling when passing some random gameticks
Expected behavior:
Gravel and sand suspicious block, never falling when passing some random gameticks
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
Thank you for your report!
We're tracking this issue in MC-263062, 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.
Discussed internally and will close this as a WAI.
While this example is a bit unfair to the player since the block is not visible at first sight this is a gameplay feature and the block doesn't fall until a neighboring block is updated.
In the cases where this happens it is still possible to save the block by adding a block below it - so there are at least ways to mitigate it.
If this would happen to a large number of blocks in a structure it could be an issue, but currently the cost outweighs the benefits.
That's absolutely fine! Thanks for the explanation!
I'm guessing that MC-241757 would be considered a value issue then? Lots of suspicious blocks are destroyed without the player doing anything.
In Bedrock Edition it is not possible to save the block by adding a block below because it drops after some random gametick which could cause losses, the report is MCPE-178020