If you've ever experienced an issue where you can't join a Sundial-enabled world, it's likely due to the game freezing while loading in. If you've ever noticed a stutter or freeze in the loading screen animation, that's where the problem lies.

But why? How does a freeze mess with the mod detection process?
The answer to that is simple: Moonbow 0.4--and as a result, Sundial 0.1--had a three second timeout on the process. That meant that any client joining the server had to respond to a mod requirement check within three seconds. If it failed to respond, it assumed that Moonbow was not installed, and therefore, Sundial cannot be functioning. Usually, the client responds in a fraction of a second, but when it freezes, it misses its opportunity to, and is promptly disconnected to avoid confusing synchronization issues.

Can something be done about the freezing?
Not really. Vanilla, unmodded Staxel suffers from these freezes, too, though you never really notice them. The only reason it's apparent now is due to Sundial needing a strict time-frame for client responses.

Can something be done about the strict time-frame?
Absolutely! Starting with Sundial 0.2, powered by Moonbow 0.4.1 (2022-08-19), you can modify the mod detection process using the Sundial config file. You can increase the timeout length, or simply disable the mod check, in the first place!

To get started, simply join your world and use the SetDayLength command. It'll automatically replace your old config file with the new one.

If you'd rather copy-and-paste, though, then here are its contents, complete with descriptions!


If you run into issues or need help modifying your config file, do post below! I'll try to help you as quickly as possible.

Stay safe, stay positive, and keep on being awesome!