The seed for our map, if you wish to play along at home, is 1261263041493870342. First, here’s a screenshot of our sample map. Let’s take a look at how ugly that can be by loading creating a map with Minecraft 1.6.4 and then loading in Minecraft 1.8.3. Mountains will plunge down sheer faces into oceans, strange perfectly square patches of forest will appear in deserts, and other ugly artifacts will appear on your maps.
#How to update minecraft pe generator#
This means if you load a map created in Minecraft 1.6.* into Minecraft 1.8.* then the transitional areas between the area you’ve already explored and the new areas you will explore in the future will be very ugly as the terrain generator will generate completely mismatched terrain. The world seed remains with the world map for the life of that map but what the terrain generation algorithm creates based on that seed can change significantly between major Minecraft versions. Where it breaks down (and what we’re concerned with today) is when players bring an old map from a previous version of Minecraft into a new version of Minecraft. This system works very well, and it’s the magical underpinning of the Minecraft universe wherein players can keep roaming and roaming with new hills, mountains, caves, and more generated on the fly for them to explore. This seed serves as a pseudo-random number that is fed into a complex equation that then generates the Minecraft world around the player, chunk by chunk. Minecraft’s enormous and procedurally generated map is created using a terrain generator algorithm fed by the world’s seed (an alpha-numeric string either generated at the time the world is created based on the system timestamp or supplied by the player).