Ethan Wanless

Yes. My apologies.

Still an issue in 1.14.3

Confirmed for 1.8.7

Can confirm. I have created a video which demonstrates this:

http://youtu.be/HagDuZicr_A

For iconcrack_ and blockdust_, you need to put the id of a block after the underscore. I have used both of those particles and am sure that they both exist. I have never tried blockcrack_ but I'm sure the same rule applies to it when you use it if it does in fact exist.

With this bug, the chunks never render until you force them to reload (relogging, pressing f3+A). With MC-129, the description says they will remain unloaded until you get very close to them. MC-129 has been in the game for a very long time, and I have witnessed it as well as this bug in the same version.

I did a test and found that only mobs named with a name tag will remain after going into spectator mode. I'm guessing this is a bug, but I'm not sure if it's only supposed to be mobs with a name tag that don't despawn or if it's that any named mob is not supposed to despawn. Here's a link with screenshots of the test I did:

http://imgur.com/a/mgLKQ

Now that I think about it, there is no name tag in your inventory. Did you name the spawn eggs and spawn one in instead of naming it with a name tag? If so, that could be the reason why we're getting different results.

I saw the screenshots. I performed a similar test and got different results. I named a creeper with a nametag in 14w19a and surrounded it by a bunch of other unnamed creepers. Then I went in to spectator mode, and the named creeper didn't despawn, but the unnamed ones did.

Fixed in 14w19a.

Really? One day of annoying sounds and skin changes as a joke, and you want to stop playing forever? Even though it's just an April Fool's joke and will go right back to normal the next day?

Opening new tickets about how leaves must be fixed will do nothing, as there is nothing to be 'fixed.' The ticket will get closed as 'invalid' or 'works as intended.' If you want it to be fixed, then make a video about it on YouTube, tweet it to someone at Mojang, let people know your opinion on it. If enough people voice their opinion, Mojang will likely change it. They've listened to the community before, like when Zombie Pigmen and Iron Golems were changed so that they couldn't drop gold or iron unless directly killed by the player. One snapshot later, that feature was removed because it was clear that the majority of the community wasn't happy with the change.

@Butt Man

Exactly. I can understand why they made glowstone/tnt/redstone blocks suffocate you. There's really no reason for them not to. But leaves? I always thought they were transparent on purpose. It makes sense for leaves to be transparent because in real life you can pretty much just push them out of your way.

People may already understand this, but for anyone who doesn't, the reason everything has a shadow is because the player is sitting slightly lower in the minecart than they should be. Because of this, they are sitting slightly inside the ground, which causes everything in the players view to appear darker, as if they were in the shade. You'll notice a similar (but not as dramatic) effect by walking under a tree.

From what I can see in the pictures, it looks like what's happening is that the minecart's going too fast at that little circle in the top left of the 3rd picture, causing it to derail on one of the corners. It then flies onto the track it was just on, and the cycle repeats over and over. If that is what's happening, then it's not a bug, it's just the way minecarts work in the newest snapshot. You need to make sure the minecart isn't going too fast on corners or it will derail.

Even if the horse issue is going to be fixed, there are still gameplay mechanics that this "fix" interferes with. For example, if you bonemeal an oak sapling too close, and the tree generates with leaves low enough to the ground, you get caught in the leaves and suffocate.

Does anyone know if this is still an issue in the latest snapshot?

This has been in the game for a while I believe. Sometimes, when you generate a world, it gets corrupted like that. It's happened to me a few times.

That actually makes a lot of sense. I am on a laptop and usually only run into one or two hostile mobs every night, but I watch people on YouTube with powerful computers and nothing seems to be going wrong for them. However, I tend to keep my render distance very low. I need to test this out.

Oh, I see what I did. I feel stupid. I forgot to add [score_name_min] to them. I guess it's just been a while since I used these. Sorry about all this.