minecraft:falling_block will render almost every block in the game using their assigned block geometry, such that the block is visible during its falling animation. However, fluids (i.e. minecraft:water and minecraft:lava) defy this behaviour, instead remaining entirely invisible throughout their time as an entity.
This behaviour began in 1.8 snapshot 14w25a and has persisted until the latest version (26.3 at time of writing). In release 1.7.10 and earlier, the correct behaviour can be seen.
To reproduce:
run this command: /summon falling_block ^ ^2 ^5 {BlockState:{id:"minecraft:water"},Time:1b}
observe what happens
Expected results: a cube of water would appear in midair, start falling, and turn into water when it touches the ground
Actual results: an entity is created (as can be confirmed by the presence of a shadow, and a hitbox if debug rendering is enabled), however this entity is completely invisible. It correctly places a fluid when touching the ground, however.
The following commands can be used to reproduce this in 1.7.10 (which correctly shows the entity) and 1.8 (which incorrectly does not): /summon FallingSand ~ ~ ~ {Time:1b,TileID:8}
To fix this, a similar approach as used for MC-193336 and MC-195237 could be used: a special_model_type for items which uses the fluid render could be used, and falling blocks, upon detecting no valid block model renderer to use, would instead use this as a fallback.
Environment
Windows 8 64-bit, Java 7
Linked issues
is duplicated by 11
MC-1300
Falling sand entities with water or lava block ids do not render properly
Resolved
MC-60440
Falling Sand Entities containing water or lava do not render until landing
Resolved
MC-68509
Lava Falling Block dont show/render
Resolved
MC-71268
Falling sand entities with water or lava block ids do not render properly
Resolved
MC-75103
Some 'Fallingsand' does not render
Resolved
Attachments
Comments 14
I think this issue was wrongly mark W.A.I because the falling sand entity is suppose to be rendered as the TileID it was assigned, this problem has never occurred before, just until now. As far as i know this problem is confirmed for 14w30c, 14w31a, 14w32a,b,c,and d.
I reported the same issue here MC-60440, I discovered this in 14w27a/b. I agree with you that I fail to see how this is 'Working as intended'. In fact I was genuinely confused when I saw that it had been marked as 'Working as intended'. An invisible entity that has a shadow as it flies through the air and then creates a block when it lands sure sounds like a bug to me.
As said previously, this is definitely not Working As Intended. Please reopen until it's ACTUALLY fixed, thanks?
Tristan Croizer, if you didn't see all entries against this issue, someone from Mojang actually decided to resolve this as intended:
[Mojang] Mog (Ryan Holtz) made changes - 30/Jul/14 3:51 PM
Resolution Works As Intended [ 6 ]
Status Open [ 1 ] Resolved [ 5 ]
So no, I don't think anyone else is going to contradict this and request to reopen it.
"Resolved" does not mean "Fixed". It means that a decision has been made. In this case, that decision is "Works As Intended". These blocks will not be visible while falling, and it is unlikely that this will change in the future.
It’s been quite a while since this ticket’s July 2014 closing, and I think that the much more recent fixes for MC-193336, MC-195237, MC-199975 and MC-256649 set a fair precedent that certain blocks not rendering in entity format indeed is no longer considered intentional game design. Also consider that the two blocks mentioned in this ticket rendered just fine as falling block entities in the preceding release version (1.7).
Could the closure of this ticket on the basis of it working as designed be reconsidered in a more modern light? As is mentioned above, I have reason to believe this is no longer the case.
Confirmed for 14w30c but I think it is better then when the old report gets reopened again