aurelien97480 / oregoncore

Automatically exported from code.google.com/p/oregoncore
GNU General Public License v2.0
0 stars 0 forks source link

The Beast Within + Deadly throw #407

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Spell 34471 (the beast within)
Talent 34692 (the beast within)
Spell 26679 (deadly throw)

When 34471 is activated, you shouldn't be slowed, but deadly throw have a slow 
effect on you.

If you use deadly throw and then the beast within - deadly throw debuff will 
disappear, but if you use deadly throw on hunter after he has used the beast 
within, the slow effect will work.

I think that's because slow effect is triggered after deadly throw deals damage 
(it does do damage to a hunter). But i can be wrong. Hope you fix it soon.

Using last rev. Don't remember which exatly.

Original issue reported on code.google.com by dscrashr...@gmail.com on 23 Feb 2011 at 12:28

GoogleCodeExporter commented 9 years ago
I can confirm this and it isnt only for deadly throw, its for most or all 
slowing effects.

Original comment by Kevdam...@gmail.com on 12 Mar 2011 at 2:05

GoogleCodeExporter commented 9 years ago
Rev 1355+
hash 5a4f38973dbb+

Just tested:
Doesn't have immune to deadly throw
Does have immune to crippling poison
Does have immune to concussive shot
Doesn't have immune to wing clip
Does have immune to frost trap
Doesn't have immune to frost shock
Does have immune to earthbind totem
Doesn't have immune to hamstring
Does have immune to piercing howl
Does hame immune to blizzard (improved with talent)
Doesn't have immune to cone of cold
Does have immune to frost armor
Doesn't have immune to frost nova

I suppose The Beast Within doesn't give immune to Damage-Done Control Spells. 
(Any spell, which does damage, does controll too, but spells which doesn't have 
damage are immune)

Original comment by dscrashr...@gmail.com on 12 Mar 2011 at 7:26

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Should be fixed as of revision 419306ef7bde . Please try with a version newer 
than that. Thanks

Original comment by stfxm...@gmail.com on 12 Mar 2011 at 10:34

GoogleCodeExporter commented 9 years ago
Yes, it is fixed now. Thanks for fix :)

Original comment by dscrashr...@gmail.com on 13 Mar 2011 at 8:53

GoogleCodeExporter commented 9 years ago
Fixed in revision 419306ef7bde

Original comment by stfxm...@gmail.com on 15 Mar 2011 at 3:11