Addon : CombustionHelper 3.0, Comb-Fu Panda.

[Deleted]

Hello all again, the new version of CombustionHelper for 5.0.4/MoP is now available. For the ones who don't already know it, here is some info :

The goal of this addon is to allow easy optimizing of the mage talent Combustion. It tracks all relevant Dots on your target, your cooldown of Combustion so you'll be able to use the talent with maximum effectiveness.

To summarize the new talent : it will add a new Dot on effect on your target which will be equal to the sum of Ignite and Pyroblast Dots.



With this addon, you'll know if one of your Dot is missing.

CombustionHelper is composed of the main addon and 2 bundled other addons : CauterizeCooldown and MageBombTracker. Here is their main features :

CombustionHelper main addon:

• Automatic switch depending if combustion is in your spellbook or not.
• Autohide out of combat is off by default, use config panel to configure it. You can choose between no autohide, autohide out of combat or autohide when combustion is on cd.
• Reset variables option because i know some of you like to bug the thing by switching options while in combat/autohide is running and stuff. If you bug it, just reset and log off so you start with a clean state.
• Option to hide all config messages in chat.
• Dot tick damage report mode. This is not the expected combustion damage report because of the complexity of ignite, rather an information about how much damage the last tick did so you know if it's powerful enough.
• Pyroblast/Hot Streak report mode which will warn you when wasted an Hot Streak proc will letting it be refreshed before getting used and at end of combat will report with number of Pyro casted with number and percentage and Hot Streak gained.
• Timer for Combustion Dot on target.
• Flamestrike tracker supporting regular flamestrike and blastwave Flamestrike.
• Tooltips for option panel settings, no more obscure settings.
• Ignite munching report, so you know how much damage you lost because of buggy mechanics.
• Ignite damage predicter (BETA), instant info of you upcoming ignite damage (check option panel for info)
• Graphical options so you can make it the way you want.
• Localisation in english, deutsch, French and Chinese (feel free to report typos…) (thanks to Hambo and Plueschbaer from MMO-C forums for deutsch version)
• Threshold option to activate color change of background when Ignite cross the specified value.
• Audio warning when ignite value reach the threshold.

CauterizeCooldown :

A simple cooldown showing Cauterize cooldown.

You can change the scale, alpha and Frame level. Also enabled by default a timer like OmniCC/CooldownCount. You can choose to autohide the addon when your cauterize is off cooldown. It will autohide too for classes other than mage. Also feature a customizable warning message which can be outputted to vicinity, party, raid or yell channel. There is also another optional warning when Ice Block is up. You can set whatever SharedMedia sound you want as an alert.

MageBombTracker :

This addon track all the new mage bombs and flamestrike cooldown which will be available in patch 5.0.4 and MoP. It show them with a list which feature :

• current target marker
• target name
• raid marker
• time remaining

Other nice features are :

• Alert when missing a bomb
• Alert when overwriting a bomb
• End of fight report

Fully customisable and lightweight, all you need to monitor your bombs !
Available in English and French for now, submit your translation for more.

------------------------------------------

Changes from 2.xx versions ?

• No more crit debuff tracking, it's gone for mages.
• No more support for FrostFire Bolt, useless for Combustion and i doubt anyone used it.
• No more Impact support, new inferno blast replaced aura procs.

Use Interface Panel -> Addons for full config or /combustionhelper for bringing up directly the option panel.
As always, report me bugs and requests. Don't hesitate to reset it if problems occurs (and reset of bundled addons are handled separately).

Download from Curse at : http://www.curse.com/addons/wow/combustionhelper

You can always get the standalone version of the addons in the links in my signature !

[markdall]

THANK YOU!

Seriously, thank you. <3

[LET JIMMY RAID]

Love you!!!

[Deleted]

Yeah, sincerely thank you for your hard work and effort, its a great addon

[Madruga]

Just in time! I was missing my Combustion tracker on the dummies already =D

Thank you!

[Deleted]

Out of interest (as i've not read up much with 5.0.4) will there be any need / will you be developing MageManaBar further for MOP?

[Deleted]

Out of interest (as i've not read up much with 5.0.4) will there be any need / will you be developing MageManaBar further for MOP?

i'll be maintaining magemanabar in mop but some features will be removed, like mage armor tick monitor, flame orb marker and some more little things. Some others features are still exclusive to it so it'll be still useful.

[Ivalen]

Thanks for the addon update.

Someone correct me - but ignite is always up, is it not, even with non-critical hits by fire spells? So the only DoT missing is the Pyroblast! dot; and you would only want to hit Combustion after a crit Pyroblast!. If that's the case, it is much easier 'to see' when to hit combustion now. (Yes I know you can use regular Pyroblast, but you wouldn't cast then unless you PoM first).

I haven't logged in yet to confirm this. Also, has any analysis been conducted on using Glyph of Combustion or not? Increase cooldown to 90seconds but doubles the DoT.

[Deleted]

Thanks for the addon update.

Someone correct me - but ignite is always up, is it not, even with non-critical hits by fire spells? So the only DoT missing is the Pyroblast! dot; and you would only want to hit Combustion after a crit Pyroblast!. If that's the case, it is much easier 'to see' when to hit combustion now. (Yes I know you can use regular Pyroblast, but you wouldn't cast then unless you PoM first).

I haven't logged in yet to confirm this. Also, has any analysis been conducted on using Glyph of Combustion or not? Increase cooldown to 90seconds but doubles the DoT.

Damn something big slipped from the release, i updated it and version 3.1 should be on approval on curse, thanks a lot for the report. Can't say for the glyph, didn't test dps.

[Zacii]

thanks! so quick!

[Barcasaur]

I have been updating all my addons, and only currently using two that are out of date but having stable game-play conditions, but with the new combustion helper active my frame rate tanks to 14-16fps, even if i have the addon enabled and switch to frost spec for example the fps recovers as long as combustion helper is not active.

got any ideas what could be causing this?

[Soulstrike]

are you able to move mage bomb section of the addon with combustion one seperately??

[Barcasaur]

are you able to move mage bomb section of the addon with combustion one seperately??

Im sorry can you elaborate on what you mean =3

*************
Edit: this fps issue is only happening when i am in Fire spec, and do not have a bomb talent selected, once i set up my fire spec, things are running fine. so idk if you were aware of this minor issue but if you were not now you know =D

Thanks a million for your dedication to the add-on, much appreciation!!

[Jimm3]

No more support for FrostFire Bolt, useless for Combustion and i doubt anyone used it.

Won't ppl be using it now with the new glyph?

[Deleted]

Won't ppl be using it now with the new glyph?

they may but it won't have any relation with Combustion, so no need for me to track it anymore.

---------- Post added 2012-08-29 at 08:58 AM ----------

are you able to move mage bomb section of the addon with combustion one seperately??

set the MageBombTracker position to "Free" in the CombustionHelper option panel

---------- Post added 2012-08-29 at 10:07 AM ----------

Version 3.1.1 is on the way on curse.

[Deleted]

Is it normal that magebombtracker always whines about the fact that I refresh my nether tempest (correct name?) too soon ? Since it doesn't explode like the living bomb, aren't we supposed to refresh it before the last tick ?

[Azatos]

Hey angayelle,

Thanks for getting this up and running so fast. Do you think you could add back in the functionality of seeing an estimated combustion tick, and how many ticks will occur? If not, no biggy...just something I enjoyed. Thanks!

[Deleted]

Is it normal that magebombtracker always whines about the fact that I refresh my nether tempest (correct name?) too soon ? Since it doesn't explode like the living bomb, aren't we supposed to refresh it before the last tick ?

By refreshing it before the last tick, you actually lose a tick, like you're paying X mana for 11 ticks instead of getting 12 ticks for the same price. Not the most effective way to spend your mana. Now you should be able to disable those message by going into the MageBombTracker module option panel and unchecking the refresh button.

---------- Post added 2012-08-29 at 12:43 PM ----------

Hey angayelle,

Thanks for getting this up and running so fast. Do you think you could add back in the functionality of seeing an estimated combustion tick, and how many ticks will occur? If not, no biggy...just something I enjoyed. Thanks!

This should happen but i haven't looked yet into the new combustion calculations.

[Deleted]

By refreshing it before the last tick, you actually lose a tick, like you're paying X mana for 11 ticks instead of getting 12 ticks for the same price.

It's a common habbit among casters to refresh dots before the last tick (Living bomb was an exception among dots because of its explosion).
Dot efficiency is not about mana, it's about uptime. By refreshing it after the last tick you're losing uptime. You don't really care about mana, uptime is what matters.

The best way to refresh arcane bomb -dps wise- is just before it fades (before the famous last tick).

[JohnnyQuest]

By refreshing it before the last tick, you actually lose a tick, like you're paying X mana for 11 ticks instead of getting 12 ticks for the same price. Not the most effective way to spend your mana.

Do we? Because this is not how DOT mechanics are meant to work. Refreshing before the last tick should cause a rollover. Is NT special and not following those rules?