So I logged onto my singleplayer world today, and decided to go and get some quick XP from my grinder. I had not been there since I used MCEdit to "Repair Regions" after my computer lost power and screwed up some stuff. The world has been seemingly fine. However, as I go down the path to the grinder, I am confronted with a stone wall. I dug around abit, then flipped on an x-ray texture pack. The grinder is completley gone, along with the dungeon and the cave near it. The underground is signifigantly different in a cubical area. What could have caused this kind of error? Is the rest of my world at risk? And is there any way I can get my grinder back?
So I logged onto my singleplayer world today, and decided to go and get some quick XP from my grinder. I had not been there since I used MCEdit to "Repair Regions" after my computer lost power and screwed up some stuff. The world has been seemingly fine. However, as I go down the path to the grinder, I am confronted with a stone wall. I dug around abit, then flipped on an x-ray texture pack. The grinder is completley gone, along with the dungeon and the cave near it. The underground is signifigantly different in a cubical area. What could have caused this kind of error? Is the rest of my world at risk? And is there any way I can get my grinder back?
just a hunch, but may be relavant. the last time I experianced a problem similar to this was when running a server across multiple versions of minecraft (basically just upgrading as new versions came out). I had originally made my world with a manually imported save so in the server properties the seed was not recorded but due to the save being there, it still knew the seed to use. we had a power outage and it crashed making slight damages to the world, but one thing I noticed was that the server properties now had a seed and it was the incorrect one. So here is my theory, whatever caused you to use the "repair regons" portion of McEdit or possibly even McEdit itself may have deleted your original seed leaving minecraft to make it's own. so with the exception of any damaged areas (as far as the file goes any way, not in game) only areas you have visited would be generated from the old seed leaving the potential for drastic abrupt changes on those outer boundry chunks as you explore new areas that have been generated by the new seed.
just a hunch, but may be relavant. the last time I experianced a problem similar to this was when running a server across multiple versions of minecraft (basically just upgrading as new versions came out). I had originally made my world with a manually imported save so in the server properties the seed was not recorded but due to the save being there, it still knew the seed to use. we had a power outage and it crashed making slight damages to the world, but one thing I noticed was that the server properties now had a seed and it was the incorrect one. So here is my theory, whatever caused you to use the "repair regons" portion of McEdit or possibly even McEdit itself may have deleted your original seed leaving minecraft to make it's own. so with the exception of any damaged areas (as far as the file goes any way, not in game) only areas you have visited would be generated from the old seed leaving the potential for drastic abrupt changes on those outer boundry chunks as you explore new areas that have been generated by the new seed.
The thing is, I haven't noticed any abrupt changes except in that small area.
EDIT: I went for a little exploring trip, and went into new chunks. There are no errors or harsh edges at all. They only seem to exist in a cubical area where my grinder was.
EDIT: I went for a little exploring trip, and went into new chunks. There are no errors or harsh edges at all. They only seem to exist in a cubical area where my grinder was.