Hunger level

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.

We do not have enough information to find the cause of this issue.
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/guides/finding-minecraft-data-folder]) here.

Once attached, the report will be reopened automatically.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

Crash attached. Hunger seems to drop only when sprinting but never when digging.

Workflow says it's postponed... Maybe you guys don't realize but I can't really play and enjoy the game the way I want because I can't set level of difficulty in a game nor hunger doesn't work. I have barely 15 days to get a refund so please let me know what are you going to do about this obvious game breaking bug which in your opinion must be so insignificant that has been postponed.... thanks...

Nothing is postponed, this bug will be looked into as soon as the developers see the ticket.

Fixing this issue will probably take more than 15 days though, as some developers are currently on vacation as far as I know.

But you can still enjoy the game without this bug being fixed; it doesn't prevent you from playing, does it? In fact, for me hunger and difficulty behave just like they should.

By the way, if you want to make the developer's life easier (and make the bug fixing process faster), maybe consider adding some screenshots and/or videos and an exact description of how this bug can be reproduced.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki

Well,I can't play on hard difficulty because after saving the game it keeps changing to normal, the same with peaceful mode, so yes, sure I could play assuming I would love to play normal mode with hunger not dropping down, what to be honest is mega boring.
No point of screenshots since this bug is always present on my computer. It must be this specific configuration of software/hardware/drivers which triggers it. You want description, here it goes: double clicking minecraft icon on my pulpit, then clicking on single player save and here we go..... and seriously, if screenshots or detailed description would be any help here I would attach it already...

It must be this specific configuration of software/hardware/drivers which triggers it.

You didn't even say what your software/hardware/drivers are, except for some basic information which already is in the crash report.

Can you attach a game log file from [minecraft/logs/latest.log|http://hopper.minecraft.net/help/guides/finding-minecraft-data-folder], maybe there is some error message which could help understanding what causes this issue.

Also, just to make sure that I understood your report correctly: When you quit the game, your hunger, difficulty, and other things are reset? Is that what your problem is? Is there something else which is reset upon quitting and re-entering the world (e.g. world time, inventory, etc)?

By saying "software/hardware/drivers" I meant all of them, the whole unique configuration of the computer which I am not going to post here.
I attached last log.
and to clarify: When setting to hard or peaceful level of difficulty after saving and restarting the game it comes back to normal level. Hunger level doesn't drop when working, digging,etc... but works when sprinting only.

There we have it. The important part is:

java.io.IOException: Stream Closed
	at java.io.RandomAccessFile.seek0(Native Method)
	at java.io.RandomAccessFile.seek(RandomAccessFile.java:540)
	at ayj.a(SourceFile:323)
	at ayj.a(SourceFile:263)
	at ayj$a.close(SourceFile:244)
	at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:241)
	at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
	at java.io.FilterOutputStream.close(FilterOutputStream.java:159)
	at aye.b(SourceFile:160)
	at aye.a(SourceFile:145)
	at bgx.c(SourceFile:37)
	at bgx.run(SourceFile:30)
	at java.lang.Thread.run(Thread.java:745)

Thanks!

Turns out this is actually a years old bug, MC-10976. A fix has been attempted twice, but it's still there.

I've resolved your ticket as a duplicate of that report, as we don't want to have multiple tickets about the same issue and MC-10976 also includes a proposed fix which makes resolving this bug even easier. Maybe this bug will be fixed in 1.13.

Nice,what makes you thinking that it will be fixed now if it wasn't in past 4 years...?.... devs were on holiday last 4 years I guess? Honestly, no comment.. But thank you for showing me how this company care about fixing their product 🙂 bye.