No hunger bar when riding a Boat or Minecart

Its something that should be there and isn't, therefore a bug.

urrrgh i am giving up on reporting bugs because i use the search function but someone always reports the bug just before me _

Please update for 1.6.2

Yeah, just noticed it myself in 1.6.2.

Since the horse update, riding minecarts, boats, and horses has,as far as I've noticed, replaced the hunger and exp bar with the horse's jump bar.

I'm not sure this is a "bug" so much as an oversight or even intentional. When horses were added, the UI for riding ALL entities changed. For example, when riding a pig, you no longer see your hunger bar either. You see the pigs health. Since boats do not have a health bar, nothing shows. But the spot is occupied by the ridden entity's health, not your hangar anymore. Bugs are consequences of broken code, not simple oversights. But it is still something that should probably be reversed.

Maybe the hunger bar could be put above the health bar, and as for armor, it could either be above the hunger bar, or overlay the health bar.

Seems a bit unfair that you can't see your hunger bar in a boat, but /can/ still starve to death. (Edit: Another query - what about poisoning and hunger effects? You might be able to contrive to empty your hunger bar, even though theoretically sitting in a minecart/boat should mean you don't starve. Admittedly, you might be able to contrive the same starvation problem while sitting on a pig or horse, which suggests to me the hunger bar should always be present, regardless of what you're riding.)

Also, it would make the UI more consistent if we /could/ see the 'health' of boats and minecarts, [and indeed if they /had/ some health, rather than the damn things disintigrating at the tiniest bump, especially boats. (I believe they are implemented internally as low health, very rapid regeneration at present). Better IMO would be very high health, no or very slow regeneration.]

NB I'm mentioning the bit in [ ] brackets as part of my reason for supporting this issue, but I appreciate the boat fragility annoyance is a separate problem.

This is a bug? I thought it was intended

Well, yes, because of the changes to hunger (healing costs hunger) you can still lose hunger (and therefor starve to death). So I guess now it would be considered a real bug.

Happens in 1.7 pre-release.

@Galaxy_2Alex

No, since the feature is working as it was created to do and is not malfunction doing to inadequate code, it is not a bug.

Because it's unnecessarily inconvenient to the player and a consequence of the developers not considering it, it is an oversight.

There is a huge difference. For one, it makes hunger shown on boats a feature request. Not a bug fox request.

Fix* I'm typing from a phone with a baby grabbing at me. Oops.

I thought I remember at one point a developer said you wouldn't lose hunger in something like a Minecart since it'd be a problem on long rides, although that was a long time ago so I'm not sure if my memory is bad.

Although that doesn't mean it should hide the hunger bar. I'm probably thinking wrong, but in any case still a problem.

You don't loose hunger, it's just pointless when there is nothing else to show.

You do not DIRECTLY lose hunger when riding any mount: a boat, minecart, pig or horse. You only lose hunger from moving when you move, not when something is moving you.

Because of this, the hunger bar was removed to display the health of horses and pigs. The hunger bar was removed from all mounts - the code is shared.

Since then, Mojang has made it so that you lose hunger when you regenerate naturally (an addition I strongly support). This has made it possible to INDIRECTLY lose hunger on a boat if you are hurt and healing naturally.

Hence it is an oversight.

You're unlikely to get hurt enough on a boat to drain enough hunger to kill you from healing. And you can just try to eat something to check of your hunger is low.

But it wouldn't hurt to add the hunger bar backs to mounts and add the mount health above it (3 lines max). Nor would it hurt to add the jump bar ABOVE the XP bar.

These are all FEATURE REQUESTS. Not bug fix reports.

>"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?

Okay, let's see... yes, this should be a good example:
If someone who hasn't got that much experience in Minecraft is riding a boat, takes damage from Skeletons and such, and after some time he is running out of Hunger Points and takes randomly damage. He has no idea what's happening, and gets confused.
Most of the people here are experienced players, but this should be a game or everyone.

Confirmed for 1.7.5, 14w08a and 14w10c

Confirmed for 14w11b

Confirmed for 14w17a

This has been intended the whole time. This is due to something new that was added in 13w17a called the "health of a mob" which occurs when you ride a pig or a horse. Additionally, due to this happening, any entity that you ride will have the health of it show up in place of the hunger bar. Due to the minecart and the boat not being a mob, no health shows up.

@Blah Yes, that's definitely the cause, but to have the hunger bar disappear in boats and minecarts with nothing taking their place is just silly, and makes it look like they missed a spot, intentional or a bug. A change resulting from another intentional change isn't necessarily intentional.

I agree that just because something was intended doesn't mean it's automatically good design. I never saw this as an accidental bug, but I have always been bothered by the mechanic nonetheless.

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

Well put. This guy gets it.

No one said it was intentional. It still isn't a bug. There is a clear difference in technical terms of the meaning. The implementation of the feature was intentional, how it was implemented was intentional, and it did not break any piece of the MineCraft engine/components when done.

However, related features were detracted from. This qualifies as a design "oversight", not a "bug".

Which means this belongs in a Suggestions section, not a Bug Report section.

@Sen In that case, then there are a lot of bugs that shouldn't have been "fixed," but were, perhaps the first being "Squids can breathe air."

Uh, there are quite a few reports on this site that are the result of oversight and not bugs in the strictest sense. If design oversight confuses, frustrates, or misdirects the user, then how is that not a "bug" as most people use the term? It's an error of logic (as opposed to syntax). Sure it's a little more broad than "this logical error physically broke something", but how does that make the grievance invalid?

Just look at MCL-1049, the largest launcher issue. It was oversight that caused it, not a bug according to your definition.

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.

I know the exact reason why, the game thinks you are riding a mob that has specific health. That means a mob like horses, cows, pigs, skeletons, creepers, zombies, endermen, and many more. Boats and minecarts. The game can't render the boat's or minecart's health because they have a different type of health. Yes, they are mobs, (although some wouldn't agree, any entity with health is a mob.) Boats and minecarts have health that is affected by the tool(s) you use to break them. Minecarts break best with a sword or pickaxe, as boats break best with an sword or axe. Other mobs specific health is used differently. There's only one exception: Axes and baby zombies, as far as I know, baby zombies die faster with axes than swords.
Edit: I am not 100% sure, as for I can't really confirm this, but I am pretty sure.

Confirmed for 1.8.

Confirmed for 1.8.1-pre1.

confirmed for 1.8.1 pre-3

Still in 1.8.1-pre4.

No hunger bar when riding in a minecart.

MC-84301 confirms the issue for 15w31c.

It's not a bug. It's a weird feature. But still would be cool to remove it.

Still an issue in 15w43b

Confirmed for

• 15w51b

This affects and will affect all entities that the player can ride. A temporary fix would be to change the func_180477_d(ScaledResolution p_180477_1_) method of the net.minecraft.client.gui.GuiIngame class (MCP 1.8 names) to only do not show the food bar when a player is riding an entity of the class net.minecraft.entity.EntityLivingBase. This would however not fix this for horses and pigs.

private void func_180477_d(ScaledResolution p_180477_1_)
{
	if (this.mc.func_175606_aa() instanceof EntityPlayer)
	{
		//...
		
		Entity var34 = var2.ridingEntity;
		int var36;

		// Replaced this
		//if (var34 == null)
		if (!(var34 instanceof EntityLivingBase))
		{
			//...
		}
		// Replaced this
		//else if (var34 instanceof EntityLivingBase)
		else
		{
			//...
		}
		
		//...
	}
}

Can confirm this bug for release 1.9

Can confirm for 1.9.2

Still in 1.9.4