Did you read the details on Patch 3.2? Many changes for the new patch, if you still play world of warcraft, I think you should read it first. Here are some others changes for patch 3.2.
First, Patch 3.2 recent living bomb and hot streak changes. The developers have found a bug with Hot Streak and Living Bomb that made the targeting of various mages on mobs too powerful due to the cris from Hot Streak. Blizzard decided to hotfix this to prevent and disable crits from hot streaks when using Living Bomb. This was done to let mages use Living Bomb the way they have thus far. Otherwise the way it works would havehad to be changed.
Blizzard Quote:
During the 3.2 development cycle, players reported the bug that Hot Streak did not trigger from Living Bomb critical periodic damage. Initially, we made the decision to continue preventing Hot Streak from triggering. This resulted in the "non-periodic" text being added to the Hot Streak tooltip. Late in the 3.2 cycle, the decision was revisited, and Hot Streak was allowed to trigger from Living Bomb periodic damage, but too late to correct the tooltip.
However, around the same time, Living Bomb was changed to be allowed on multiple targets per Mage. In addition, our QA team discovered a 3.2.0 live bug that periodic damage from Fireball and Frostfire Bolt was being counted toward breaking the Hot Streak (as these could never crit). In discussion yesterday, we determined that with multiple targets per Mage, Living Bomb periodic damage triggering Hot Streak was too powerful. However, we still liked Living Bomb being used on multiple targets and didn't want to change that. Instead, yesterday (Wed Aug 5) we hotfixed Hot Streak so it could no longer be triggered by periodic damage, resolving both the bug with Fireball and Frostfire Bolt, and the balance concern with Living Bomb.
In the course of that hotfix, a data error was introduced which caused the non-periodic damage from Fireball and Frostfire Bolt to never break the Hot Streak streaks on non-crits. That data error was corrected with a hotfix this morning (Thr Aug 6).
