[1.7.10] Packet was larger than I expected, found 40229 bytes extra whilst reading packet 53

[lightning02]

Forge: 1614
Chisel-2: 2.5.1.44

On the client side the problem look like this: after copied some massive buildings on an area of 15x15 chunks and after modifing or adding some more thing the problem doesn't occurr, but when you disconnect from that area and try to reconnect the ammount of data of the streams is maybe to big to be sent all in once.
But also people that teleport or run to does chunks fall in that disconnection problem and they can't join again.

http://pastebin.com/QwGfVzMM [this is kinda what happens on client side, the logs on server console seems to be not so detailed]

I noticed, looking around that this error happened in 2014 and was related to forge. unfortunately they claims to have fixed that or at least LexManos in December 2015 was still asking if someone was still having the problem but then he locked the github thread; and as we know he is not glad to offer support for 1.7.10 anymore.

I've tryed to reducing the maximum bulk chunks in spigot to 1 but i may gain 1/2 more seconds when I log in but then i get kicked. Now with 41486 bytes extra (but it depends sometimes are 41360 [depends where i look at/move])

Ok, after digging more into the problem i discovered some interesting things.
The problem occur in an area of about 290 blocks within the "corrupted" chunk.
The very interesting things are these:

1. Only happen on server giving that error
2. Chunk render distance does not affect or infuence/avoid the issue
3. Only the coordinates of the player matter (for example if any player approach the corrupted location and reach a chunk within 300 blocks from the corrupted one he get kicked from the server with that error, no matter the render distance they have in video settings)

Anyway i've also loaded the server world in single player and i've located what corrupted the chunk.
It is some blocks from Chisel 2 (in particular factory block) that now appear to be invisible.

I don't know how and when it happened, I only know that those blocks were made using the set command from WorldEdit, but they were fine for a while in fact they didn't get corrupted immediately.
I then manage to edit and remove the corrupted part with MCEdit and actually the world work again on server and people don't get disconnect.

P.S: I heard that Chisel 2 is no longer supported, however the download link of the chisel 3 appear all offline.. could you tell me why?
also, would may this issue be fixed on chisel 3?

[Drullkus]

Check to see if the issue still persists in 2.9.5: http://minecraft.curseforge.com/projects/chisel

On Apr 16, 2016, at 8:06 AM, lightning02 notifications@github.com wrote:

Forge: 1614
Chisel-2: 2.5.1.44

On the client side the problem look like this: after copied some massive buildings on an area of 15x15 chunks and after modifing or adding some more thing the problem doesn't occurr, but when you disconnect from that area and try to reconnect the ammount of data of the streams is maybe to big to be sent all in once.
But also people that teleport or run to does chunks fall in that disconnection problem and they can't join again.

http://pastebin.com/QwGfVzMM [this is kinda what happens on client side, the logs on server console seems to be not so detailed]

I noticed, looking around that this error happened in 2014 and was related to forge. unfortunately they claims to have fixed that or at least LexManos in December 2015 was still asking if someone was still having the problem but then he locked the github thread; and as we know he is not glad to offer support for 1.7.10 anymore.

I've tryed to reducing the maximum bulk chunks in spigot to 1 but i may gain 1/2 more seconds when I log in but then i get kicked. Now with 41486 bytes extra (but it depends sometimes are 41360 [depends where i look at/move])

Ok, after digging more into the problem i discovered some interesting things.
The problem occur in an area of about 290 blocks within the "corrupted" chunk.
The very interesting things are these:

1. Only happen on server giving that error
2. Chunk render distance does not affect or infuence/avoid the issue
3. Only the coordinates of the player matter (for example if any player approach the corrupted location and reach a chunk within 300 blocks from the corrupted one he get kicked from the server with that error, no matter the render distance they have in video settings)

Anyway i've also loaded the server world in single player and i've located what corrupted the chunk.
It is some blocks from Chisel 2 (in particular factory block) that now appear to be invisible.

I don't know how and when it happened, I only know that those blocks were made using the set command from WorldEdit, but they were fine for a while in fact they didn't get corrupted immediately.
I then manage to edit and remove the corrupted part with MCEdit and actually the world work again on server and people don't get disconnect.

P.S: I heard that Chisel 2 is no longer supported, however the download link of the chisel 3 appear all offline.. could you tell me why?
also, would may this issue be fixed on chisel 3?

―
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

[lightning02]

Tryed just now, the problem remain the same i guess that WorldEdit broke something but i'm not 100% sure, even because it happened all in once several hours later than the //set block commands .
I've temporally solved the issue removing the corrupted blocks with MC edit, i let you know if the problem occur again in the future.
By the way should i use chisel 2.5.1.44 or 2.9.5.11 at this point?

[TehNut]

2.9.5.11