Thomas Clinton

I tested this once again in the latest snapshot - it hasn't been fixed yet. I haven't played Minecraft for a little while, so I only just got around to checking this. Updating the affected versions.

I think his point is that many data tags are converted to the correct data type when the command is run. I haven't personally tested other tags that use floats recently, but I don't remember having to do this for numerous other data tags. Yes, it works by inputting "f" afterwards, but many other tags don't require that you specify the data type.

Scratch that, I did some testing with drinkable potions and splash potions. I found that it is simply the result of the way splash potions calculate their area of effect.
http://minecraft.gamepedia.com/Splash_potion#Area_of_effect

At less than 22 ticks, the duration is so short, resulting in an area of effect that is so small that it's impossible to get within the potions effect range.

Which is a tad disappointing, as now there's no simple way to directly apply an effect like regeneration 6 on a player for 2 ticks to give exactly 1 heart of regeneration extremely quickly.

Well that would be a separate bug. I will work on creating a new ticket for that, though I don't know how that will turn out.

Well it doesn't work for regeneration. The result of 2 ticks of regeneration 6 is exactly one heart healing virtually instantaneously. However, the potion, instead, did not affect my health. I should have mentioned that. Also, when I used this same command with a duration of 22 ticks or more, it worked properly but didn't have the duration I wanted and, thus, did not have the desired effect. I did find a workaround, however.

I gave the player regeneration 6 using /effect, then using a scoreboard I kept track of game ticks, and after 2 ticks of regeneration it removes it. That seems to work really well.

Tested, and this is still in 1.8 pre.

Yeah, it will always result in both of the skulls displaying the same skin, even though they should display two different ones.

I seriously ask that this be reopened, as MC-52806, MC-53393, and MC-58796 address old skulls not updating to the new skin. My issue addresses the way that Dinnerbone stated they should work, and how they fail to do so when multiple skins of a single player are involved.

How is this a duplicate of MC-52806? That addresses the issue of old skulls not updating to the new skin. I'm talking about how old skulls don't display the old skin like they should!

Sigh Maybe I'll try the suggestions reddit. I don't see the logic in them having an NBT tag that is supported by all entities that does nothing to quite a large amount of them, but what you said is undoubtedly true. I think I'm just upset that they removed such a cool thing from mobs. It's not like it was a detriment to the game or anything, and that's probably what bothers me the most.

If worse comes to worse, I guess I could just have a Wither Skull or an Item ride the mob with a custom name or something like that. Though that just makes me wonder why I have to go through the trouble to do so... :/

Yea, my main problem was the lack of verification. I legitimately thought that my messages weren't sending until I personally asked the people on my server afterwards. All I really feel I need from this is some sort of notification that it was sent, since unless someone responds or there's a notification it seems as if it doesn't work.