Describe the Bug

When building contraptions in the twilight forest, they tend to crash when loading them (e.g. when quitting the twilight forest and coming back to it)

Reproduction Steps

1. Create a singleplayer world with the mods mentioned
2. Go to the twilight forest
3. Create the contraption in the screenshot
4. Disconnect from the server and reconnect
5. You should connect in a frozen world. If it is a server, it will also crash

Expected Result

The server should work when I reconnect

Screenshots and Videos

After reconnecting

Crash Report or Log

https://pastebin.com/FbS8xVmR

Operating System

Linux

Mod Version

0.3.2g

Minecraft Version

1.16.5

Forge Version

36.2.34

Other Mods

Twilight Forest version 4.0.870

Additional Context

• the crash seems to happen both on servers and in singleplayer worlds
• To fix the server, you can do this:
  • restart the server with view-distance to 1 and max-tick-time to 600000
  • Connect to the server while being far from the chunks containing the machine (~100 blocks ?) (you can use an NBT editor to edit your coordinates if you would spawn right on the chunk)
  • Go to the machine: it will not crash ! (Do not disconnect/reconnect while here or it will crash)
  • Destroy the machine
• Putting the motor to a lower speed (1) still produces the crash
• I could not reproduce this in 1.18.2 with Forge 40.2.4, Create 0.5.1f and Twilight Forest 4.1.1494
• The crash doesn't happen if the same contraption is made in the overworld (and IIRC it works fine in the nether too but I'm not sure)

i admire the effort you have put into this and i wish i had better news, but create on 1.16.5 is no longer maintained. terribly sorry.

Hello ! Don't worry, I was kinda expecting this, I mostly made this issue so that me/other people that had a similar issue could properly diagnose and fix the affected server

it is a very difficult issue to diagnose because that is not a regular crash. it is a forced crash by the watchdog thread who noticed that the code for processing a tick was not done after 60s. so the crash is not directly related to the issue. somehow something is taking too long. it could be many things among which: a deadlock, or an infinite loop.