Horizons Daybreaker Crashes

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • 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

Stead.fast

New Member
Jul 29, 2019
5
0
0
Title:
Horizons Daybreaker Crashes​
Launcher Version:
1.4.11​
Modpack:
Horizons: Daybreaker​
Modpack Version:
1.2.0​
Log Link:
Details of the issue:
The server will run fine for a while and then suddenly it will kick all clients (I play on LAN with my girlfriend right next to me) and will not allow them to log back in.

I tried updating to the latest 64 bit Java, still no go. I do have Treecapitator and bksprscore installed additionally, but I did a clean unaltered install of the server and client and ran into the exact same issue after about ten to fifteen minutes on the server.

Thanks for the help.
​
 
Won't let me edit so I'll just add it here...

Deleting the player data allows us to log back in, but it re-corrupts and we keep losing our inventory / map data / bed spawn etc.
 
For clarification, is the server crashing or do the clients crash to desktop?
 
Sorry to double post but I error out on edit...

If it is the client that is crashing to desktop check your client crash log.
If the log looks like this: http://pastebin.com/chn848eN (null pointer exception part)

Then try removing Blood Arsenal from the server files. There is a mob from that mod which causes the client to push up daisies. I had the exact same issue a couple of days ago and, O-M-G, it was bothersome but removing that mod totally fixed the issue.

P.S. if this gets you up and running and you eventually notice an issue with the "Tome of Alchemical Knowledge" //forgetting// EMC research try removing wiiemc from the server as well. I kinda had to restart my research 5 times before figuring out where the issue was.