Roachy

ThePhysician2000 has the right of it. As shown in this latest attachment (using 1.8), the oak stairs were placed in a straight row, and then the stone stairs placed to complete the rings. Then the spruce stairs were placed in rows on each side of the ring.

The spruce stairs clearly follow the behavior described by ThePhysician2000.

An unfortunate but inevitable confusing effect of the way stairs transform, but most definitely not a bug.

Ah, I see what you mean now, and I think this makes sense as to the inconsistencies in my images. When I made the multiple circles of stairs, I placed down the outer lines of stairs the same way, and I placed down the inner ring of stairs using the same method, but not probably always starting facing the same direction. I will test this again when I can and post back.

To clarify for myself and any others reading, the non-obvious behavior here is that a corner stair can exist in one of two orientations, depending on which direction it was originally placed. It will look identical in either orientation, however this "invisible" orientation will dictate which transformation style certain adjacent stairs will take on.

I'm not sure I entirely follow you, but regardless, I don't see how that explains the inconsistency. Why would some stairs turn into a corner while others, having been placed the same exact way in another location, stay straight. Take a close look at the screenshot titled stair_behavior2.png

During these tests I even made sure to face in the same directions while placing stairs (or as best I could without using command blocks to orient the player).

Still an issue in 1.8.

Still an issue in 1.8.

Still an issue in 14w32d. See attached SS.

Not that it's relevant to this issue, but I came across a funny side effect that emphasizes this issue while playing with the Twilight Forest mod. In this mod there exists a hostile mob, a giant pinching beetle of sorts. It charges you, grabs you (read: forcibly makes you ride it) and walks around with you and causes damage over time until you kill it.

In this case, because you are riding an entity, your health doesn't show up, even though the very thing you are riding inherently causes damage to you, and you would need to know that information.

Obviously mod-based arguments are not valid here, but imagine if Mojang wanted to code in a similar enemy or mechanic. They would change this behavior real quick.

Just to give a realistic example off the top of my head, say horses could be set on fire by zombies like players can. That fire could damage both the horse and the player riding it. Too bad you can only view the health of one or the other :[ For that matter it might even be possible already for both a horse and a riding player to take fire damage.

> "A change resulting from another intentional change isn't necessarily intentional."

Well put. This guy gets it.

Still exists in 14w11b. See latest screenshot.

Based on the evidence, it's unlikely that anything short of a complete overhaul of the clientside entity rendering code will fix this bug.

I'm experiencing this in 1.7.4 with a beacon in the nether, which has nothing but bedrock above it.

I've seen this bug numerous times, but just today it happened even after accessing a tile entity screen, which I've never seen before.

I ate a steak, then immediately accessed an anvil without switching away from the food, and after the anvil screen came up the burp noise happened and another food was consumed. As mentioned before, switching away from the food immediately after eating will prevent this bug, but apparently accessing an anvil screen will not. Just thought I'd mention it.

I agree with David Truog. I'm currently in 1.7.4 clearing a large area of the nether with Efficiency V shovels and pickaxes. This bug is happening to me a lot, and is exacerbated by switching between the shovel and pick (when I switch from mining soulsand to netherrack and vice versa).

When it happens the block looks to disappear client side, but when you walk into its space it jerks you around like your client is trying to move you forward but the server keeps resetting your position to be outside the block. The easy way to fix it (without relogging) is to attempt to place a block in the offending space. The block you place will not be placed, but the block originally in the space will reappear and the block-placing noise will not occur. That's the callsign of this bug. I've seen it recorded in several videos of youtubers I watch as well, mostly Etho and Docm77.

>"You're unlikely to get hurt enough on a boat to drain enough hunger to kill you from healing."

There are are several reasons you could be significantly hurt riding a boat or minecart, including being attacked by mobs, suffocation, fall damage, lava, potion effects, etc.

I have to admit that this is in fact an oversight and not a bug, but it amounts to a pretty bad UI inconsistency. The fact that you're unlikely to lose hunger in these situations is irrelevant to the fact that a critical UI element is missing.

Let's pretend sitting in a minecart made you invulnerable. Would you be cool with not seeing your health while in a minecart? When you're not gaining or losing XP your XP level will always be the same. Should that be hidden when you're not at an enchanting table?

Alrighty.

Noticed a stone brick slab stuck like this, seen in newly attached image.

I loaded up a superflat world made of 1 layer of cobble slabs, and randomly placed slabs everywhere and filled my inventory with them and cannot reproduce the problem. I get the feeling that this may have something to do with the much higher load my single player world is under, what with all the mobs and tile entities.

The latest driver for my card is currently 332.21. I was already running that version, however I've redownloaded and reinstalled it, choosing the clean installation option. The problem still persists.

IIRC, 332.21 is a recent release, and I'm pretty sure I was having this problem on the last driver version as well, which was 331.something.

Crash report attached.

That's kind of my point. All of these are symptoms of the same issue, which you stated. The one I posted simply has more votes and more information.