CombustionHelper

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.

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. Previously bundled with CombustionHelper, it's now available as a stand alone addon. 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.

Donation is totally optional but all funds will be used to buy chocolate for my wife so she'll be a bit less mad at me spending so much time coding.

Release 3.5.2
TOC update
Fix for combustion nerf

Release 3.5.1
TOC update

Beta 3.5
Italian translation for Combustionhelper main module
Moved all the code related to magebombtracker module, hopefully fixing bugs
Fix for other character than mage interface bug
TOC update

Release 3.4
Added option to hide pyroblast and Bomb tracking in main window
Fix for 5.1 combustion formula
Fix for zoning spam
Fix for chinese languages (beware using may freeze your computer for a min the first time)Release 3.3.1
Fix for 5.1

Release 3.3
Added pyromaniac warning (red background by default)
Added Heating Up warning (yellow background by default)
Fix for MageBombTracker disappearing in arcane/frost spec
Fix for Ignite triggered from other mages
Added support for Combustion glyph in predicter
Disabled refresh warning when refresh just before last tick of bombs

Originally posted by Hiker It would be great if CombustionHelper would only show during combat and hide itself when out of combat. That way it would only be visible on my screen when I actually need it.

Originally posted by Codex It would also be cool if you could display a number in the corner of the box that shows how much combustion will be ticking for

this is on the todo list but there is 2 possibilities : report damage after combustion is cast or calculate it by checking the dots on the target. The second option is not very accurate because it can't take in acount the potential criticals of the combustion dot but it could be a good information, yes.

Originally posted by Taroven Yep, doesn't matter too much with an indirect call. You don't need the info for both, since the name is the same between the two. UnitDebuff will get the same info either way.

Edit: Little note if you're planning on adding glyph support, the API doesn't usually have glyph info available immediately after entering an instance. You can get around that by checking via LFG_LOCK_INFO_RECEIVED, ZONE_CHANGED_NEW_AREA, and ZONE_CHANGED_INDOORS. Send me a PM if you want some example code. (I don't use the addon myself, kinda happened upon the comments here on a whim, so I probably won't be keeping a close eye on anything further)

i thought about using the name and unitdebuff but i'm not sure the name will be the same in each language, hence the use of spellid, and then the need to keep track of both spellid. anyway it works, so...

about the glyph i was planned to have a glyph check at start in my onload function and then to check the glyph change with event check like glyph-update but i'll have a look at your code for sure.

Originally posted by oldchap32 unfortunately blizz used two spellid for the casted and proc version of pyroblast dot... and they refresh each other. But yes i finally used getspellinfo to avoid the hassle of localization...

Yep, doesn't matter too much with an indirect call. You don't need the info for both, since the name is the same between the two. UnitDebuff will get the same info either way.

Edit: Little note if you're planning on adding glyph support, the API doesn't usually have glyph info available immediately after entering an instance. You can get around that by checking via LFG_LOCK_INFO_RECEIVED, ZONE_CHANGED_NEW_AREA, and ZONE_CHANGED_INDOORS. Send me a PM if you want some example code. (I don't use the addon myself, kinda happened upon the comments here on a whim, so I probably won't be keeping a close eye on anything further)

Originally posted by Taroven A better solution to using the spell name and icon directly is to find it via spellID.

Code:

local pyro,_,pyrotex = GetSpellInfo(92315)

Repeat as needed for other spells. This can be done once during the addon's initialization and repeated for other spells as necessary. After they're set you can use UnitDebuff(pyro) to find the info you need.

This cuts down on the rewriting needed when changes happen, and has the added benefit of automatically localizing for non-ENUS users.

unfortunately blizz used two spellid for the casted and proc version of pyroblast dot... and they refresh each other. But yes i finally used getspellinfo to avoid the hassle of localization...

Originally posted by oldchap32 i still believe the Pyroblast! is a bug <snip>

A better solution to using the spell name and icon directly is to find it via spellID.

Code:

local pyro,_,pyrotex = GetSpellInfo(92315)

Repeat as needed for other spells. This can be done once during the addon's initialization and repeated for other spells as necessary. After they're set you can use UnitDebuff(pyro) to find the info you need.

This cuts down on the rewriting needed when changes happen, and has the added benefit of automatically localizing for non-ENUS users.

Originally posted by Dukes The size of each dot or a total dot size would be pretty cool too :P
Might be pretty hard though.
you also now need to add "!" after the 3 times Pyroblast is in the code :P

i still believe the Pyroblast! is a bug, this information has yet to be confirmed on beta forums so this is scheduled for later.
About the size of the dots, i plan to add a stack counter for FFB and the final size of the combustion dot generated for information purpose but i don't really see the use of each dot size.
The only reason i could see if to have the most important dot before using combustion but i don't think you will delay using it a lot to build the biggest dot you can..

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.