DiEvAl

"Fix Version/s: Future Version - 1.6"
Does this mean that there will be no more snapshots until 1.6?

@Maxwell
I guess this: https://twitter.com/Dinnerbone/status/340148991469699072 😛

@Matthias the schematic you attached is a zombie spawner, but that error log mentions creepers. Are you sure it's the same spawner?

Can you attach a schematic of that spawner?

If horses shouldn't be able climb ladders, then slimes, creepers, magma cubes, ocelots, wolves, pigs, sheep, chickens, etc shouldn't be able to climb ladders either. (RIP most slime farms)

@Toraby I think it was all mobs except for squids, bats, ghasts and maybe blazes. Basically all flying mobs 😛

I looked at it in MCP. Here is what I found:
1) Entities don't have CustomName. Entities don't have CustomNameVisible.
2) Mobs have CustomName. Mobs have CustomNameVisible. Mobs both load and save them.
3) Minecarts have CustomName. Minecarts don't have CustomNameVisible. It looks like minecarts should both load and save CustomName. If there is a bug that they don't save it properly, then I just can't find it. At least not in the middle of the night 🙂

Lightning has no string ID, so you can't spawn it.

If @William Pearson is right, than mob spawners shouldn't spawn them, because mob spawners respect light levels. So Resolution should be changed to "Works As Intended"

Maybe related to MC-10587?

Does this happen in multiplayer? Do other players see your cured zombie villagers?

Can you upload a schematic of that spawner?

Does this mean that using withers for mining is a lot easier now? 😉

<sarcasm>Then let's mark all bugs that cause crashes as duplicates of each other: "It's the same bug in the sense they both cause minecraft to crash".</sarcasm>

1 fire disappears, updates fire blocks next to it, they also disappear, update blocks next to them... This repeats infinitely. This is supposed to happen. The bug is that it would take infinite time to do this, so it crashes. It'd be pretty difficult (if possible at all) to change infinite number of blocks in a finite time, and it wouldn't be ever used by sane players, so I agree with Grum.

1. Yes, this is not a feature request. But it's not a bug report either. I don't know what this is.

2. It does differentiate, repairing it would be even more expensive.

3. Mojang can comment on closed topics.

Sorry if I accidentally trolled you. I know that the issue is closed, this is exactly why I'm continuing this conversation: to decide whether it is really a bug or dinnerbone should undo this change.

If you go home, grab some sand, and put it on a fire, tell me if it burns

Dig a 2x2x1 meter hole IRL, fill it with water, and try taking infinite amount of water out of it. Or kill a dragon IRL. Minecraft is not supposed be like real life.

I think the title answers that for you, it's sand, sand isn't flammable. Walking Dead, Corpses and people are flammable, but not sand.

Pigmen are immune to fire, but they burn.

Every other entity in the game burns, why make an exception?

This argument is the only one that makes sense to me. I agree that it should burn.

@NeverCast
I know what he said. But it affects any EntityFallingSand. Usually it's sand or gravel. But not always. Since 12w26a you can use mob spawners to spawn EntityFallingSand with any block ID.

@NeverCast

If it doesn't combust in Block form, it shouldn't show fire animation in entity form.

But OP suggested that entity shouldn't burn even if block can burn. And I think this is how dinnerbone did it.