We started getting this error after doing some extensive exploring in new chunks generated by the new terrain gen (our world's been around since 1.6). We had no problems with the new terrain gen for quite a while; it only started after a couple of us went exploring on horseback very far from where we'd been previously (5-10k blocks) When we go back to the chunks generated BEFORE the issue began we don't have problems. Also, it happens less regularly when there are less people on the server, and when the explorer stays in one place in the new chunks generated, not moving around much.
Please fix soon! It's becoming quickly unplayable on our server!
I get the feeling that a couple of different bugs are being represented here, given the variety of ways people have come across this issue. This isn't surprising, given the generality of the error message. Perhaps those of us with the problem can do some more experimenting to see if we can come up with a way to replicate our problem from scratch? If our experiments lead us to multiple, very different ways of replicating the error then we could look into splitting the issue into separate issues and resolving each one individually. I'm committed to getting this fixed though; this really messes up the experience on our vanilla server.
I will have to do some tinkering with our server, but here is what I've noticed when this has happened to us on the two different servers I play on where this error occurs:
1. Old terrain (Pre-1.7) exists on the server.
2. New terrain (1.7) is being generated quickly when this error begins to occur; by quickly I mean the player is usually either boating, on horseback, or using a speed buff and running mainly in one direction for quite a while, all while generating new terrain.
3. Once the problem begins to occur, it occurs repeatedly until (a) the player stops generating new terrain, and (b) leaves the new terrain that has been generated after the error started occurring.
4. Anytime a player returns to the area where the error was occurring, the error begins to happen again for the whole server until the said player leaves the area again.
Again, I'll play around with it and see if I can get this to happen consistently. I'll create a test server with these conditions, and see if the error occurs for me. If anyone else can experiment with this, or add anything to the steps that I mentioned, that would be great.
Kyle Tuft
MC-7194
Not modded whatsoever, just launched from Magic Launcher, but otherwise vanilla 13w02b.
@Yaroslav not Tekkit.
We started getting this error after doing some extensive exploring in new chunks generated by the new terrain gen (our world's been around since 1.6). We had no problems with the new terrain gen for quite a while; it only started after a couple of us went exploring on horseback very far from where we'd been previously (5-10k blocks) When we go back to the chunks generated BEFORE the issue began we don't have problems. Also, it happens less regularly when there are less people on the server, and when the explorer stays in one place in the new chunks generated, not moving around much.
Please fix soon! It's becoming quickly unplayable on our server!
I get the feeling that a couple of different bugs are being represented here, given the variety of ways people have come across this issue. This isn't surprising, given the generality of the error message. Perhaps those of us with the problem can do some more experimenting to see if we can come up with a way to replicate our problem from scratch? If our experiments lead us to multiple, very different ways of replicating the error then we could look into splitting the issue into separate issues and resolving each one individually. I'm committed to getting this fixed though; this really messes up the experience on our vanilla server.
I will have to do some tinkering with our server, but here is what I've noticed when this has happened to us on the two different servers I play on where this error occurs:
1. Old terrain (Pre-1.7) exists on the server.
2. New terrain (1.7) is being generated quickly when this error begins to occur; by quickly I mean the player is usually either boating, on horseback, or using a speed buff and running mainly in one direction for quite a while, all while generating new terrain.
3. Once the problem begins to occur, it occurs repeatedly until (a) the player stops generating new terrain, and (b) leaves the new terrain that has been generated after the error started occurring.
4. Anytime a player returns to the area where the error was occurring, the error begins to happen again for the whole server until the said player leaves the area again.
Again, I'll play around with it and see if I can get this to happen consistently. I'll create a test server with these conditions, and see if the error occurs for me. If anyone else can experiment with this, or add anything to the steps that I mentioned, that would be great.
Joseph, given your specs I would say that this is the issue you're facing, not a bad connection to a server!