If a gravity block (sand, gravel, or anvil) is placed directly above a corner piece of a chorus plant, it will break a few pieces of the plant, then break itself. On the other hand, if it falls onto the corner piece, it doesn't do this, and simply lands normally without breaking anything. It also doesn't break the chorus plant on any other pieces except corner pieces.
To reproduce:
1) Grow or find any chorus plant.
2) Place a block of sand, gravel, or anvil directly above a corner piece.
3) Watch what happens.
Considering the inconsistency between what pieces it affects and how it acts whether it's falling or placed directly, it seems too strange to be intended behavior?
Attachments
Comments 4
It's hard to show in a static shot, so I recorded a GIF of it and attached it. (Ignore the scoreboard display in it; it's irrelevant.) You'll notice if you drop a gravity block (anvil, sand, gravel, etc.) onto a corner-turn piece of a chorus plant from more than 1 block above, the gravity block breaks. But if you place one directly on the corner piece (in the block space 1 above it), the chorus plant breaks instead, with the gravity block stopping a seemingly random distance down the plant. This is true of all gravity blocks, but only occurs with the corner-piece or intersection plant blocks, not the straight ones. The inconsistent behavior is what makes me think this wasn't intended.
I think it is WAI: When it falls on chorus trunk as an falling entity, it breaks into an item, when it is spawned/placed on chorus, it is a block so it will break a chorus up to that place, like any other normal block placed there, after breaking chorus it will become an falling anvil entity and than it will break into an item, like before.
I understand the mechanics of why it happens, but shouldn't the gravity blocks always spawn initially as a FallingSand entity? Having it become an immediate block when placed on top of a block, but a FallingSand entity when placed elsewhere is strange and leads to this kind of inconsistent behavior.
Is this still an issue in 15w45a? If so, please explain the issue in detail and provide steps to reproduce it. Please also update the list of affected versions. Please also attach a few screenshots showcasing the issue.