Version:

• Minecraft Version: 1.20.1
• Fabric Version: 0.16.12
• Mod Version: 1.20.1-beta-0.7.2

Describe the bug
When using CRN with Time and Wind set to a real-time scenario (full 24hr cycle, made w/ trial and error + DragonLib config to sync the time correctly), the visual model for the clock shows a completely different time to the CRN actual time.

To Reproduce
Steps to reproduce the behavior:

1. Set up Time and Wind and CRN to show realistic time. This is done by setting Time and Wind to have 1,728,000 tick total day length (1,008,000 tick day, 720,000 tick night), set up timezone, and set DragonLib's .toml to have 1,728,000 day length with a 1,294,800 tick offset (dunno why, might be my timezone or smth).
2. Save everything, relaunch Minecraft, and reload TAW.
3. Place a CRN clock.
4. Clock shows a time of (I think) 9:12. (Note: This discrepancy also exists with other clocks, but as those are from other mods, I suspect they rely on a 24,000 tick day to operate.)

Expected behavior
The CRN clock shows the time accurately as it is represented in-game.

Screenshots
This screenshot was taken at 6:07pm as seen in the screenshot.

Additional context
I have used another time mod before, but the relevant .tomls have already been deleted from the Minecraft instance.

edit: figured out how the cuckoo clock works, still wrong tho

Also turns out that pausing the game (singleplayer) causes the time to be off when unpausing, this is likely done so trains aren't desynced with the current time tho.

I think I just don't know how to configure DragonLib to work with Time and Wind...

new bug: the time isn't updating for some reason, despite the train working fine (it's using CRN time schedules).

new bug: the time isn't updating for some reason, despite the train working fine (it's using CRN time schedules).

I think I fixed it - TAW's realtime sync apparently wreaks havoc with the current time and time progression.