After looking through the forums, i still struggle to find a blizzard statement about if they plan to fix Arcane concentration to work with each arcane missiles damages or not.
Because at the moment, Arcane missile damages cannot proc Arcane concentration, but casting it can, and meanwhile flamestrike can proc it both on casting and on the damages it deals, it simply makes no sense and basically deny Arcane mages to play with arcane missile and still have a decent mana management.
Please blizzard tell us, so i can know if i’m losing my time with my mage or not.
Its a typo on the talent, its supposed to be triggered by casting not damaging. This text was fixed at a later point so that the description is consistent.
Its too bad, would be interesting if it only applied to say arcane missiles with each missile being able to trigger it.
There is no evidence that this is a typo. Blizzard concluded that they would keep AM(Arcane Missiles) interacting with AC(Arcane Concentration) as it did back in the day, in Vanilla. However they also stated that they would fix interactions that were not intentional. I believe rather than “Blizzard made a typo”, that they simply did not manage to implement the AM as intended. This is supported by the fact that AM worked as an invisible dot-effect in Vanilla which caused many issues, including that it did not proc “on spell hit”-effects. This was fixed in patch 1.9 I believe, a similar situation occured for critical strikes with AM iirc. AM proccing AC was not fixed until prepatch for WOTLK iirc. With the changes to the arcane spec and haste rating in WOTLK, AM became quite op for a short period and then the spell was changed such that it would not proc AC on each missile hit anymore in an early WOTLK patch (this can be seen in patch notes). However, since it might have been the intention of the class designers that AM would proc AC there is an argument to be made that this “unintentional interaction” should be fixed for TBC Classic. Imo it makes sense for AM to proc AC on each missile since this complements the play-style of the Arcane Mage. Mathematically it will not make AM op (or even strong for that matter) but simply incentivises using AM instead of Frostbolt for situations where Arcane Blast is too mana expensive. It is imo clear from the talent-tree that there was a different intended interaction between AM and AC then what is currently implemented in Classic and Classic TBC.
I agree with the fact that it wouldn’t make AM Op, it will just offer the playstyle it was supposed to deliver at first instead of spamming frost bolt as an alternative.
I dunno if this is a typo, at least in the french version when i read it can proc on damage, it should proc on damage, end of the line, with certains exceptions like it cannot proc on blizzard, but again it can proc on flamestrike, what the hell.
I honestly don’t know if i should commit time in my mage because of that, thing is i don’t really want to play shaman or anything else beside mage, so i’m stuck with a broken talent
that is correct, sadly we already know this has been reported ingame over and over during and before the beta test, and i also did it, all i want is an official note stating if this talent will be playable normally or not, having such information is crucial to many players that want to level up a mage.
Well it wouldnt make AM overpowered but thats not the issue, the talent works on every spell. So if damage would trigger the effect and not casting it would then be applies to all spells doing damage, so every AOE spell would trigger this, most noticeably blizzard would be pretty much a 100% chance to proc.
So the options for this would be to ether change the talent to proc on damage and restrict the spells it can proc on, or keep it as is and change the description to fit how it works currently. Or leaving it alone obviously.
