Okay, to start off, I'm totally prepared for this to be impossible. I'll accept it if it is. However, my friends and I were playing a modpack (Attack of the B-Team, which is a 1.6.4 modpack, to be specific) and eventually decided that we wanted to create our own modpack based on B-Team, but in 1.7.10. So, I created a test modpack and loaded up a backup of the world where, to no one's surprise, the world wasn't the same at all. Several blocks where changed and several complete biomes had changed.
Ultimately, is there a way to update a world from 1.6.4 to 1.7.10 without loosing the world? Or do we have to start completely from the beginning again to do what we want?
I would create a copy of the 1.6.4 (2018Dec10-1.6.4) world to my desktop and rename the copy 2018Dec10-1.7.10 then drag it to the saves folder and open it in 1.7.10. Your versions folder should have both 1.6.4 and 1 7.10 subfolders. You can do the same with your mods folder.
That is how I name all my worlds YearMMMDD-version. It removes all confusion should I decide to reopen any world after a long period without play.
I think that you misunderstood, sorry if I wasn't clear. The world wasn't confused with another one, it was almost sort of "overwritten" when we updated the mods to 1.7.10.
If you updated without making a copy first you're probably correct... it is too late!
If the 1.6.4 and 1.7.10 versions have the same Mods installed It shouldn't make a great deal of difference.
If the 1.6.4 version contained Mods that modified (non-vanilla) or added things (blocks or items) that the 1.7.10 does not, it's toast IMO and reopening it in 1.6.4 will not solve the problem.
I added a TempStorage folder to my MC. Before I open any world I drag the current copy on my desktop to the TempStorage, and create a copy of the world I'm going to play from the saves folder to my desktop. That way I have 2 very recent copies that can easily be used should something catastrophic occur. For the record it has!!! I only lose a small part of my current world.
a huge number of under the hood things changed between 1.6.4 and 1.7.10. personally i would reccomend using a newer version of minecraft (such as 1.11 or 1.12) as they handle these transitions much more gracefully. having said that there is little hope of saving your world, the best thing you can try is copying the entire config folder from the old version to the new version so that your settings and block configs might be saved, be ready for this setup to crash however because you are using old configs
Okay, to start off, I'm totally prepared for this to be impossible. I'll accept it if it is. However, my friends and I were playing a modpack (Attack of the B-Team, which is a 1.6.4 modpack, to be specific) and eventually decided that we wanted to create our own modpack based on B-Team, but in 1.7.10. So, I created a test modpack and loaded up a backup of the world where, to no one's surprise, the world wasn't the same at all. Several blocks where changed and several complete biomes had changed.
Ultimately, is there a way to update a world from 1.6.4 to 1.7.10 without loosing the world? Or do we have to start completely from the beginning again to do what we want?
Thanks for the help.
I would create a copy of the 1.6.4 (2018Dec10-1.6.4) world to my desktop and rename the copy 2018Dec10-1.7.10 then drag it to the saves folder and open it in 1.7.10. Your versions folder should have both 1.6.4 and 1 7.10 subfolders. You can do the same with your mods folder.
That is how I name all my worlds YearMMMDD-version. It removes all confusion should I decide to reopen any world after a long period without play.
Links to pdf format, downloadable, command lists for (these often clarify/expand descriptions, and where possible link to the author's posting):
MoreCommands: http://www.mediafire.com/view/qjc9c6klcnp660e/CmdLstMoreCommands.pdf
WorldEdit: http://www.mediafire.com/view/bi7r00xd9rgxrrt/WE_Commands.pdf
I think that you misunderstood, sorry if I wasn't clear. The world wasn't confused with another one, it was almost sort of "overwritten" when we updated the mods to 1.7.10.
If you updated without making a copy first you're probably correct... it is too late!
If the 1.6.4 and 1.7.10 versions have the same Mods installed It shouldn't make a great deal of difference.
If the 1.6.4 version contained Mods that modified (non-vanilla) or added things (blocks or items) that the 1.7.10 does not, it's toast IMO and reopening it in 1.6.4 will not solve the problem.
I added a TempStorage folder to my MC. Before I open any world I drag the current copy on my desktop to the TempStorage, and create a copy of the world I'm going to play from the saves folder to my desktop. That way I have 2 very recent copies that can easily be used should something catastrophic occur. For the record it has!!! I only lose a small part of my current world.
Links to pdf format, downloadable, command lists for (these often clarify/expand descriptions, and where possible link to the author's posting):
MoreCommands: http://www.mediafire.com/view/qjc9c6klcnp660e/CmdLstMoreCommands.pdf
WorldEdit: http://www.mediafire.com/view/bi7r00xd9rgxrrt/WE_Commands.pdf
a huge number of under the hood things changed between 1.6.4 and 1.7.10. personally i would reccomend using a newer version of minecraft (such as 1.11 or 1.12) as they handle these transitions much more gracefully. having said that there is little hope of saving your world, the best thing you can try is copying the entire config folder from the old version to the new version so that your settings and block configs might be saved, be ready for this setup to crash however because you are using old configs
Thanks, though we've just decided to start from scratch. The difficulty isn't worth this.
i would strongly recommend picking up 1.11 or 1.12, due to under the hood changes you should never have this issue (to this extent) ever again