Quote:
Originally Posted by Alunova
[You must be logged in to view images. Log in or Register.]
Should interrupt only if that person has access to the bash skill.
In classic, iirc, slam was limited to 1 damage and a very small chance to interrupt unless that person also had skill in bash, which would increase the damage and stun ability of slam equally.
Shamans for example would never bash for more than 1 damage, with a very high miss rate and very low stun chance, even at 60.
|
Shaman on live 99-06 and can attest that Bash is only 1 damage for non-native classes (or racial only bash). I agree that it had a high miss rate even at level 60, but from my memory a landing bash ALWAYS interrupted the cast, and in the way stated above by stopping the cast immediately. Most of the time the mob would immediately (after swing due to mob auto-attack) and usually try to recast the spell.
By having it work the way it does now, allowing caster to finish casting is allowing people more chances to attempt bash on monsters and reducing the potential # of casts a mob will make (whether successful or not). I don't know if that last bit made sense but what I am trying to say is, mobs are easier if allowed to continue casting even if that cast has a chance to re-gain concentration.
***Like to add that I believe mobs immune to stun were also immune to the interrupt effects of a bash, even if landed.