Fatal Error on connection to server.

Question

Fatal Error on connection to server.

madhatr opened this issue 7 years ago · 10 comments

madhatr commented 7 years ago

minecolonies-universal-1.12.2-0.8.4701.jar

forge-1.12.2-14.23.0.2538

Expected behavior

Connect to minecraft server.

Actual behaviour

Fatal error during connection, connection terminated.

https://pastebin.com/mtNg23KS

Raycoms · Answer 1 · 2017-11-12T19:19:04.000Z

Did that happen more than once?

madhatr · Answer 2 · 2017-11-12T21:14:35.000Z

Yeah, i'm not sure what happened. Something when I was going to a this new version. I can't connect until I delete the colonies.dat file inside the world/minecolonies folder.

So looks like that colony is gone.

madhatr · Answer 3 · 2017-11-12T21:38:09.000Z

Also when you delete the dat file, the server gets spammed with this message.

[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:33] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:34] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.
[17:36:34] [Server thread/WARN] [minecolonies]: TileEntityColonyBuilding at world:[-256,68,-408] had colony.

Raycoms · Answer 4 · 2017-11-13T00:39:03.000Z

Please try with forge: 14.23.0.2493

Until we fixed this.

Raycoms · Answer 5 · 2017-11-13T00:58:12.000Z

Has been reported to forge, please follow: MinecraftForge/MinecraftForge#4514

madhatr · Answer 6 · 2017-11-13T02:14:54.000Z

Okay so it was a MC issue? You will have it fixed soon? based on MinecraftForge/MinecraftForge#4514

Justen-N · Answer 7 · 2017-11-13T02:17:35.000Z

It was a Forge issue.

…

On Nov 12, 2017 7:14 PM, "madhatr" ***@***.***> wrote: Okay so it was a MC issue? You will have it fixed soon? based on MinecraftForge/MinecraftForge#4514 <MinecraftForge/MinecraftForge#4514> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1612 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF4Sougvwxl0hcnXz4PPx-EBu4ZB9Boqks5s16YfgaJpZM4Qa_wS> .

Raycoms · Answer 8 · 2017-11-13T02:19:44.000Z

Forge has changed something but that didn't get to us.

@Asherslab is working on something to make our code compatible again.

madhatr · Answer 9 · 2017-11-13T22:42:23.000Z

Once it is compatible again, will I be able to bring my colonies.dat file back in to restore the colony? Not a big deal if not. It was only a budding colony.

Raycoms · Answer 10 · 2017-11-13T23:15:42.000Z

You can try it, if you're lucky it didn't corrupt the colony and it will work =) 2017-11-13 22:42 GMT+00:00 madhatr <[email protected]>:

…

Once it is compatible again, will I be able to bring my colonies.dat file back in to restore the colony? Not a big deal if not. It was only a budding colony. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1612 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGI9yxV3BzldPyvM8bGqC54hnayuTenxks5s2MXQgaJpZM4Qa_wS> .

Share to

Expected behavior

Actual behaviour