What I expected to happen was...
The FallingSand entity would vanish after the "Time" NBT tag ticked to 600.
What actually happened...
The entity remained even after 600 ticks. FallingSand entities spawned with "Time" over 600 also fail to disappear immediately.
How to replicate:
1. Spawn a command block
2. Input this command: summon FallingSand ~ ~1 ~ {Block:"minecraft:stone",Time:580,DropItem:0,Motion:[0.0,3.0,0.0]}
3. Activate the command block
4. The FallingSand entity spawned should fly upwards, then disappear after exactly 1 second before hitting the ground. However, it does not.
Linked issues
Comments 5
Order of tag doesn't matter. Then What you say is not correct :
"The FallingSand entity would vanish after the "Time" NBT tag ticked to 600."
If you read the wiki, it say (the wiki is right):
"When Time goes above 600, [or above 100 while the block is below Y=0], the entity is deleted."
NBT define the entity when the game is not running, and here Time is very particular : the NBT Time is a Byte type, whereas the variable time is an Integer, so when you try to "load" an entity with Time:580, it won't work properly, because here, time must be between -128 and 127, but when the game run, the variable can be outside this range
The underlying issue is MC-35127, so I'm relinking this.
Time needs to be added before block.