Server crash after update to recommended.

  • Thread starter Thread starter kristi71111
  • Start date Start date
  • 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
K

kristi71111

Guest
Title:
Server crash after update to recommended.
Launcher Version:
Modpack:
Infinity Evolved
Modpack Version:
v2.4.2
Log Link:
Details of the issue:
After the update from 2.3.5 to 2.4.2 this crash seems to happen with thaumicenergistics. After some testing we have found the issue:
Placing facades arround the arcane terminal Screenshot: http://prntscr.com/aeehnq
Doing this and logging into the chunk when its unloaded (loading the chunk) or unloading the chunk after placing the facades by logging out will crash the server. Issue only seems to happen with forge microblocks. Can anyone confirm or is this only a issue with my server?
 
Actually looking into this:
http://pastebin.com/LRYtRGhs The crash can be reproduced by placing a cable and a microblock in the same area. This will cause the cable to become a microblock (you can notice this because the ME cable will take longer to mine). Now even if you had removed the microblock itself the cable still remains a microblock and adding any Thaumic Energistics terminal (both arcane crafting and essentia terminals) will cause the same crash when this area become loaded or unloaded.
http://i.imgur.com/9fnbRHe.png <--- explanation with a picture
 
What I did as a temp solution was ban forge microblocks since I did try to block their placement next to ae cabbles with a plugin but that did not work. I am working on a fix for this tho...