When I summon falling sand using /summon FallingSand ~ ~ ~ {Time:60,TileID:9}
What I expected to happen was...:
When it spawned it would fall down looking like water then turn into water
What actually happened was...:
The falling sand showed up as sand and despawned
Steps to Reproduce:
1. Launch minecraft in 14w10b or 14w010c
2. summon falling sand like said above
3. watch what happens
Attachments
Comments 5
Even when I leave the ID blank it doesn't work it still spawns then despawns
I summoned it like you said /summon FallingSand ~ ~ ~ {Time:60,TileID:minecraft:water}
I'm getting actual falling sand. That's whether I use the correct numeric ID (which sometimes works, sometimes doesn't on 1.8 depending on what type of field it is) or the correct name string ("minecraft:wheat" which is ID number 59 and "minecraft:farmland" which is 60). Setblock had no problem with the same name string. I was using an updated version of my "mob spawner that spawns crops-as-falling-sand riding farmland-as-falling-sand. Normally it has a range of 64 and operates in the background if the player is within 128 blocks but for the test I changed the range to 6. Nothing but pillars of sand. Which is weirdly ironic since I tested it in a desert ("all your crops are sand and ash in this desolate place!").
Note that FallingSand uses the "TileID" field rather than the more common "id" field. Might this be the problem? I've noticed some of the non-standard id fields still demand the number rather than the name even though it's a block id situation. Also I just noticed that if you have the riding tag it refers to the next entity id field as "id" even though it's normally "EntityId". I've been exact about the capitalization of these examples of course.
It could just be a bug I am experiencing I will wait for the official 1.8 release because it could just be because of the fact that it is a snapshot
Cannot confirm.
Don't use numeric IDs, use
instead.