(This is my first thread, by the way, so tell me if I'm missing something.)
I've been trying to enter a custom world seed using the NBT Explorer. First, I've generated a world (on a version 'Infdev-20100327', for a example, because entering custom world seed was added in beta_1.3 as feature), then saved the world and closed the game. Within the world's folder, I've deleted all region files and left nothing except the level.dat file itself. Then, I took the NBT Explorer and edited the world's seed to 0, saved data and closed the editor. After loading the world again, it changed under a completely different seed value.
Original seed:
Changed seed:
Randomised seed:
What have I done wrong? This method of changing the world's seed works with every value except 0. Has this something to do with the Java engine or something else?
Is the seed still 0 if you re-open level.dat without opening the world in-game (i.e. only NBTExplorer touched the file)? If so, then the game itself is changing it, presumably since it sees 0 as a flag that the seed hasn't been initialized, much like how more recent versions would use a random seed if you entered 0 into the seed box (they do accept 0 if you edit level.dat, or enter a string that hashes to 0). If this is the case the only way to get these versions to use 0 is to modify the game.
The level.dat file itself remains untouched after saving it and closing the editor (the edited seed '0' value remains). In recent versions, the seed 0 was possible to generate by few two-worded sentences (exemplī gratiā; creashaks organzine, pollinating sandboxes, drumwood boulderhead, et cētera) but in earlier stages of Minecraft development this option didn't exist yet. Only in 1.18+ versions it was available to write 0 in the world seed box and generate it. The NBT Explorer refuses to accept any letters within the seed's box, rendering this option obsolete.
Ah well, I thought the game didn't recognise the world's seed 0 as a edited input wtihout use of modifications. I've looked up early MCedit program with a option to edit the world seed but didn't find any compatible version which handled versions up to 1.6.
You can find an older version of MCEdit here (0.1.7.1 is the latest stable version and the one I use), although I don't know if it is compatible with InfDev (I've never used it on older version worlds but it has a "terrain-classic.png" in its files, suggesting it supports back to Classic):
Either way, if the game itself isn't accepting a seed of 0 MCEdit won't be able to do anything either since it modifies it in the same way, and changing the data type to a string will almost certainly just crash the game (it doesn't work like the seed input box, which is read as a number and if an exception is thrown because it isn't a valid number it catches it (else it would crash) and uses the hash code of the string, most likely you'd see the same error as when loading a world from 1.8 into an older version, due to item IDs being changed to a string).
Hello!
(This is my first thread, by the way, so tell me if I'm missing something.)
I've been trying to enter a custom world seed using the NBT Explorer. First, I've generated a world (on a version 'Infdev-20100327', for a example, because entering custom world seed was added in beta_1.3 as feature), then saved the world and closed the game. Within the world's folder, I've deleted all region files and left nothing except the level.dat file itself. Then, I took the NBT Explorer and edited the world's seed to 0, saved data and closed the editor. After loading the world again, it changed under a completely different seed value.
Original seed:
Changed seed:
Randomised seed:
What have I done wrong? This method of changing the world's seed works with every value except 0. Has this something to do with the Java engine or something else?
Thanks for reading!
Is the seed still 0 if you re-open level.dat without opening the world in-game (i.e. only NBTExplorer touched the file)? If so, then the game itself is changing it, presumably since it sees 0 as a flag that the seed hasn't been initialized, much like how more recent versions would use a random seed if you entered 0 into the seed box (they do accept 0 if you edit level.dat, or enter a string that hashes to 0). If this is the case the only way to get these versions to use 0 is to modify the game.
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?
The level.dat file itself remains untouched after saving it and closing the editor (the edited seed '0' value remains). In recent versions, the seed 0 was possible to generate by few two-worded sentences (exemplī gratiā; creashaks organzine, pollinating sandboxes, drumwood boulderhead, et cētera) but in earlier stages of Minecraft development this option didn't exist yet. Only in 1.18+ versions it was available to write 0 in the world seed box and generate it. The NBT Explorer refuses to accept any letters within the seed's box, rendering this option obsolete.
Ah well, I thought the game didn't recognise the world's seed 0 as a edited input wtihout use of modifications. I've looked up early MCedit program with a option to edit the world seed but didn't find any compatible version which handled versions up to 1.6.
Thanks for reply!
You can find an older version of MCEdit here (0.1.7.1 is the latest stable version and the one I use), although I don't know if it is compatible with InfDev (I've never used it on older version worlds but it has a "terrain-classic.png" in its files, suggesting it supports back to Classic):
https://bitbucket.org/codewarrior0/mcedit/downloads/
Either way, if the game itself isn't accepting a seed of 0 MCEdit won't be able to do anything either since it modifies it in the same way, and changing the data type to a string will almost certainly just crash the game (it doesn't work like the seed input box, which is read as a number and if an exception is thrown because it isn't a valid number it catches it (else it would crash) and uses the hash code of the string, most likely you'd see the same error as when loading a world from 1.8 into an older version, due to item IDs being changed to a string).
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?