Bug:
After loading a World with Version 13w16a and loading the same World later with 1.5.1 again, 2 from 6 checked Villages were loaded wrong or damaged.
Recreate: Haven't find out yet, because it is a pretty rare and random Bug.
What kind of Damage:
-Houses cut
-Houses and Blocks placed wrong
-Houses and Blocks disappeared
Note:
World Created in: 1.2.5
Affected Villages first discovered in 1.2.5 and ~1.4.5
Not happend in other backup. (same World)
It seems like it is a rare random bug.
Reload does not solve the problem.
Self build things are (at first view) not effected by this bug.
Related issues
Attachments
Comments
migrated
Torabi
This is generally unsafe (and unsupported, I believe) behavior. You shouldn't expect to be able to load a world that a later version has touched in an earlier version.
Given that, the specific problem shown here is probably caused by something else. What do you see if you generate the world using the same seed in both versions?
migrated
I know that a World touched by a later version could be damaged if you load it again in an earlier version. However, the World that I used was just a copy for testing Snapshots etc. Usually I delete them after I finished my tests. I don't even remember why I loaded the same file in 1.5.1. So I logged out in this Village in the first Picture. As I logged back in, I just saw that the Village were loaded wrong. After I checked if something else was damaged in this World, I was wondering why just some few Villages and nothing else was damaged. Now I generated the World from the seed in both versions and in both versions those two Villages, that were loaded wrong, are completely okay. And after testing that, I tried to reproduce that bug again (I already tried it before I wrote the Bug Report) by loading the in 13w16a new from the seed generated World in 1.5.1.. The Villages were again completely correct loaded. So as I said, it is a rare bug and maybe it was just coincidence. I wrote the Report just to let the Developers know that it happened. For me it's not a problem because, as I said, it was just a copied World for doing some testing.
Ezekiel
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
migrated
Emanuel, did your problem affect mine too?