svrUptime

[1.2.7] — 2026-09-23

Uptime is now measured from the overworld day/night clock, and both views break down to the tick.

Added

• Minecraft 26.3 support.
• /uptime query gametime [unit] and /uptime query realtime [unit] — query either clock on its own, choosing the largest unit it should roll up into. /ut works as before.
• Ticks as the smallest unit on both views, so a reading is exact rather than truncated at the day (Minecraft Time) or the hour (Real Time).
• Seconds and minutes on Real Time, which previously stopped at hours and showed nothing at all for a server up less than a day.
• /uptime admin sleeptime enable|disable — choose whether Real Time counts the time sleeping fast-forwarded through. Enabled (the default) reports world time and keeps both views in step; disabled reports the server's actual runtime instead.
• /uptime admin status now reports both raw clocks and the gap between them, so the effect of that setting is visible.

Fixed

• Sleeping no longer undercounts the day count. Uptime was read from getGameTime(), which counts only ticks that actually executed — sleeping skips no ticks, it jumps the day/night clock, so a server where players sleep every night reported roughly half the sunrises they had seen. Both views now derive from the overworld clock, which is advanced by sleep and persists across restarts.
• Real Time could print "12 Months". A flat 30-day month does not divide a 365-day year, so the cascade could leave a 12-month remainder (1 Year, 12 Months, 4 Days) instead of rolling up. A month is now a twelfth of a year exactly.

Changed

• Real Time is derived from the same clock as Minecraft Time. On a server where players sleep, it therefore reads as elapsed-world-time rather than wall-clock server runtime.
• /uptime query <unit> (the 1.2.6 form) still works and now caps both views rather than only Minecraft Time.
• One jar for Minecraft 26.1 through 26.3 — 26.1, 26.1.1, 26.1.2, 26.2 and 26.3 — on both Fabric and NeoForge, replacing the separate 26.1.x and 26.2.x jars. The mod's code is identical on all of them, so there is nothing to pick between.
• The jar is now named _MC-26.1-3, and the code lives on the multi_26.1-3 branch (multi_26.1 and multi_26.2 are retired).

Dependencies

• Fabric: Minecraft 26.1–26.3, Fabric Loader >= 0.19.3, Fabric API for your Minecraft version
• NeoForge: Minecraft 26.1–26.3, NeoForge 26.1.2.76 or newer (no Fabric API, no Architectury)