Crashing after joining our server

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Recon

New Member
Jul 29, 2019
408
0
0
Ok I'm at a loss for this one. Been playing on our new world for about a week now, hosted at my friend's house. Its been working just fine up until today. I log on from my desktop when I'm at home, or with my laptop when I go over to visit. Last night I was over there and we played for a few hours. The laptop logs in fine.

This morning, I got online from home and the game loaded up fine, and let me walk around a few seconds, then crashed. I tried it several times and it always crashes. Sometimes I don't even see the world first, the game just disappears.

Strange thing is, I still can log on with my laptop. So I copied my entire setup from the laptop to a new location on the desktop and ran it from there. Same issue as before. It immediately crashes.

can anyone tell what's going on from this crash log?
http://pastebin.com/hZxFNc1S

[edit]
Now it crashes on the laptop too
http://pastebin.com/xgi4t7zg

Seems to be a problem on the server, nobody can get on. Or rather, it lets us log on but a few seconds later it crashes. bizarre.
 
Last edited:

JamiePhonic

New Member
Jul 29, 2019
404
0
0
all i can tell you is that both errors have the same cause and that it has something to do with the codechicken and Forge Multipart libraries.
there isn't any useful info on google, just a lot of similar crash reports and unanswered forum threads.

my only thought is that it could be a RAM problem because it may be referencing a memory location
Code:
java.util.NoSuchElementException: key not found: codechicken.lib.vec.BlockCoord@ffffc196
from that i see its checking for a "key" of some sort at "ffffc196"
whatever "ffffc196" is, it could be a memory location or just as easily a part of a file that got corrupted. i have no idea. for all i know, it could be something else altogether.

you could perhaps try running the server on a different computer. see if that helps?