Solved DW20 1.6.4 crashing with upgrades from .16

  • 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

Tim Draper

New Member
Jul 29, 2019
4
0
0
We've been running find on every release upto and including .16. we have tried .18 and .19 updates, but it appears that everytime we enter a certain house area, the server will crash.
the player in question is heavily reliant on AM2, and after finding issues with mana batteries present and what appears to be block ID changes (we've dumped mana batteries to trash/lava), i suspect issues are still present surrounding the AM2 mod.

this is the crash report when we enter the players house:
http://pastebin.com/xvNFwQhR

with the issues we've had with releases after .16, i'm hoping someone has encountered these issues on their server and can give some help to us!

edit: host is private dedicated server, running linux and java 1.7u51. no extra mods
 
Last edited:

Wagon153

New Member
Jul 29, 2019
3,148
-3
1
Crash appears to be occurring due to multiparts, which is strange as usually that is a client side issue. Try getting rid of all the multiparts in said house using MCEdit.
 

Tim Draper

New Member
Jul 29, 2019
4
0
0
Thanks for the input. The player did have microblocks in those areas. Not sure exactly which ones were at cause though.
we 'fixed' it a slightly different way...

We've been using MCPC+ since dw20 1.6 came out, so it's part of the fixtures for us. While I said we had no extra mods installed (technically correct, right?) we are using MCPC+ r250 which I overlooked. Even going back to r245 and r225 that we've used in the past, the problem stayed the same; crash when that house area was loaded.
What we did was run the default server jar that comes with DW20, it reset the 3 chunks that it was upset with (totally deleted and regenerated the affected chunks), and now the player is working on rebuilding those areas. reverting back to MCPC+ server jar is also working normally now those chunks have been reset.

Simple solution that took far too long to think of trying, and the player was happy for me todo that and for him to rebuild, so I'm marking this as resolved.