-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mage]: [Presence of Mind: 12043] [BUG] #233
Comments
Thanks for the report i will look into it soon after some other todo's ;) |
Awesome can barely wait! :-) |
In the wait time you can report more stuff xD :-) |
Sounds like a brilliant idea xD |
I have 1000 of patches here local but most outdatet or never tested so with luck i have instant a fix when you posting reports ;) |
Can I get a copy of those patches then i'll test them 1 by 1? |
Well i have saved patches from 2008-2014 a lot of it must be update to test it ;) but yes i can give you if you need you can join to hipchat https://www.hipchat.com/gnVp2ea0e works on all platforms and phones so i can give you and can talk it easy |
Hello there,
I've just ran into an issue while playing on my mage, it's regarding http://www.wowhead.com/spell=12043 and it doesn't work correctly.
Lets say I'm casting pyroblast and I want to do another pyroblast almost instantly after I've fired my first one. Regularly are you able to cast a pyroblast more after finished casting the first pyroblast instantly with the help of spell 12043 [Presence of Mind], if you press the spell right after your first pyroblast have hit the target, will the buff just vanish.
The buff should'nt be triggered by a spell that you have casted but only by spells you're about to cast.
I hope it makes sence you can try it yourself.
Go to a nearby npc or player, start casting pyroblast keep clicking on Presence of Mind so it will buff right after the cast of pyroblast. Then you'll notice the Presence of Mind buff will dissapear when it hits the target so you're not able to do a double pyroblast.
The text was updated successfully, but these errors were encountered: