Timers

Timers use a scoreboard objective that increments every tick. When the score reaches the configured duration, completion handlers fire.

This is a strong fit for round timers, capture phases, delayed rewards, warmups, or any mechanic that should complete after a predictable amount of ticks. Durations are expressed as TimeNumber values - 5.seconds, 200.ticks, etc.

Registering a timer

val timer = registerTimer("round_timer", 5.seconds)

This generates:

• A load function that creates the scoreboard objective.
• A tick function that increments the score of every entity with a score ≥ 0, players or not.

Typical lifecycle

function("round_start") {
	timer.start(player)
}

function("round_cancel") {
	timer.stop(player)
}

Using dedicated start and stop points keeps it clear which gameplay events begin or cancel the countdown.

Using a timer

function("round") {
	with(timer) {
		start(player)
		onComplete(player) {
			say("Time's up!")
		}
		stop(player)
	}
}

Timer with Boss Bar

Combines a timer with an auto-managed boss bar:

val timedBar = registerTimerWithBossBar("boss_timer", 10.seconds) {
	color = BossBarColor.GREEN
	style = BossBarStyle.NOTCHED_20
}

function("boss_round") {
	with(timedBar) {
		start(player)
		onComplete(player) { say("Boss round over!") }
		stop(player)
	}
}

The boss-bar variant is useful when you want a countdown that is both mechanical and visible to players without having to manually synchronize a separate UI layer. Its max is the duration in ticks, and every tick copies the timer score into the bar:

execute as @e[limit=1,scores={boss_timer=0..}] store result bossbar my_pack:boss_timer_bar value run scoreboard players get @s boss_timer

One bar shows one timer: when several entities run the same timer at once, the bar follows one of them. Register a timer per entity, or per team, to show each its own bar.