[MC-263062] 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 7

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

is duplicated by 2

MC-267831 Trail ruins generate with airblocks Resolved

MC-295413 Trail ruins when spawning, air may spawn at the bottom of the suspicious gravel Resolved

relates to 1

MC-241757 Sand and gravel within ocean ruins often convert into falling blocks when the world generates, causing performance drops and suspicious blocks to be destroyed Reopened

Attachments

MC-263062.mp4

Comments 4

billysjoberg 2023-06-08T14:54:07Z

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.

Avoma 2023-06-08T14:58:09Z

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.

Timer RP 2024-01-06T23:27:13Z

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

Johnathon Acosta 2025-05-19T22:23:49Z

I think this being reopened should be considered, as these voids can span 2 or even 3 blocks, making it impossible to save it all. I’ve even seen where two suspicious gravel were above one void. Only thing is I could see it being like irl where there will always be sacrifice.