> > Hmm. Are you saying there is now a lake where before there wasn't one? THAT would > be > > incredible, and I'd have no explaination for that... but that would go beyond > simple > > biomes... that water had to come from somewhere! > > No, the water's not new, at least as far as I know. It's definitely a glitch, though. > The coast on my side is a perfectly sheer cliff that's squared off on one side, and > if you watch the F3 display as you cross, the chunk ID is "Forest" all the way > across. > > > Also, and I amdit I've been spotty on the server, I didn't know you were on and > > building! Where's your place? I'll check it out. > > I'm at roughly x: -447 z: -1037. Pretty much NNW from your pit. > > > Sadly, I'm still in the same spot, still digging the same hole. It's way over > budget, > > way past deadlines, and the Creeper Party is likely to gain a significant number of > > seats in the House next election due to the political football my unfinished dig > has > > caused. > > In Boston, you'd fit right in.
There were changes to biome calculation whenever new biome types were added. Spawn and the area around it is an ocean biome, despite being several kinds of forest, hills, and plains. A kilometer south of me, there's a village, and it's right next to what is now a very green and mycelium-free landlocked mooshroom "island."
Existing chunks should no longer change the biome they are, as that information is now recorded with the biome data, but more changes are always coming, so what exists as we push the edges back will always be messed up. Until they implement a smooth transition that looks at the existing terrain rather than the calculated terrain (doubtful).
I've not had much luck connecting to the server since it went down (the message above). Pings have been in excess of 1 second, sometimes exceeding 1700ms. Haven't been on today though, caught something while driving my sister to/from work over the weekend, hiding from it in bed as much as I can.
|