Pretty much what the title says.
I create a custom Map in 1.16 because it was the newest version. But now I noticed (or rather, I have only just been told) that the map need to be in the 1.14. So I cleared the nether and removed all 1.16 / 1.15 blocks + villagers. But if i load the Map in to 1.14, nothing is there. Its just a normal new generated world.
So I looked for something useful on the Internet, but didn't really find anything, except that the type of storage was changed from 1.13 to 1.14, but nothing from 1.14 to 1.16.
Can someone help me on this problem? Or any ideas, how to fix the world in 1.14?
(I have already tested the Amulet Editor, but not really got anything done. It is described in a rather strange way)
As always, downgrading is not, was never and will never be officially supported. Please do not run 1.16 worlds in older versions of Minecraft.
Rollback Post to RevisionRollBack
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
the best thing you can do is export sections of the world as schematics (not sure if any 1.16 mods exist to do this though) and then import those in 1.14
As far as I know, the only way to "downgrade" a world is to export it as a schematic and import it into a world created in the older version, assuming that the schematic format is cross-compatible (which it should be, as it is stored in a format specific to the editing tool, not the game itself, just make sure that there are no blocks/items/entities that do not exist in the older version). I'm not sure how compatible structure blocks and their associated data files are (in any case, they are quite cumbersome to use for very large structures).
Otherwise, I doubt that anybody will ever make a world downgrading tool due to the changes Mojang is constantly making to the save format since 1.13, which would require updates with every new release, possibly even minor ones like 1.16.1 (I'm not sure of the specific details but the changes are enough to cause chunks to completely fail to load, hence they get reset; long gone are the days when you only had to worry about missing blocks/items/entities. One possible cause may be that chunks have a "data version" tag and the game can only load chunks with a version that is less than or equal to its version, and it is changed with every release, including snapshots and pre-releases).
Pretty much what the title says.
I create a custom Map in 1.16 because it was the newest version. But now I noticed (or rather, I have only just been told) that the map need to be in the 1.14. So I cleared the nether and removed all 1.16 / 1.15 blocks + villagers. But if i load the Map in to 1.14, nothing is there. Its just a normal new generated world.
So I looked for something useful on the Internet, but didn't really find anything, except that the type of storage was changed from 1.13 to 1.14, but nothing from 1.14 to 1.16.
Can someone help me on this problem? Or any ideas, how to fix the world in 1.14?
(I have already tested the Amulet Editor, but not really got anything done. It is described in a rather strange way)
As always, downgrading is not, was never and will never be officially supported. Please do not run 1.16 worlds in older versions of Minecraft.
the best thing you can do is export sections of the world as schematics (not sure if any 1.16 mods exist to do this though) and then import those in 1.14
Creator of Metroid Cubed 3, a Metroid-themed mod! Become a donator today!
As far as I know, the only way to "downgrade" a world is to export it as a schematic and import it into a world created in the older version, assuming that the schematic format is cross-compatible (which it should be, as it is stored in a format specific to the editing tool, not the game itself, just make sure that there are no blocks/items/entities that do not exist in the older version). I'm not sure how compatible structure blocks and their associated data files are (in any case, they are quite cumbersome to use for very large structures).
Otherwise, I doubt that anybody will ever make a world downgrading tool due to the changes Mojang is constantly making to the save format since 1.13, which would require updates with every new release, possibly even minor ones like 1.16.1 (I'm not sure of the specific details but the changes are enough to cause chunks to completely fail to load, hence they get reset; long gone are the days when you only had to worry about missing blocks/items/entities. One possible cause may be that chunks have a "data version" tag and the game can only load chunks with a version that is less than or equal to its version, and it is changed with every release, including snapshots and pre-releases).
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?
Whatever you do backup the world first. Twice maybe in two different spots.
With vanilla Minecraft without external tools it's not possible to do this without getting problems like missing or incomplete stuff broken mobs etc