Will have to ask my friend again whenever i have time to talk with him and will try and get back to you on it. The answer you get is for the few seconds of trinket and lucid but you can get a max of 3 secs out of them. You can use your 2nd rune any time in an 80sec window without it capping. Forgot to touch on this. That way you have 1 more BM stack than if you waited with combust till right before meteor landed. I guess his question was not, when to pop combustion. His question was when to cast meteor while combustion.
When Hot Streak procs, one trick is to cast the instant Pyroblast after a spell with no travel time, rather than after a Fireball or Frostfire Bolt which have a travel time. The global cooldown needed to put up LB is enough time for the last projectile to land, and the Pyroblast will not munch any Ingite if it crits.
Do this only if Living Bomb has very little time remaining, as waiting too long to use a Hot Streak proc may cause you to lose a chance at another proc.
A second possibility is to use Scorch before instant Pyroblast. The Scorch cast time is long enough to allow any Fireballs or Frostfire Bolts to travel to their target, so if it crits it won't munch any ignites. Also, it has no travel time of its own, so it's crit won't be munched. And finally, it will refresh the Improved Scorch debuff on the target Assuming the mage has this talent, which most deep-fire mages do.
This bug in the ignite mechanic has given scorch a synergy with Hot Streak, however this synergy is by fault and not by design. I guess some calculations must be done to confirm that damage was actually increased by both sources, it could be just info in combat log that it's refreshed twice, but dmg was increased only from one source. Sorry, something went wrong.
Ive read the wiki you copy pasted and yes i know the bug was present but it was fixed or it rarely ever happened. In the logs Ignite is always refreshed 0. So you cant tell me that this is not enough evidence. Also your bigest competitor on the scene has this working correctly. Well, i don't quite understand your math, you're not considering rolling over dmg from previous ignite for example.
I've checked other encounters on that raid to find examples near beginning of the fight, where ignite munching happened, and there's not much counting involved also filtered out irrelevant info. That's why i was asking for more info math done properly , because as you can see info that ignite was refreshed twice is NOT a proof that both crits should be counted towards ignite DoT. Still more info needed if ignite munching should happen always or only sometimes in situations where 2fire spells did crit in same or almost same time without ignite refresh between them.
I'm still burning! Comment by Bergelmir This can get really annoying, because it seems to spread to nearby critters and battle pets as well. This means that while you're technically done with a fight, sometimes there might be a tiny little spider on fire scittering around. Just to top it off, for some reason they take an insignificant amount damage from it, so it stays like that until you're out of range, or until you kill them. Links WeakAuras Export.
Your target burns for an additional 6. If this effect is reapplied, any remaining damage will be added to the new Ignite. Phoenix Flames causes your Ignites to spread to 8 nearby enemies. Please keep the following in mind when posting a comment: Your comment must be in English or it will be removed.
Unsure how to post? Check out our handy guide! Simply browse for your screenshot using the form below. Screenshots containing UI elements are generally declined on sight, the same goes for screenshots from the modelviewer or character selection screen. Notify me of new posts via email. Search for:. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:.
0コメント