By throwing potions directly up, so that they break on your face (no wall needed), you get accurate time. Although this discovery would now classify this bug as 'works as intended', there should be a minimal radius where the potion would still be at maximum time before the time fall-off. For example, my custom potion should still last 20 minutes instead of 15 if I throw it at my feet.
My adventure map was made in 1.3.2 using the seed 31337. When generated in 1.3.2, the torches are fine. But the same seed in 1.4.4 makes the torches float.
Just make a (normal, not superflat) map with the seed 31337, and teleport to -971, 77, 229.
/tp -971 77 229
I was standing, looking straight down, throwing it directly at my feet. I wasn't on the edge of a cliff either, there was a decent amount of flat space where I was standing. Likewise, I think a whole 5 minutes is a bit extreme to be a simple time fall-off, even for a potion lasting 20 minutes.
This (http://www.minecraftwiki.net/wiki/Splash_Potions#Splash_Potions) more than likely backs up my theory.
This is probably not a bug. I believe it works as intended.
I can confirm this. It seems to happen in the vicinity of torches, usually in a vertical fashion. The 'sprite', if you will, of the flame seems to spawn at a random point near the torch, and despawns within a split second.
I'm using a PC, so this is more than likely a misbehavior within the torch coding. I am willing to bet it has something to do with the new torch behavior since the 1.4.x pre-releases.
This works as intended. The witch is a hostile mob, therefore will despawn when you venture too far away from it.
Looked at a stronghold library. It didn't seem to have floating torches, like mrheat said.
I can confirm this. In 1.4.4 I am unable to get 'The End?' on both survival AND creative.
I tried it out several times, even on a normal, naturally generated map.
By the looks of the alphabetical command names, there probably doesn't even need to be a page 4.
Interesting. This might have to do with the fixing of torch orientation in 1.4.4, but I may be wrong.
I can confirm this.
This affects 1.4.3 as well.
I can confirm that this still happens in the 1.4.5 pre-release with the bottom X symbol, but seems to have been fixed with the top X.