Spells / Hot Streak

Hot Streak

changed

build 1.60.1.69876 | compared to 1.15.9.69722 | synced Sep 16, 2026 | how we read this →

Changed in build 1.60.1.69876. 4 fields differ from Classic Era 1.15.9.69722: auraDescription, description, durationIndex, effects.

Classic Era vs Forever

Classic Era 1.15.9.69722

Hot Streak

Fire school

Any time you score 2 spell criticals in a row using using Fireball, Fire Blast, Scorch, Living Bomb, Spellfire, or Frostfire Bolt, you have a chance the next Pyroblast spell cast within $d will be instant cast.

Your next Pyroblast spell is instant cast and costs 100% less mana.

Forever 1.60.1.69876

Hot Streak

Fire school

Your non-periodic critical strikes with Fireball, Frostfire Bolt, Fire Blast, and Scorch grant Hot Streak for $400625d. Hot Streak reduces the cast time of Pyroblast by $400625s1%, stacking up to $400625s2 times.

Your next Pyroblast spell has its cast time reduced by 25%.

changed value added in Forever removed in Forever

Also changed behind the tooltip: effects (not shown in a tooltip line). See the full field diff below for both values, verbatim.

A highlighted $ formula is computed by the game client from spell power, level and talents; the client does not store the final number, so the template is shown verbatim rather than a value invented.

Every field that changed, verbatim

Field	Classic Era	Forever
auraDescription	Your next Pyroblast spell is instant cast and costs $s2% less mana.	Your next Pyroblast spell has its cast time reduced by $s1%.
description	Any time you score 2 spell criticals in a row using using Fireball, Fire Blast, Scorch, Living Bomb, Spellfire, or Frostfire Bolt, you have a chance the next Pyroblast spell cast within $d will be instant cast.	Your non-periodic critical strikes with Fireball, Frostfire Bolt, Fire Blast, and Scorch grant Hot Streak for $400625d. Hot Streak reduces the cast time of Pyroblast by $400625s1%, stacking up to $400625s2 times.
durationIndex	1	8
effects	[ { "amplitude": 0, "aura": 108, "auraPeriod": 0, "basePoints": -100, "chainTargets": 0, "dieSides": 0, "effect": 6, "index": 0, "miscValue": [ 10, 161 ], "triggerSpell": 0 }, { "amplitude": 0, "aura": 108, "auraPeriod": 0, "basePoints": -100, "chainTargets": 0, "dieSides": 0, "effect": 6, "index": 1, "miscValue": [ 14, 161 ], "triggerSpell": 0 } ]	[ { "amplitude": 0, "aura": 108, "auraPeriod": 0, "basePoints": -25, "chainTargets": 0, "effect": 6, "index": 0, "miscValue": [ 10, 161 ], "triggerSpell": 0 }, { "amplitude": 0, "aura": 4, "auraPeriod": 0, "basePoints": -3, "chainTargets": 0, "effect": 6, "index": 1, "miscValue": [ 0, 0 ], "triggerSpell": 0 } ]

Both values are read verbatim from the client tables in the build shown. We publish the change, never a verdict on it.

History

Build	Compared to	State	Fields
1.60.1.69876	1.15.9.69722	changed	4

Full 1.60.1.69876 ledger → · How we read this →