Modpack version
1.59a Server Files

Can the issue be reproduced?
Yes

Logs
https://pastebin.com/vJZnfYNe

Issue
Server crashes while starting up after updating to 1.59a from 1.58, downgrading back to fresh 1.58 files launches the server fine.

Client has no issues launching when updated to 1.59a

Did you do the following as listed in the changelog?

It's advised to run the command /bq_admin default load if you are updating from 1.58 or earlier.

(not sure if this is related; I just read it a few minutes ago while browsing)

If I remember correctly that command is used in-game to refresh the Quest Book. Unless I'm able to do in the server console, I can't do the command because I can't get on the server in the first place.

Assuming this is a duplicate of #1020. Same crash message and everything. Something‘s probably fucked up with FoamFix or another coremod... ugh

Moving this to #1020.

That reporter found a fix:

Then to fix what I did

create anew directory with just the new download in it and run the serverstart.bat and chnage eula
it create a new world.. works..
copy over my world to it and it also worked..

something in old directory keeping new download from working with the rest of the old files -world

hope that helps

I will try that, thanks for the help

Ohhhh, it might be library files or mixins staying around when they shouldn’t! If that’s the case, just delete the directories and rerun serverstart

Where do I find these mixin files? I can try this in addition to testing the transferring over the old world to a fresh install.

It’s the .mixin.out directory ^^ also you COULD try to also delete the libraries folder since, if I remember correctly, the server start script we use reinstalls them if they’re not there right?

Unless its hidden in some way, I actually don't have a folder called .mixin.out in my server files. I will try deleting the libraries folder though.

Server still crashes after deleting libraries folder and redownloading it through the serverstart script.

Something else then... The „from scratch“ approach definitely works though (see the other issue again), but... what causes the error then? :/

It didn't happen on my test server by the way, so it doesn't happen every time.