Migrated from Purpur 1.21.10 to 26.1.2 — /time commands broken, sun frozen, "no clock defined for minecraft:overworld"

[/u/K-port]

Hey, I recently migrated my server from Purpur 1.21.10 to Purpur 26.1.2 and I'm facing a weird issue with the world clock.

Symptoms:

- Sun, clouds and villager schedules are completely frozen

- Any /time command (/time query daytime, /time resume, /time set day) returns an error saying there is no clock defined for minecraftverworld

- gamerule advance_time is set to true

- /execute data get entity u/p Dimension confirms I am in minecraftverworld

What I tried:

- Deleted and let the server regenerate world_clock.dat files (in world/data/minecraft/ and world/dimensions/minecraft/overworld/data/minecraft/)

- Created a datapack that explicitly defines a world_clock for minecraftverworld (empty JSON file at data/minecraft/world_clock/overworld.json)

- Checked level.dat, no relevant difference found compared to a fresh world

- The Time value in level.dat is present and non-zero (18754520)

Migration notes:

- The world was previously using the Infinity Cave datapack which modified world height (min_y: -128, height: 448). This datapack is no longer present, replaced by a minimal datapack that only redefines the dimension height for chunk compatibility.

- All world data was manually migrated (DIM-1 → dimensions/minecraft/the_nether, DIM1 → dimensions/minecraft/the_end, playerdata → players/data, etc.)

The /time commands work fine on a fresh world created directly by Purpur 26.1.2, so the issue is definitely related to the migrated world data.

Any idea what could cause this and how to fix it?

submitted by /u/K-port
[link] [comments]

Continue reading...