1.9 corrupted my world. I have a youtube account, was doing a series. When I started Ep. 2 I shifted my version to 1.9, logged on and looked in my chest. Nothing there. I looked in my Inventory. Nothing there either. I went to complain on Mojang. Could not log on. Think I should cheat the stuff back in?
What version were you playing before you "shifted" to 1.9. Moving between major MC releases is bad, i.e. possible corruption and loss of items. Try using a Save to restore your original world. Then make a brand new 1.9 world.
Rollback Post to RevisionRollBack
"We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far."
What version were you playing before you "shifted" to 1.9. Moving between major MC releases is bad, i.e. possible corruption and loss of items. Try using a Save to restore your original world. Then make a brand new 1.9 world.
That's only an issue if you downgrade; it should be totally safe to upgrade to 1.9 unless you were using mods in 1.8 or an older version. At the worst, you'd get chunk walls where world generation was changed (which was not changed since 1.7, except for some new structures and the End).
This sounds more like a case where they downgraded, perhaps from a 1.9 snapshot or pre-release to 1.8.9, then upgraded back to 1.9; once you load a world in any new snapshot or pre-release you are stuck (except for the cases where no changes were made; as always, make a backup before downgrading). Actually, I don't think there is an issue downgrading from 1.9 to 1.8 as long as no new blocks/items/mobs were introduced into your world (1.8 changed the way item IDs are stored, which WILL break any world that is downgraded to 1.7.10 or earlier).
That's only an issue if you downgrade; it should be totally safe to upgrade to 1.9 unless you were using mods in 1.8 or an older version. At the worst, you'd get chunk walls where world generation was changed (which was not changed since 1.7, except for some new structures and the End).
This sounds more like a case where they downgraded, perhaps from a 1.9 snapshot or pre-release to 1.8.9, then upgraded back to 1.9; once you load a world in any new snapshot or pre-release you are stuck (except for the cases where no changes were made; as always, make a backup before downgrading). Actually, I don't think there is an issue downgrading from 1.9 to 1.8 as long as no new blocks/items/mobs were introduced into your world (1.8 changed the way item IDs are stored, which WILL break any world that is downgraded to 1.7.10 or earlier).
I went from 1.8.9 to 1.9. I sometimes go from 1.6.4 to 1.7.10 on other worlds, and that does not cause a problem. Do you think I should try going back to 1.8.9?
I guess I'm saying that your stuff is gone. Going back might make things even worse.
You probably accidentally opened this world (even for just a second) when you were trying to use 1.7.10
You should create a dedicated profile for each old version you want to use and configure it to use a separate dedicated game directory and keep your various worlds organized by version. Whenever you want to use a world in a later version you can copy it from .minecraft1710/saves to .minecraft189/saves for example.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
1.9 corrupted my world. I have a youtube account, was doing a series. When I started Ep. 2 I shifted my version to 1.9, logged on and looked in my chest. Nothing there. I looked in my Inventory. Nothing there either. I went to complain on Mojang. Could not log on. Think I should cheat the stuff back in?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhat version were you playing before you "shifted" to 1.9. Moving between major MC releases is bad, i.e. possible corruption and loss of items. Try using a Save to restore your original world. Then make a brand new 1.9 world.
"We live on a placid island of ignorance in the midst of black seas of infinity, and it was not meant that we should voyage far."
That's only an issue if you downgrade; it should be totally safe to upgrade to 1.9 unless you were using mods in 1.8 or an older version. At the worst, you'd get chunk walls where world generation was changed (which was not changed since 1.7, except for some new structures and the End).
This sounds more like a case where they downgraded, perhaps from a 1.9 snapshot or pre-release to 1.8.9, then upgraded back to 1.9; once you load a world in any new snapshot or pre-release you are stuck (except for the cases where no changes were made; as always, make a backup before downgrading). Actually, I don't think there is an issue downgrading from 1.9 to 1.8 as long as no new blocks/items/mobs were introduced into your world (1.8 changed the way item IDs are stored, which WILL break any world that is downgraded to 1.7.10 or earlier).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
I went from 1.8.9 to 1.9. I sometimes go from 1.6.4 to 1.7.10 on other worlds, and that does not cause a problem. Do you think I should try going back to 1.8.9?
Going from 1.8.* to 1.7.* will cause all your chest and inventory contents to permanently disappear in any loaded chunk faster than you can say "Oops"
Going backwards is never advisable as old versions don't understand stuff from the future.
Should I just do nothing then? (Not saying that in a mean way, just a question.)
I guess I'm saying that your stuff is gone. Going back might make things even worse.
You probably accidentally opened this world (even for just a second) when you were trying to use 1.7.10
You should create a dedicated profile for each old version you want to use and configure it to use a separate dedicated game directory and keep your various worlds organized by version. Whenever you want to use a world in a later version you can copy it from .minecraft1710/saves to .minecraft189/saves for example.