OnTime — Changelog

3.0.0

The biggest update to OnTime so far. Major new feature areas plus a full rework of how the on-screen counter syncs with the server, finally fixing the visual ±1 second glitch.

✨ New

• Web admin panel — a built-in dashboard served by the mod itself. View timers in real time, start/pause/stop/reset, edit them, browse the history. Manage with /timer webpanel start | stop | info.
• Dynamic time expressions — set timer durations with math: players_online * 30, score(my_obj, my_team) + 60, etc. Use /timer expr create | set | add.
• Condition expressions — full boolean DSL for timer conditions: &&, ||, !, comparators, and live values like time_remaining, time_elapsed, players_online, score(...). Use /timer condition <name> if <expr> (or if_start).
• Event triggers — fire timers on vanilla events: player death, dimension change (any or specific), advancement earned. Each trigger can either start or finish the timer.
• FTB Quests integration — fire timers on quest completion or reward claim by ID. Auto-detected, no extra setup.
• Jade compatibility — the timer overlay no longer overlaps Jade; both move out of each other's way and restore cleanly.
• Cooldowns — add a delay between repetitions (/timer repeat) and between sequence steps (/timer sequence).
• Per-timer storage — every timer now lives in its own JSON file under config/ontime/timers/. Better for backups, version control and avoiding merge conflicts. Existing timers.json is migrated automatically on first load.
• Export / Import / Clone — share timers between worlds or instances with /timer export, /timer import, /timer clone.

🔧 Improved

• Smooth counter rendering — reworked the client-side prediction so the displayed second behaves like a real wall clock. The "the counter goes back and forth by 1 second" glitch is gone.
• Lower server overhead — scoreboard updates now happen once per second instead of every tick, and the timer-save path no longer rewrites every JSON file on every change.

♻️ Changed

• Default ports Websocket moved to 25581, away from the heavily contested 8765.

🐛 Fixed

• The on-screen counter occasionally appearing to step backwards on networked play.
• Multiple unnecessary disk writes during the tick loop, which could cause micro-stutters on slow disks.
• Some redundant data in the timer sync packet that was sent every second to every player.