Issue description:

Server watchdog kills server process due to tick times > 60 seconds. Based on the stack trace and player activity, I think this is occurring when refined storage is re-discovering a network. We've got players who are relocating bases and when they teleport between them the server really eats the dust, sometimes resulting in the crash. This has several times across the last few days. Since

What happens:

Very long tick times / hangs, resulting in crash.

What you expected to happen:

Tick times not severely impacted by network discovery?

Steps to reproduce:

Wish I knew precisely. Issue description contains my best guess.
...

Version (make sure you are on the latest version before reporting):

• Minecraft: 1.16.5
• Forge: 36.1.32
• Refined Storage: 1.9.3

Does this issue occur on a server? [yes/no]
yes

If a (crash)log is relevant for this issue, link it here:

This has happened at least three times in the past few days, though it happened more previously (as I had server watchdog turned off, these earlier ones did not produce crash logs).

Here are three of those instances:

https://gist.github.com/SargeRyong/bdfbdd3d55fb98eb1693f02fed8c2ea8
https://gist.github.com/SargeRyong/fae7c5409ebdc47d9c6dd602ef6e0a24
https://gist.github.com/SargeRyong/2013d44d0d8cfbe402fa1df621d5ecb5

They don't occur during the exact same instruction, but they do appear to be related.

You can set the crash timer by modifying max-tick-time in server.properties.

The only real "solution" is to chunkload them :/.