Humger deplete much faster when jumping in 1.7.2 and 13w48a compared to 1.6
Video proof by Morilibus comparing 1.6 and 1.7
http://youtu.be/ouum9Z9GlpY
And yes it still affect 13w48a the same way
Some reports of this bug are marked as "work as intended"
This change has never been written in the changelogs of 1.7, so i'm sorry but something that changed ( for the worst) and it's not referenced in the changelog is a bug for me.
Futhermore this change make survival a lot more anoying, you have to take a lot more time farming food and also... eating !
Exploring is a key feature in 1.7 thanks to the new biomes but for just 1 hour of exploring you have to take at least 2 stacks of steaks with you just because the hunger start to depletes a lot more faster when the saturation is gone, it's even worst in the nether where the hunger can go down in just 10 seconds ( if you run and jump )
and last but not least, hunger can even deplete while standing still if the saturation of the food is gone, so you bassicly die while being afk...
Please consider being honest at least and state if it's a feature of 1.7 or just a bug.
Comments 6
Yes but they could at leats state that it is a feature of 1.7 and not just let people think it's a bug, but for me it is still a bug, it's normal that when the hunger start depleting, it only take less than a minute to be at zero, even while standing still !
Ok you seem to be having a different problem to me. My hunger depletes faster than normal, yes, but not as fast as your describing.
Dinnerbone resolved MC-31014 as working as intended.
The 31014 bug is full of different hunger problems. The video provided shows that if you jump in 1.7 while sprinting. It uses about 4x as much food as in 1.6. Is that "works as intended? Did they give us a sprint key for us to never use for fear of starvation? Or maybe a decimal place was off when they rewrote some of the code? I feel like this bug is being swept in with other hunger complaints regarding the use of hunger to heal.
Is losing hunger when standing still - "works as intended" as people have been experiencing that.
or all these problems being combined and overlooked as complaints on an "intended" hunger mechanic.
Can we specifically look at the problem shown in the video to ensure we are talking about the same problem. And if this is an intended change from 1.6 to 1.7 it would be nice for to be listed in the change log.
stamping 'works as intended' without further explanation about what is specifically intended makes it feel like trying to use the bug tracker is a waste of our time and we don't get the sensation that these bugs are being addressed.
Ahh! I thought I was going crazy... Never eaten so much steak in my Minecraft life. It does seem to be an intended feature... What it looks like is that the saturation value has been halved if anything.