Crash trying to run my modpack in a dedicated server

[vpontin]

Oh hello!

I have a personal modpack which i host on my personal git server, and after a while i decided to setup again a dedicated server to keep my CC turtles running even if i need to close the client for a random reason.

I always separate "universal" (i.e. works in both sides) and singleplayer-only mods in two distinct folders: the proper "mods" for universals and "mods_client" (symlinking it with "mods/1.12.2") for ssp-only mods, and when i cloned the modpack repo into the dedicated server folder i was sure to not symlink the mods_client, so no ssp-only mods load on dedicated server.

 

But for my surprise today i got this crash when i tried to boot the server. I tried to read but i didn't find any clue for what was the culprit mod.

 

So i'm posting on OFF-Topic because i'm sure its not related to Forge, but came anyway because you guys could help me figuring out what mod broke.

Thanks in advance!

[DaemonUmbra]

  Quote

| UE | terrarium | 0.1.0-dev | terrarium-0.1.0-dev.jar | None |

Expand  

This one seems to have errored, it's a place to start.

[vpontin]

Thanks Daemon

EDIT: Gegy just confirmed it was Terrarium the culprit. He already fix the issue. Can close it now! Thanks!

Edited August 19, 2018 by vpontin

[FriendlySurvival]

I know this thread considered "resolved" but I may as well leave this for future passers.  

 

When a crash happens, generally if it doesn't print the obvious error like a corrupted block or what not. You can use the loading status as an indicator and starting place.  

 

What ever mod(s) have a different loading status than the majority is the spot you want to start.