| Time | Event | Clock | {{ possessionLabel }} | Violations | Copy |
|---|---|---|---|---|---|
| {{ entry.time }} | {{ entry.event }} | {{ entry.clock }} | {{ entry.possessions }} | {{ entry.violations }} | |
| No events yet. Start the clock or begin a new possession. | |||||
A shot clock limits how long one team can hold the ball before taking a shot, so the timer shapes pace, late-possession decision-making, and table-side communication at the same time. In practice, the hardest part is rarely counting down from 24 or 30 seconds; it is restarting cleanly, warning at the right moment, and keeping a usable record of what happened. This timer gives you a manual possession countdown with common preset lengths, a warning window, and an event trail you can export after the session.
The page is built for situations where a dedicated scoreboard is unavailable, overkill, or not flexible enough for drills. It shows the remaining shot clock in tenths of a second, tracks possessions and violations, and keeps a running event list so a coach, referee, or table operator can review resets, pauses, and late-clock breakdowns without reconstructing them from memory.
That makes it useful for more than games. A coach can run a 24-second half-court drill and watch how often the group reaches the warning window, while a practice scrimmage can switch to a 14-second reset profile to rehearse quick second actions after a stoppage or rebound-like restart.
The package is intentionally simple. It does not synchronize with a game clock, trigger a horn, enforce possession-arrow logic, or decide which official rule exception applies in a given play. The preset names point you toward common shot-clock lengths, but the page remains a manual timer rather than a full rules engine.
That distinction matters when you read the outputs. A clean event log or a familiar preset does not certify rule compliance by itself; it tells you what this timer counted, when it was reset, and whether the session drifted into repeated late-clock pressure or violations.
Start by choosing the preset that matches your session, then check the two badges that matter most: Length and Warning. If those two numbers look right, the rest of the timer usually falls into place quickly.
This page works best for drills, table-side rehearsal, pickup games, and smaller venues where one person can actively operate the countdown. It is a poor substitute for a full arena system if you need automatic horn output, synchronized game-clock control, or league-specific reset logic that changes by live-ball situation.
Auto-start on reset. If you are teaching, reviewing film, or correcting the table, leave it off so Reset and New Possession do not launch the clock immediately.Warning threshold against Shot clock length. If the warning value is close to the full clock, the timer will spend most of the possession in warning mode by design.After a few possessions, open Coach Cues and compare it with the Events tab. The combination tells you whether the warning profile, reset behavior, and recent violation trend actually match the drill you meant to run.
The timer is a local browser countdown that updates every tenth of a second. Shot clock length is rounded to whole seconds and clamped from 5 to 60, while Warning threshold is clamped from 0 up to the active clock length. The visible clock is rendered in MM:SS.t format, so a 24-second run begins at 00:24.0 and a near-expiry state might show 00:04.9.
Presets change the starting length only. The shipped options are 24 seconds, 30 seconds, and 14 seconds, which correspond to common competition or drill scenarios, but the page does not branch into different rulebooks after that selection. Everything after the preset is driven by manual controls such as Start, Pause, Reset, New Possession, and the second-by-second adjustment buttons.
The two most important state transitions are the warning window and the violation state. Warning becomes active when the remaining time is greater than 0 and less than or equal to the configured warning threshold. A violation is recorded when the running clock reaches 0, or when a manual downward adjustment drives a running clock to 0. In both cases the timer stops, Violations increments, and an event row is added.
Event logging is broad rather than minimal. Preset changes, starts, pauses, resets, new possessions, manual adjustments, and violations all create rows in the Events tab. Each row stores a device-local Time stamp, the event text, the shot-clock Clock value, the running possession count, and the cumulative violation count. The list is capped at 300 entries, so very long sessions roll older rows off the end.
The timer behaves according to a short, explicit state machine. That makes it predictable, but it also means the operator is responsible for choosing the correct moment to reset or start.
| Trigger | Immediate Effect | Visible Outcome |
|---|---|---|
Start |
Begins the tenth-second countdown and logs Clock started. |
Status changes to Running. |
Pause |
Stops the countdown and logs Clock paused. |
Status changes to Paused. |
Reset |
Sets the clock back to the active length without adding a possession. | The main display returns to the full count. |
New Possession |
Increments the possession counter, resets the clock, and optionally auto-starts it. | Possession increases by 1. |
-1s or +1s |
Shifts the remaining time by whole seconds within the supported range. | The displayed clock and event log update immediately. |
Clock reaches 00:00.0 while running |
Stops the timer, increments violations, and logs Shot clock violation. |
Status becomes Violation recorded. |
| Surface | What It Tells You | Format |
|---|---|---|
| Summary badges | Current length, warning threshold, possession count, violation count, and reset mode. | badges |
| Events | Chronological log of starts, resets, possessions, adjustments, and violations. | table |
| Coach Cues | Three recommendation cards derived from warning ratio, reset mode, and recent violations. | list |
| JSON | Current parameters, live state, and the full exported event list. | structured text |
Coach Cues is not random commentary. It uses the ratio of warning seconds to full shot-clock length to label the warning profile as early, balanced, or tight, then combines that with reset behavior and recent violations to produce three fixed guidance cards. Because those cues are derived from the current session state, they become more useful after at least a few possessions have been logged.
The whole tool runs in the browser and ships without a server helper. Copy, CSV, DOCX, and JSON actions are generated from the current state on the page, which means there is no built-in external time authority, scoreboard link, or central event service behind the session.
Use one short possession cycle first, then expand into full drills once the warning and reset behavior feel right.
Preset. The Length badge updates immediately, which is your quick confirmation that the session is starting from the intended clock length.Warning threshold, Possession label, and, if needed, Auto-start on reset. If the warning value snaps down, it exceeded the current clock length and the tool has clamped it.New Possession to begin a tracked rep. That increments the possession count and resets the display to the full clock length.Start. The status line should change to Running, and the main display begins counting down in tenths of a second.Reset, Set to ...s, or -1s and +1s for corrections during stoppages. If you need the next rep to begin immediately after a reset, turn on Auto-start on reset before continuing.Events after the sequence, then check Coach Cues and JSON if you want a summary of the session state or a shareable export.Once the baseline cycle looks right, keep the same length and warning values for several possessions so the event log and cue cards reflect the drill rather than setup churn.
The headline clock is the real authority here. When the display shows 00:00.0 and the status line reads Violation recorded, the tool has already stopped the countdown and incremented Violations. Before that point, warning is active only when 0 < remaining time ≤ Warning threshold.
Possession is not moving, the operator has not used New Possession; Reset alone does not increment that counter.Time column in Events looks unfamiliar, remember it is device-local wall time, while the Clock column is the possession countdown.Coach Cues before changing the warning threshold. The issue may be reset discipline rather than warning timing.The main false-confidence trap is assuming that a 24-second, 30-second, or 14-second preset means the page is now applying a league rulebook for you. It is still a manual timer, so confirm competition-specific restart conditions and table procedure separately whenever the setting must match official play.
Select the 24-second preset, leave Warning threshold at 5, press New Possession, and then press Start. Early in the rep the summary badges read Length 24s, Warning 5s, Possession 1, and Violations 0.
When the display reaches 00:04.9, the clock turns red but the status line still reads Running. That is the intended late-clock cue: the rep is under pressure, but it has not become a violation yet.
Choose the 14-second preset and set Warning threshold to 14. The next possession begins at 00:14.0, but because the warning threshold equals the full clock length, the red warning state is active from the first instant.
That setup can be useful when you want every rep to feel urgent, and Coach Cues reflects that by treating the warning profile as early rather than balanced. It is a good edge case to understand because it shows the difference between a valid configuration and a practical one.
Suppose the table operator presses New Possession expecting the clock to run immediately, but the summary badge still shows Manual restart. In that state the tool will reset the display and increment the possession count, but it will not resume counting until Start is pressed.
Turn on Auto-start on reset and repeat the action. The badge switches to Auto-start reset, the status line stays Running, and the Events tab records both the new possession and the automatic restart. That is the corrective path when the timer feels slow between live reps.
No. The presets provide common clock lengths, but resets, starts, and corrections are manual. The package does not inspect live-ball context or enforce league-specific exceptions for you.
Because warning is active whenever remaining time is greater than 0 and less than or equal to Warning threshold. If the warning value matches the full clock length, the whole possession counts as warning time.
If the timer is running and a downward adjustment drives it to 0, the tool records a Shot clock violation, stops the clock, and increments the cumulative violation count.
Time is the device-local wall-clock timestamp for the logged event. Clock is the shot-clock value at the moment that event was recorded.
Up to 300 rows. Once the list grows past that size, older entries are dropped so the current session remains manageable.
00:00.0.