Worlds not saving upon exit (single player)

This looks like a problem with your install and isn't really a bug. Try looking here for help. http://www.minecraftforum.net/forum/151-unmodified-minecraft-client-support/

Thank you sterling 🙂 My Minecraft does seem to be working fine on previous versions. Apparently using compatibility mode fixes it.

I'm pointing a few bugs back here as duplicates including ones where items are being lost on logging out as there seems to be a global issue of worlds not saving correctly in singleplayer for some people.

This video was linked in a duplicate ticket: http://www.youtube.com/watch?v=nPJCLgadl8o

It has happened to me in 1.4.2. I don't remember if the "saving" dialog was shown, but when i reloaded the world, about 30min of building was gone. I have no mods.

I am not entirely sure it is an install problem, I have reinstalled many times and that bug continues to happen. I believe, as I stated in MC-593, that this is a problem with the fact that the world no longer saves as often.

I have this same problem. I have tried to re-install multiple times and even tried creating new worlds but it never works. It is making it impossible to play Minecraft since I never know what will save and what will not.

I am also experiencing this issue since the 1.4.2 live release on previously generated and newly generated worlds.

The behaviour is duplicated under both java 6.0 and the most recent Java 7 update 9 release. (tried updating, made no difference).

The behaviour is duplicated wether minecraft is running in the standalone launcher or the applet on minecraft.net/play.

OS : WinXP
CPU: Singlecore Athlon FX64
JRE: V7 Update 9 (build 1.7.0_09-b05)
Browser : Firefox 16.0.2

Notable behaviour:

The saved game appears to act as if there are two conflicting versions of the saved block state, which are persisted or loaded at random, depending on some unknown factor.

Nothing I've tried so far appears to give stable saved results, however once a set of blocks changes in "both" versions, the loaded results are consistent.

The versions don't appear to "toggle" between consecutive loads, but seem to depend on some random factor.

More info to follow as I go...

the issue with the chest i did hade once while using 1.4.2. now, with 1.4.4, it didn't came up since (win 7 32 bit). i'll test it and report here/edit this coment, if necessary.

Update :

Note : it was possible to get reasonably reliable persistence behaviour under 1.4.2 hitting ESC, waiting 30 sec, clicking save, waiting 30 sec and going back into the game. However the reliability of this was only about 75%.

Under the just-released version 1.4.4 the behaviour is still occasionally reproducible, especially when saving the diggings of just a few blocks. The game save behaviour is now about 90% reliable without waiting for the "silent save" to complete.

Clearly whatever it was, it got improved by the 1.4.4 release, but the underlying cause is still lurking about.

The "Saving game..." message is still conspicuously absent.

Fixed? No.

More reliable? Yes.

Please keep this issue on the front burner 😉

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Hey tails. Sorry for the lack of updates.

The current release version of Minecraft, 1.4.7, no longer has this issue. I think it was actually resolved by a prior version, possibly 1.4.5.

I can confirm that it is definitely resolved under 1.4.7, however, and my world saves appear to persist almost immediately 😉

Just try not to loose the fix in a stray code branch 😉

The bug seems to fix itself when playing minecraft in Win95 compatability mode

HEY! I'm playing on 1.5.2 and I've got this problem.

Why cloning when this is still open?

Anyone who's experiencing this, please start Minecraft by

minecraft.bat

java -Xmx1g -Xms512M -cp minecraft.exe net.minecraft.LauncherFrame 1> log.txt 2> error.txt

and attach log.txt and error.txt after the error occured.

It does not work

I have the latest full version of Minecraft installed (1.5.2), without snapshots or mods (single player mode). The descripted error already appears. The world status, including the recently added items in a chest inventory, is saved incomplete. Waiting a few minutes before leaving the game to the main menu seems to increase the chance of correct saving. But it is not reliable. Please, create a boringly normal, but working save button, even though the game is somewhat less novel.

Once again me. Starting the proposed batch file, minecraft does not start. error.txt then contains the message (in german): "could'nt find or load main class net.minecraft.LauncherFrame". log.txt is empty.
Starting normal works fine. Suggestions?

Also in 1.6 !!!

I've received this issue in the 1.6.1 release, although it may be by another cause. I use Windows Vista.

Having this issue in 1.6.2. Also, it won't save if I close minecraft by clicking the "x" in the top-right corner.

Confirmed in 1.6.2 !

Cannot reproduce in the latest version of minecraft

Did you use XP? I can still reproduce this 😞 The "saving level" screen never shows up.

My computer doesn't show a saving level screen, however saves it. I will reopen to 1.6.2.

Mine doesn't save it however.

this happens to me on windows vista as well

THis happens to me on Windows XP as well

I have evidence of this bug in snapshots. If I can attach these, just ask. (i.e. version 1.6.4)

Edit:
Upon reviewing the snapshots, they do not display much detail of the bug (however a video would). So these snapshots would be of little use.

It doesn't save the last couple seconds. If you place 3-4 blocks and leave the game and then come back they wont be there.

Confirmed in 1.7.1

I thought it was fixed for me atleast in 1.7.2 and 1.7.1, but then yesterday I logged on singleplayer and a sign was missing. It was the last thing I had placed in a previous session. This happened in 1.7.4, so I don't know whether 1.7.2 was fixed or not.

I think the reason for this is the local server hasn't finished shutting down when you get to the title screen. since about 1.3, when quitting a world, i'll run task manager and wait till the cpu usage goes down before doing anything on the title screen.

confirmed in 1.7.4 and all later snapshots, extremely annoying and needs to be fixed.

I am getting this in version 1.7.5

I was getting this in the current snapshot- 14w21b. At first I thought it was an entity problem- I was just dropping things and reclogging, wanting to use MCEDIT. (maybe my old version of MCEDIT triggered it?) Then my blocks wouldn't save progress either, but my inventory would.

After finding people with similar issues on a forum, I deleted everything from ".minecraft" except my saves, stopped using MCEDIT, and I enter & exit the nether right before saving and quitting now. It saves my progress again, but I don't know which, if any, of my actions resolved it. I hope this helps you guys isolate the issue, but I realize I'm being rather vague.

Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I haven't run minecraft recently much, so I feel I can't effectively answer the above. However what I have noticed is items disappear when you login a 1.8 world with a 1.7 profile loaded. This is probably because the new formats which may not be compatible.

From searches I have found that the items are unreplacable. So for other users; take this as a warning.

That is MC-45009. Downgrading is not, was never and will never be officially supported.

I first started experiencing this in 1.8.3. Thought I was loosing whats left of my mind as was usually minor tasks lost that I thought I did but couldn't be sure. Then some changes I made to a redstone contraption including changing item counts in some hopper and droppers didn't save. I clearly remember doing the math on them item counts thrice. This world has not been touched with an external editor and was never downgraded.

@@unknown: Before After having 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/finding-minecraft-data-folder]) here.

Please attach the complete output of the "Game Output (Your Minecraft name) " which can be found on the fourth tab of the launcher.

If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open".

That can be a memory issue, see e.g. MC-78028

It would be rather difficult to force a crash on a world I've already closed. The problem being that changes from the last time I played were not saved even though it appeared to exit normally. As for memory settings, I have been tinkering with those recently, yet, it occurred when using the default settings as well. At this point I've already deleted everything except my saves and launcher profiles and am keeping an eye on things to see if it occurs again.

While this is for the multiplayer server I think it might be related. When shutting down a server I've noticed an error a couple of times with no corresponding crash-report generated. Once in the middle of saving the players, and once in the middle of saving chunks.

2015-02-25 17:32:41,040 ERROR Attempted to append to non-started appender ServerGuiConsole
Exception in thread "Server Shutdown Thread" org.apache.logging.log4j.core.appender.AppenderLoggingException: Attempted to append to
non-started appender ServerGuiConsole
at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:425)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:406)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:367)
at org.apache.logging.log4j.core.Logger.log(Logger.java:110)
at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1011)
at net.minecraft.server.MinecraftServer.s(SourceFile:379)
at net.minecraft.server.MinecraftServer$2.run(SourceFile:713)

@@unknown: You're right. Please force the crash at any time.

Them two roughly approximate the conditions under which I've noticed this issue.

Sorry was about to delete the email when noticed you wanted the game output.

@@unknown: Nothing to see in the reports except that your graphics card drivers are one version behind. Current one: http://www.geforce.com/drivers/results/81877

Hmm, let me get this straight:
A: does your inventory save but not the world? My answer: Yes
B: does this occur on Windows 8? (Yes)
C: does this always occur or just sometimes (Sometimes)
D: does it occur in just one world or more than one (at least 2)
E: do all the block you placed since you logged in disappear or just the last 5-minutes or so? (only the last ones)
F: how do you fix the problem? (idk)
G: what 1.8.5-compatible versions of Minecraft fix this issue? (idk)

For these conditions: confirmed.

I can't reproduce this in 1.10 and never even heard about this. I'm on Windows 7, also played on Ubuntu and even Boardwalk on Android (port of PC minecraft to mobile), but it never happened, even with lag, freezes, crashes, etc. Also when I set the autosave time in Optifine to 30 minutes and the game crashed, it didn't happen (but I know that that doesn't count here). Does anyone have tips on how to reproduce this?
I have 7 of my 8GB RAM allocated to MC, but it also worked before and even on a sh*tty school computer (worse than phone) while hosting a server.

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.

Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. It will be reopened as soon as the requested information has been delivered.

Encountering the same issue on versions past snapshot 20w22a for my single player world. None of the versions after that snapshot seem to allow me world to save chunks.

Do you have reproduction steps for this? What's your specs, launcher settings, etc. Do you have free disk space and is the folder writeable? And hard disk faults, problems in other programs, etc.?

I am now having a very very similar issue right now in 1.16.5