Moderator Note
Downgrading from newer versions to older versions may have undesired behavior, please back up your worlds before testing snapshots.
Upgrading to a snapshot may also corrupt worlds, please back up your world before testing.
Enabling Development Builds Warning in the Launcher:
Are you sure you want to enable development builds?
They are not guaranteed to be stable and may corrupt your world.
You are advised to run this in a seperate directory or run regular backups.
Downgrading is not, was never and will never be officially supported!
Definition of downgrading: Going from a version with a higher number (example: 1.12.2) to a version with a lower number (example: 1.11)
@unknown in https://twitter.com/jeb_/status/507193706781614080
... Don't open a 1.8 world in 1.7 unless you have a backup ...
https://twitter.com/jeb_/status/507198150474727424
Since you ask: 1.7 doesn't know how to handle 1.8 saves, but tries its best not to crash. This means it ignores data, which is lost forever.
14w03a came up today and I noticed the transparancy bug with glass panes, so I switched back to 14w02c to verify that was working correctly there. All items everywhere vanished. Everything in my inventory, equipped gear, even everything in chests and furnaces are gone. Switching back to 14w03a did not bring it back.
Related issues
is duplicated by
relates to
Attachments
Comments


Never. Switch. To. Older. Version.

You have got to be kidding me. Where does it say this? If this is so, then the game shouldn't let you open it in an older version, or should warn you and make a backup copy.

You were warned...
Enabling Development Builds in the Launcher:
Are you sure you want to enable development builds?
They are not guaranteed to be stable and may corrupt your world.
You are advised to run this in a seperate directory or run regular backups.

That says that the snapshot may corrupt your world, not that you should never switch to an older version.

Okay, don't take that too personal, but:
What part of "may corrupt your world" and "run regular backups" isn't clear to you?

It is a snapshot for now... unless the bug is fixed, then it won't be a snapshot when 1.8 is released.
"It's a beta, expect bugs" is not the same as "It is perfectly normal to crash and eat your hard drive, don't bother reporting it as a bug so it can get fixed or anything".

I agree with the Mods. You kind of have to accept things like this when using a beta. You just accept it and move on and remember not to repeat the mistake.
I'll just say that when it happened to me I only lost everything near where I was when I switched back including my inventory, all chests and my Nether chest which I didn't have with me. My main house which was a long way away still had all my stuff in the chests there.

... https://mojang.com/2014/01/minecraft-snapshot-14w02a/ says:
As this is the very first snapshot of 1.8, do remember to backup your worlds before trying it!

Again, when this happens when you downgrade from 1.8 to 1.7, neither of which are beta, it will NOT be acceptable. I don't expect you to wave a magic wand and fix my broken world, but it is a bug that needs to be fixed and saying otherwise is stupid.

I'm almost certain that downgrading has never been supported. Also, rolling back past 1.2 will loose your whole world.

@Phillip Susi Do you realize 1.8 isn't released yet? And that snapshots are beta testing versions?

Of course I do... why is this so hard for you people to grok? It is a beta now, which is why we test and file bug reports so that they can get fixed before it is released as 1.8. Saying that bugs are expected in a beta and closing the report so it won't be fixed is counter-productive.

Admittedly it shouldn't have been closed for that reason, however downgrading is not supported.

I'll just put my two cents in as to WHY downgrading is a bad idea, and why it isn't a bug that if you go back to a previous version, items are missing.
Updates may change the data format on disk as to how the world is stored - including items, blocks, etc. That is perfectly fine to do in an upgrade, providing it retains compatibility with older worlds. It is not, however, possible (or needed) to guarantee compatibility with the reverse. It would be unrealistic to never change the data format storage purely so that the first Minecraft alpha could still read the worlds. Granted, this is 1.8 to 1.7 - not a big jump as in the circumstance I mentioned. However the same principle still applies.

If the format has changed, then minecraft should detect that the file is a newer format, and refuse to load it, not open it, corrupt it, and save it back.

Yes, however that is technically a feature request 🙂

Luckily I noticed that before I went into a world with lots of containers!
Helpful note: Play on a version that you usually play on! It will most likely prevent you from downgrading versions (or just wait until a stable version comes out.)

I'm wondering why you downgraded your world in the first place, what's the point?

To test for bugs of course. I wanted to make sure that it wasn't my video drivers or something that caused the glass bug, and maybe play without that annoying bug until it got fixed.

Again, says that the current version may corrupt your world ( which is understandable, bugs happen ), not that downgrading versions can ( which is entirely preventable; it should be able to see that the format changed and realize it doesn't support the new version ). It also won't apply when 1.8 comes out and downgrading to 1.7, neither of which are development version, will corrupt your world.

I wanted to downgrade it so that I can play on the 1.7 servers. I never went on my Singleplayer maps, and when I upgrade versions, I noticed that all my items are there!

My world is in 14w08a and I have a backup of it in 14w08a. obviously i cannot downgrade to 1.7.5. but when 1.8 does come out can i upgrade to it without losing all of my items?

John Hinson, upgrading to 1.8 won't be a problem.

are you sure upgrading to 1.8 wont be a problem

If you're in doubt, make a backup before upgrading.

You should update the moderator note so that it says "and 1.7.7" as well.

Agreed. Wait until the full update comes out to update a world.
If you should, create a new folder to store snapshot-testing worlds in.
IF you forgot to backup, You can restore to an older version.

That won't help if this bug isn't fixed by then, and it looks like it won't be.

@Phillip Susi Downgrading isn't supported

I believe the moderator note should be updated so it includes 1.7.10.

Done, thanks.

No problem!

so does this mean I have to start from punching wood again? and all things are gone permanently? I picked a bad day to start using snapshots.

Is there any way to get my items back?

Sadly, no.

I have had this happen to me once. I played a creation map on 1.7.2 (because of a computer incompatibility) when the map was 1.8 snapshot (I didn't notice that little piece of info on the map download). Everything worked just fine for about a month. I logged in one day in Fullscreen mode (I usually play it at the little tiny default window size). All the signs said "null '(Text)' null null". I thought that was just a temporary glitch and relogged. The signs were still messed up. I was in the process of trying to fix them when I noticed my inventory was empty. I figured "Oh well, maybe I was a scatterbrain and put my stuff in a chest." I go to a chest and open it. A chest that I KNOW I had stuff in was completely empty. All jukeboxes were empty, too. (I like to listen to Cat a lot, so I usually keep one near me.) I also noticed all the paintings had fallen off the walls. I picked them up and realized either:
a) Someone hacked me (has happened before), or
b) Something went wrong.
There was nothing in the launcher indicating something went wrong. Also, I had this weird thing where I could craft slime blocks in 1.7.2 in that world. I thought they had already existed until I saw the 1.8 release log. Could that have corrupted a world? I reset the map just fine (I usually store all my maps in a folder) to see if it was my computer (my computer's very old). It wasn't. The game worked just fine. It was very annoying having to make full diamond armor again. However, it hasn't happened to me after that and I haven't been able to replicate the error.
[^yJlBhQ9[1].png]