I just updated from 1.6.2 to 1.7.4 and went back to working on a world i've put a lot of time into. I backed it up by making a zip file of the save folder under "C:\Users\David\AppData\Roaming\.minecraft\saves", then opened it in 1.7.4 - it worked fine, so I made another zip file backup, then I wandered around a bit.
A creeper destroyed part of a structure I couldn't be bothered rebuilding, so I deleted the save folder, unzipped the 1.7.4 backup, and went back to reopen it. (This is something that I've done a million times before updating to 1.7.4 without any issue - the unzipped folder used to show up on the saved games screen without any trouble.)
It doesn't show up in the list of singleplayer games. Every other save folder, including ones from years ago (like 1.3) show up, but not the folderthat I just newly unzipped.
I've never seen Minecraft behave like that before. Does anyone know what the problem is?
I just updated from 1.6.2 to 1.7.4 and went back to working on a world i've put a lot of time into. I backed it up by making a zip file of the save folder under "C:\Users\David\AppData\Roaming\.minecraft\saves", then opened it in 1.7.4 - it worked fine, so I made another zip file backup, then I wandered around a bit.
A creeper destroyed part of a structure I couldn't be bothered rebuilding, so I deleted the save folder, unzipped the 1.7.4 backup, and went back to reopen it. (This is something that I've done a million times before updating to 1.7.4 without any issue - the unzipped folder used to show up on the saved games screen without any trouble.)
It doesn't show up in the list of singleplayer games. Every other save folder, including ones from years ago (like 1.3) show up, but not the folderthat I just newly unzipped.
I've never seen Minecraft behave like that before. Does anyone know what the problem is?
I really don't want to lose this save!
A reason to find desert wells, make hasty crossings, & build stone firepits to set wood alight in the snow.