Take the 2-minute tour ×
Arqade is a question and answer site for passionate videogamers on all platforms. It's 100% free, no registration required.

My favorite single-player map is relatively old - created no later than beta 1.1. Since then, the terrain generation algorithms have changed. When I explore any farther, I'm faced with glitches like sliced mountains and differences in sea level.

I tried making a new world with the same seed, but it turned out completely different.

Is there a way to smooth the transition between the old and new automatically, or will I have to run around terraforming myself?

share|improve this question
2  
There's no tool I know of to do this automatically. VoxelSniper is a large-scale in-game terrain editor that would make the terraforming easier, but you'd have to set up a local Bukkit server, install the VoxelSniper plugin, add (a copy!) of your world, connect to the server to change things, and then copy the world files back to your single-player worlds directory. –  SevenSidedDie Nov 6 '11 at 21:10
    
I don't know enough about it to post it as a full on answer, but I believe MCEdit allows you to transplant chunks from one map to another. If nothing else, it'll let you pick and choose which chunks to bring forward (like chunks with structures). –  Raven Dreamer Nov 6 '11 at 22:56
1  
You may not be able to fix the problem, but one fun option would be to pack up all your belongings and take a long, long, long trip through the Nether until you reach an area far beyond the borders of your already-explored regions. This will give the terrain generator a nice blank canvas while keeping your legacy world around too. –  Brant Nov 7 '11 at 5:11

1 Answer 1

up vote 2 down vote accepted

The world generation has radically changed since 1.8 (and will change again in 1.9+), so it's most likely not possible to directly run your world again. In my tests, a world imported from 1.7.3 into 1.8 did have significant changes in the biomes and the landscape.

A workaround which would always work, if you're ready to relinquish new features, would be to keep the binaries (~/.minecraft/bin) of the old version around and swap them around as needed.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.