mojira.dev
MC-50316

Seed changes when updating to new versions

I started a new world with the server for 1.7.2 and did not specify a seed in the server.properties file. Later, when 1.7.4 came out, I updated the server to the new version and for some reason the seed changed at some point. I checked my first 1.7.4 backup and the seed was the same as the initial seed. When I checked my 2nd backup from a few weeks later, I found that the seed was different. I first noticed it after I had upgraded the server to 1.7.5 where I have found that the seed is different from either of the two previous seeds.

I double checked and created a single-player world with each version with the original seed and noted that the world stays the same for each version. I'm not sure where the seed is stored or how/why it would be changing but this is not expected behavior. When I've created server worlds in the past, I never noticed the seed changing. I have never used a pre-designated seed in the server.properties file but I assume if I had, the seed would be the same for all of them.

Comments 6

Cannot reproduce, however you did give me quite the panic and I ran to check my own 1.7.x-1.7.5 server. 🙂

Try loading the world where the seed changed, with the seed entered into the server.properties. It may override and save your world.

I used McEdit to remove the chunks that were generated with a different seed then set the seed in the server.properties file to the original seed. Everything looks ok so far. However, I would like to point out that I'm apparently not the only one with this problem. I see a discussion on the forums from back in mid-January with a similar problem: http://www.minecraftforum.net/topic/2259145-server-is-replacing-chunks/

Is this still a concern in the current Minecraft version 14w18a / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I have been unable to replicate the issue. I found the seed in the original version, set that as the permanent seed and have had no more problems. That being said, I can't say for sure that the problem has gone away, I just don't know how to replicate it. Reading the previously mentioned forum thread, it looks like I'm not the only one who has had this problem though.

My seed number has changed as well. My world is the same, but if I create a new world with the same seed, I get one completely different. To use Amidst, I have to use an old version of my world, that I had saved (I save my world and take the file with me once a week or so.) It's very weird.
I use snapshots, and I'm well aware of the risk 🙂

Perry Heinrich

(Unassigned)

Unconfirmed

Minecraft 1.7.5

Retrieved