To review cooldown tracking mistakes in League of Legends, rewind 5–10 seconds before the first click, mark which engage, escape, and objective cooldowns were live on both teams, and ask whether the fight converted into an objective or cost your next contest — then Coach Me that loss on thatswhy.gg and turn the Recurring Habit into one queue rule. Mechanics tell you how to land the combo. Cooldown tracking tells you whether that combo was available when you clicked. You all-inned on spell two. The rest of the kit was on break.
| Situation | What A Good Cooldown Window Looks Like | Common Mistake | Queue Rule Fix |
|---|---|---|---|
| Lane all-in | Your key abilities and summoner spells up; enemy engage on cooldown | Extended trade after your combo went on cooldown | No all-in until my ultimate is up |
| Post-skirmish chase | You know enemy Flash timer or saw it used recently | Chase into fog assuming Flash is down | No chase without knowing enemy Flash timer |
| Dragon or Baron contest | Jungler has Smite; team has engage and Flash for the pit | Start objective after burning ultimates in mid | No Baron start until our jungler has Smite |
| Teamfight engage | Front line engage and carry damage cooldowns both live | Start 5v5 while primary engage is on a 40s timer | Wait for engage cooldown before starting the fight |
| Pattern | What It Looks Like | What You Usually Lose | Queue Rule Fix |
|---|---|---|---|
| Fight on cooldown disadvantage | Use combo, miss key ability, walk forward anyway | Lane lead, HP, and first dragon tempo | No all-in until my ultimate is up |
| Assume enemy tools are down | Dive or chase without checking Flash or ultimate timers | Shutdown gold and objective contest tools | No chase without knowing enemy Flash timer |
| Spend cooldowns too early | Win skirmish, burn Flash and ult chasing, lose dragon fight | Next objective and teamfight tempo | No Baron start until our jungler has Smite |
| Vague Goal | Specific Queue Rule |
|---|---|
| Track cooldowns better | No all-in until my ultimate is up |
| Stop chasing blindly | No chase without knowing enemy Flash timer |
| Respect Smite fights | No Baron start until our jungler has Smite |
| Wait for engage | Wait for engage cooldown before starting the fight |
Frequently Asked Questions
- How do I know if a lost fight was a cooldown tracking mistake or a positioning mistake?
Positioning mistakes are about where you stood relative to threats — front line too far forward, ADC in fog. Cooldown tracking mistakes are about availability: you started the fight without Flash, your ultimate, or Smite when the contest needed them, or you assumed enemy tools were down without checking. Review fight start for availability; review the death replay for spacing.
- What is the most common cooldown tracking mistake in solo queue?
Starting an all-in or objective fight while your primary engage or escape tool is still on cooldown from the last skirmish. Review whether waiting one cycle or farming one wave beat clicking forward because the lane felt winnable.
- Should I always wait for my ultimate before fighting?
Not always — short trades and farming often beat waiting. But do not start an even teamfight or objective contest without knowing whether your ultimate, Flash, or your jungler's Smite is available. Review whether the timer you were racing actually needed your full kit.
- How do cooldown tracking mistakes relate to summoner spell timing mistakes?
Summoner spell timing review focuses on whether you spent Flash, Ignite, or Smite well. Cooldown tracking review focuses on whether you checked availability before the fight. Many spell timing mistakes start when you never tracked that enemy Flash came back up or that you burned yours before dragon.
- How does thatswhy.gg help me review cooldown tracking?
Search your Riot ID, Coach Me the loss where the fight felt even and then was not, and read the Recurring Habit. Turn it into one binary rule — no all-in until my ultimate is up, or no chase without knowing enemy Flash timer. After five analyzed SR losses, Why Am I Losing? shows the empty-bar cluster; We’ve Seen This flags the next guess. Excuse Me, Coach? if their Flash was actually down.