Fireblast aftercast?
It's a known bug that's been around like half a year. Nothing has been done about it, and judging from all the other completely ignored bugs, it never will.
Yes, it makes playing a fireblast set a lot harder than it's supposed to be.
Nope, that's false. My fire blaster has had the problem since it first appeared. And I haven't even been to the tailor since the color changes were introduced in the game. Everything is 100% default, but it's still bugged.
Are mind fires immune because I'm default colors and have never experienced this?
http://www.xtranormal.com/watch/6685529/3-hot-and-vex-3
weird. i was able to fix it on my fire/cold just by putting on bright fire.
|
I will have to change his blasts to see what happens
Does this happen in PvE also? If it does there's a lot better chance of it getting fixed (say, with I17's release).
EDIT: Nevermind, just tried it out. Fire Blast roots for too long, Fire Ball doesn't. This was with default colors.
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
Sigh....just as I thought. It's never gonna be fixed.
Just like with Epsilon's data on PvP drops, when Divine tried to explain the bug to them, they just probably called him a liar and decided he made it all up.
It's definitely easier to simply call your players liars than to actually fix bugs.
I've never experienced that kind of groundin on fireblast (w/o darkblast), on a blaster though it does have a longer animation time than on a corr... If you play both regular enough you will notice the difference and it will be a bit annoying.
If fireblast went as fast as a corrs, as much as i would like it, that would make them OPd.
Edit: more op'd
lol at fire being OP'd.
Count how many fire blasters play on serious arena teams in the league.
If you count more than 0, you know something I don't.
Er, I'm probably missing something, but afaik it's been that way since the Defiance changes. Fire Blast has an animation that's 1.2 seconds, but the root time is 1.67 (for Blasters) to match all of the other tier 2 blasts. So if you're getting almost a half second of nuisance after the animation where you're still rooted, it's working as intended and does the same thing in PvE.
For Corruptors (and probably Dominators), I'd imagine that for less work in the animation department the "Dark Fire" probably links to the same (ie, Blaster) animation for all of the ATs, and gives the same root time; they should have a 1.2 second animation, which is why you shouldn't have the issue with bright fire (same animation, painted different) or the original colors. Giving the Blaster version of the animation to Defenders when it was ported over is also why the Defender Ice Blast has a 1.67 second animation vs the Corruptor's (or Dominator's) 1 second animation.
Long story short - if it's longer than 1.67 seconds (adjusted for animation sequence timing - ie, arcanatime - to 1.848) then it's a bug. If it's not, then it's WAI.
Or someone could PM BAB and see if he can look into it. I'm just guessing based on what I remember of the changes for Defiance 2.0.
it has gone from unconscionable to downright appalling that we have no way of measuring our characters' wetness.
|
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
The day devs finally fix bugs will be the day after i quit coh probably.
i am not raging enuff yet..sowwy :P
Why all of a sudden is there a 1-2 second aftercast on fireblast which makes you root nearly as long as shout? It makes this set almost unplayable in pvp
Fix this crap please!
"You wrote that the world doesn't need a saviour, but everyday I hear people cry for one"
Mortilance - Elec/WP Stalker