Guide

Game cooldown systems explained

Harbor Siege's closed beta shipped Anchor as a support with three buttons: a 4-second heal, a 12-second shield, and a 30-second resurrection. Players mashed heal on cooldown every fight; the shield and res rarely fired because there was no reason to plan — the shortest timer always won. Opponents learned to ignore Anchor after the first heal and focus carries. Support pick rate in ranked 3v3 fell to 11% despite the character's raw numbers.

The refactor kept the same abilities but changed how time gates them: heal gained two charges with independent 6-second recharge, shield stayed at 12 seconds but added a visible wind-up, and a 1.2-second global cooldown (GCD) after any ability prevented frame-perfect heal-spam. Support pick rate climbed to 34%; opponents now tracked charge pips and punished empty-heal windows. A cooldown system is the rules layer that says when an ability may fire again — flat timers, charge stacks, shared pools, or hybrid models tied to combat events. This guide explains cooldown taxonomy, GCD and grouping, CDR curves, UI feedback, PvE vs PvP tuning, the Harbor Siege refactor, a technique decision table versus super meters and stamina, pitfalls, and a production checklist.

What a cooldown system is

A cooldown (often abbreviated CD) is the minimum elapsed time between successive uses of an ability, item, or action slot. Unlike super meters that accumulate from combat and spend in bursts, cooldowns typically start full and deplete on use, creating a rhythm of availability and downtime. Cooldowns appear in MOBAs, MMOs, hero shooters, ARPG skill rotations, and even fighting-game assists where assist call cooldowns gate tag-team offense.

Good cooldown design does three jobs: it caps burst (no infinite healing loops), creates readable windows (opponents know when your escape is down), and forces prioritization (spend the long CD now or save it for the objective). Bad cooldown design feels like arbitrary waiting — identical timers on every button, hidden CDs with no UI, or CDR stacking that removes all pacing.

Cooldown models: flat timers, charges, and triggers

Flat single-use timers

The simplest pattern: use ability, start timer, block reuse until expiry. A 12-second shield is unavailable for exactly 12 seconds after activation. Flat timers are easy to communicate and spectate; they work for high-impact tools (resurrections, map-wide ults) where one charge per fight is enough.

Charge stacks (multi-cast)

Charge-based cooldowns store N uses; each cast consumes one charge and starts a per-charge recharge timer. A heal with 2 charges / 6-second recharge lets you double-tap in emergencies, then leaves you empty for 12 seconds if both charges were spent. Charges add micro-decisions without requiring a separate resource bar — the UI is often pips or segmented rings.

Combat-triggered reset and reduction

Some abilities reset or shave cooldown on events: “on kill, refresh dash,” “on critical hit, -2s remaining.” These tie pacing to player skill but need caps so streaks do not remove downtime entirely. Pair with diminishing returns on repeated triggers in the same window.

Shared and category cooldowns

Ability groups share one timer: all potions on a 30-second potion CD, or all movement abilities on a mobility slot. Category CDs prevent stacking five defensive escapes while still offering variety within the group. Document groups in tooltips — players blame “buggy buttons” when a shared CD is invisible.

Global cooldown and input pacing

A global cooldown (GCD) fires after any ability from a defined set, blocking all of them briefly — classic in MMOs (1.0–1.5s after instants) and increasingly in hero shooters to stop macro scripts. GCD separates “which ability” from “how fast you can chain inputs.”

Fighting games use a related idea on assist calls: after summoning an assist, both players share a short lockout before another tag or assist. The GCD should be shorter than your shortest meaningful ability CD so it paces spam without overriding intentional rotations. If GCD ≥ shortest ability CD, the global gate becomes the only timer players feel.

Off-GCD abilities (fire during GCD) are power budget tools — use sparingly and telegraph with distinct UI so players understand why two buttons fired in one frame.

Cooldown reduction (CDR) and haste

Cooldown reduction lowers remaining or maximum cooldown duration, usually from stats, talents, or buffs. Linear CDR (−10% per stack) is intuitive; additive stacking needs a hard cap (often 40–50% in competitive titles) so late-game builds do not reach zero downtime.

Haste (increase action speed) and CDR are often conflated. Haste speeds animations and cast times; CDR speeds timer decay. Mixing both on the same stat multiplies pacing changes — tune one primary lever per genre. MOBAs frequently use flat CDR caps; ARPGs may use separate “attack speed” and “cooldown recovery” stats.

Show CDR in UI as modified end times, not abstract percentages, so players learn when the ability actually returns.

UI, audio, and readability

Players cannot play around cooldowns they cannot see. Minimum viable feedback:

Radial swipe or numeric timer on the ability icon
Charge pips for multi-charge abilities
Ready flash or audio ping when a high-impact CD completes
Desaturated icon while on CD; distinct color for “locked by GCD” vs “on long CD”
Combat log/tooltip naming the shared category when a button rejects input

Spectator and esports overlays should echo the same timers — casters call “Flash down” because the UI trained viewers to read cooldown state.

Harbor Siege support refactor (worked example)

Anchor's beta kit had overlapping problems: identical mental model (press when off CD), no GCD, and heal shorter than reaction time to punish. The refactor:

Heal: 2 charges, 6s recharge each, 15% reduced throughput per charge to offset uptime
Shield: 12s flat CD unchanged, added 0.4s wind-up VFX so opponents see startup
Resurrection: 30s CD, now resets to 45s if interrupted during 1.2s cast
GCD: 1.2s after any ability; heal cannot bypass via charge dump in one frame

Metrics after two weeks of ranked play: support pick rate 11% to 34%, average match healing throughput +8% (not +200% — charges did not remove trade-offs), opponent focus-fire on empty-heal Anchor windows +22%. The lesson: stagger timers and charges create windows opponents learn; uniform short CDs create noise.

Technique decision table

Approach	Best for	Avoid when
Flat per-ability CD	High-impact ults, boss mechanics, simple mobile skills	Spam-prone low-impact buttons with no GCD
Charge stacks	Heals, dashes, consumable-like skills with burst + downtime	Abilities that must be strictly once-per-fight
Global cooldown	Preventing input macros; pacing support combos	Frame-critical fighting-game specials (use separate systems)
Shared category CD	Potion slots, trinkets, defensive layers	Unrelated abilities players expect independent
Super meter (not CD)	Comeback tension, spectacle supers, on-hit buildup	Simple utility you want on a fixed schedule
Stamina / mana pool	Sustained channeled costs, RPG attrition	Clear “once every N seconds” readability needs

Default for ability-heavy PvP: mix one long flat CD (identity tool), one charge-based utility, GCD under 1.5s, and a 40% CDR cap. Layer combo systems on top — cooldowns pace when tools exist; combos pace how they connect.

Common pitfalls

Uniform short CDs — every button 4–6s; players rotate mindlessly with no commitment.
Hidden shared CDs — two defensives share a pool but only one icon shows timer.
Uncapped CDR — late-game zero-downtime ults break encounter design and PvP fairness.
Cooldown on start vs on end — starting CD at cast while channeling doubles effective downtime; pick one rule per game and document it.
Server/client desync — client shows ready, server rejects; always authoritative timer with reconciliation.
No empty-state punishment — charge abilities with no risk when spent dry do not create opponent counterplay.
GCD longer than rotation — global gate swallows intended per-ability pacing.
Cooldown skip exploits — animation cancel or load-screen reload resetting CDs; validate on server.

Production checklist

Assign each ability a CD model (flat, charge, or event-driven) in the design doc.
Define GCD scope and off-GCD exceptions explicitly.
Map shared/category cooldown groups; list them in tooltips.
Cap CDR or haste contribution; simulate max-build rotation DPS/HPS.
Implement server-authoritative cooldown state with client interpolation for UI.
Build icon timers, charge pips, and reject reasons (“on cooldown 3.2s”).
Playtest empty-state vulnerability: can opponents punish when key CD is down?
Log ability usage intervals in telemetry; flag sub-CD spam as exploits.
Balance PvE separately if NPCs need shorter CDs — do not share one table blindly.
Document whether CD starts at cast start, cast finish, or projectile fire.

Key takeaways

Cooldowns gate when abilities return; they create pacing windows opponents can learn.
Charge stacks and staggered timers beat identical short CDs for readable support and mobility kits.
GCD prevents input spam without replacing per-ability identity.
Harbor Siege Anchor support pick rate rose 11% to 34% after charges, GCD, and wind-up telegraphs.
Cap CDR and show timers on UI — hidden or infinite recovery destroys encounter and PvP design.