Get an Epic Experience with Premium


Mage Login to Add Favorites
  • World of Warcraft
  • 1,569 Monthly Downloads
  • Supports: 6.0.2
  • 217,930 Total Downloads
  • Updated 10/17/2014
  • Created 03/27/2011
  • 101 Favorites
  • Project Site
  • Comments
  • Release Type: Release
  • License: GNU General Public License version 3 (GPLv3)
  • Newest File: 3.6.0
Support development! **

About myBigIgnite


myBigIgnite has been designed to allow fire mages to quickly decide whether it is worth to trigger their Combustion spell.

To achieve this, the addon display is centered on the amount of damage done by Ignite and provides additional informations around. Addon colour and size is adjusted depending on whether a threshold of Ignite damage is reach and Combustion is available.
Together with this central function, myBigIgnite comes with other features such as a specific timer for Ignite as well as an automatized power bar, a entire module dedicated to providing informations about Combustion, etc.
The addon has a modular structure: every feature can be seperatly activated. It means that it can virtually fit any player preference whether a full or a minimalistic set of information is wanted.


  • Clear display of Ignite damage
  • Ignite timer bar
  • Ignite power bar
  • Combustion module
  • Heating up module
  • Statistics record
  • In game help
  • Autohiding following different conditions
  • Configurable layout that supports sharedmedia
  • Addon activation only in fire spec (and only if you're a mage)

More precisely:

Ignite damages:
Blizzard now transmits tick values through the aura of dots. This allow to fetch the value of Ignite damage even before the tick. The downside is that it is inaccurate when several spells hit the target in a short period of time: all the spells will be incorporated in the calculation for the next tick but the value transmitted by the Ignite aura changes as fast as a new spell lands on the target. To avoid too much confusion, myBigIgnite incorporate a timer that delays slightly the refreshing of damage display, so most of these fast landing spells are absorbed and never reflected in the display. You can turn off this option if you will, but the damage display will consequently be more prompt to change and inaccurate (not badly as this shoudn't lead to an overprediction of the next tick, only a downprediction). You can also keep with the former way of fetching Ignite damage by looking at the combat log, but you loose in this case the advantage of being able to see Ignite damage before the tick happens.

Ignite power bar:
A bar indicating the power of current Ignite tick. This is done by real-time computing your damages. Briefly, it calculates the average and standard deviation of your Ignite damages over a certain amount of ticks. It makes the limits of the bar flexible but still relatively stables and should help you to spot exceptionnal ticks more quickly.

Combustion module:
It is entirely dedicated to Combustion. The module pops each time Combustion is available and Ignite damages are above a threshold. It then shows a predicted amount of total damages for Combustion as well as the number of ticks. If Combustion is triggered it will show its timer, CD and tick damages. The last scrolling information corresponds to the total damage done and shows you the deviation compared to the prediction.

Heating up module:
This module shows when you get Heating up and Pyroblast! buffs. By default, Heating up icon is hidden when Inferno Blast is in CD.


Type /mbi config to access configuration tab or use the Interface button in game options. Type /mbi threshold [value] to set your optimal threshold without using the config panel.
Type /mbi help to access in game help. Type /mbi stats to access your records.


English, French

tag 3.6.0
globule <>
2014-10-18 02:03:06 +0100

- WoD compatible
- new option to show threshold as combustion tick damages


    - -removed irrelevant stuff for wod:
    smooth dmg
        show ignite tick as dps
    - changed way combu tick is calculated to reflect wod changes to Combustion
    - new option to show threashold as combu tick damage
    - help updated
    - new option to display ignite dmg number : auto
    - corrected bug to auto enable addon because of blizz removing ignite as a spell
    - toc to 60000


First Previous Page 5 of 11 Next Last
  • #105

    Is this updated for 5.1? Or does it/is it still tracking the Pyroblast DoT?

  • #108

    just uncheck the tracking pyro option in general tab until I remove it completly

  • #103

    Is there a reason why I don't see the options to change the layout modes anymore like I used to, like the screenshot for the addon shows? I don't seem to have the settings (I have manually installed the addon).

    Last edited by Soulfuse on 10/29/2012 6:45:10 PM
  • #104


    yes it's gone to make room for much more interesting features coming in next releases. But you can still achieve the same result manually at least for the time being

    Last edited by Istaran on 10/29/2012 6:58:25 PM
  • #102

    thank you very much !!!! 

    I own my dps to you :)

  • #101


    if using curse client to update the addon, you still experience a problem with myBigIgnite, please update the addon manually. To do so:
    - logout
    - go to World of Warcraft\Interface\Addons
    - delete the myBigIgnite folder
    - go to World of Warcraft\WTF\Account\YOUR_ACCOUNT_NAME\SavedVariables
    - delete myBigIgnite.lua and myBigIgnite.lua.bak if any
    - download myBigIgnite from curse site (be sure to dl last version => 3.0.1)
    - unzip somewhere, then copy the folder myBigIgnite into World of Warcraft\Interface\Addons
    - login

     Thank you very much, it works! And thanks to that fixed the bug. I love this addon! 

  • #99

    At last!!!

    I'm very happy with returns of MBI. And also prepared for the 5.1. Smile

    Very good job. Wink


  • #100

    Thanks :)

    I've been quite busy with other things these last 2-3 months and had no time for wow related stuff but I'm back now!

  • #94

    After the 3.0.1 update, the issue isn't resolved for me. When I log in, I don't get the "mbi loaded" message, i don't get anything. I've the option to press "config mbi" in the interface > addon > mbi menu, but when I do, nothing happends.



    Swapping specs after this from my offspec frost and back into fire, will prompt the usual "Configuration available only when mybigignite is enabled."

    Last edited by markfoged on 10/22/2012 4:21:16 AM
  • #95

    Do you have a lua error associated with this?

    Also be sure to run the 3.0.1 version, you can tell it by looking at the .toc file in mBI folder. Try possibly to delete the entire folder and reinstal it from a download from curse site.

  • #98

    Good! I'm going to make a note in the description as I think it's related to the way curse client is updating the files.

    Last edited by Istaran on 10/22/2012 6:58:01 AM
  • #97

    I'm sorry I don't understand this issue. I just tried myself to run mBI completly alone, from clean install and it works like a charm, enabling itself in fire spec and disabling itself otherwise. There is nothing wrong with the addon in this case. Maybe you can try to do it manually (uninstall/install), just wondering if curse client could mess a bit around. And delete the mBI files in your saved variables folder as well.

    Last edited by Istaran on 10/22/2012 6:58:45 AM
  • #96

    I'm not getting any popups about errors atleast. And yes, I've already tried uninstalling it via the curse client and reinstalling it.



    I just manually deleted all mBI related files and manually installed it, which corrected the issue. Thank you!

    Last edited by markfoged on 10/22/2012 6:34:01 AM
  • #91

    I get the following error running just mBI and no other addons.

    Message: Interface\AddOns\myBigIgnite\MBIOptions.lua:2021: attempt to get length of field 'igT' (a nil value)
    Time: 10/22/12 18:11:19
    Count: 1
    Stack: Interface\AddOns\myBigIgnite\MBIOptions.lua:2021: in function `?'
    Interface\AddOns\myBigIgnite\MBIOptions.lua:1793: in function `LoadFireOptions'
    Interface\AddOns\myBigIgnite\MBIOptions.lua:2456: in function `ChangeConfigDisplay'
    Interface\AddOns\myBigIgnite\MBIOptions.lua:130: in function <Interface\AddOns\myBigIgnite\MBIOptions.lua:129>
    (tail call): ?
    [C]: ?
    [string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
    (tail call): ?
    ...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:799: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:614>
    (tail call): ?
    [C]: ?
    [string "safecall Dispatcher[4]"]:9: in function <[string "safecall Dispatcher[4]"]:5>
    (tail call): ?
    ...ce\AddOns\myBigIgnite\libs\AceGUI-3.0\AceGUI-3.0.lua:314: in function `Fire'
    ...nite\libs\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:28: in function <...nite\libs\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:25>

    Locals: <none>

    Any ideas what might be causing that? Thanks.

  • #93

    it doesn't make any sens to me as the table which is faulty should be created anyway (this is done during the loading). Are you sure to run the last version of mBI?

  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Star Trek Online Wiki Editing Contest