Title:
Details of the issue:
Server won't start anymore with FTB Regrowth.
Launcher Version:Feed The Beast Launcher v1.4.10
Modpack:FTB Regrowth
Modpack Version:0.8.3 (Beta)
Log Link:Details of the issue:
Me and a friend of mine are playing on a locally hosted FTB Server (his 2nd computer I think) for about 3-4 days now I believe. We choose to do Regrowth as it gets good reviews, is challenging but yet you learn alot from it.
We didn't really have much issues untill just a few moments ago. Another friend wanted to join which succeeded, no issues there but then something happend which made the server go bye bye.
First we invited him in the party through the quest book which he accepted. But he wanted to get kicked out of the party to start for his own so we did.. Which resulted in issues. The friend who got KICKED had all quests completed and the other friend who kicked HIM had a buggy quest book in which he couldn't even open it.
Soon after the server crashed giving the log above. He also copied this from the CMD:
http://pastebin.com/NaQv0jyT
I've tried searching around, increasing memory, putting in some JVM arguments. Only thing we didn't try YET (He had to go but he'll be back later) is updating the pack which we will do.
Anyone has any clues as to what this is ? I have no idea anymore, google didn't give me much results which 'fixed' the issue so I don't know.
Thanks for the help in advance,
NoPain9
We didn't really have much issues untill just a few moments ago. Another friend wanted to join which succeeded, no issues there but then something happend which made the server go bye bye.
First we invited him in the party through the quest book which he accepted. But he wanted to get kicked out of the party to start for his own so we did.. Which resulted in issues. The friend who got KICKED had all quests completed and the other friend who kicked HIM had a buggy quest book in which he couldn't even open it.
Soon after the server crashed giving the log above. He also copied this from the CMD:
http://pastebin.com/NaQv0jyT
I've tried searching around, increasing memory, putting in some JVM arguments. Only thing we didn't try YET (He had to go but he'll be back later) is updating the pack which we will do.
Anyone has any clues as to what this is ? I have no idea anymore, google didn't give me much results which 'fixed' the issue so I don't know.
Thanks for the help in advance,
NoPain9