This project is abandoned.

Whether this project is out of date or its author marked it as abandoned, this project is no longer maintained.

If you wish to take this project over, please report it and state your intentions.

A Grid Status module to display HoT/aura information, while allowing much easier aura additions in the near future over the most common module, GridStatusHoTs.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of cheeseman11 cheeseman11 Oct 27, 2014 at 14:09 UTC - 0 likes

    This is a fantastic addon and incredibly useful for resto druids, I would hate to see it not updating for WOD.

    Do you have any plans to update it? I know myself and others out there depend on this addon and I hope you will be able to continue it.

    Thank you and hope to hear from you

  • Avatar of Phanx Phanx Apr 20, 2013 at 00:09 UTC - 0 likes

    Hi everyone,

    I just wanted to drop by and mention that Grid has allowed you to color aura statuses based on their stack count or their duration for over a year now. Since this was the main feature of GridStatusHots, that plugin is only useful now if you want separate statuses for "my Lifebloom" and "others' Lifeblooms". I haven't used GridStatusHotter, but based on the description it sounds pretty similar, so you may want to check out the options built into Grid.

    Just check "Show Advanced Options" under Status > Auras, and you'll see the stack/duration color options appear under each aura status.

  • Avatar of Puri Puri Apr 05, 2013 at 18:17 UTC - 0 likes


    thanks for the addon, with the included mistweaver support I switched over to it.

    But there is one thing I miss: With GridStatusHoTs, I was able at my druid to see the number of stacks of lifebloom on my target with colors (one stack:red, two stacks yellow, three stacks green). In GridStatusHotter it changes it's color depending on the remaining time (and I can see the stack size as text), but I would prefer the color encoding to depend on the stack size. Would it be possible to be implemented?

  • Avatar of gabestah gabestah Jan 30, 2013 at 05:46 UTC - 0 likes

    @wyldphire1: Go

    Thanks for the report! This memory leak should be resolved in the latest release.

  • Avatar of wyldphire1 wyldphire1 Jan 29, 2013 at 08:55 UTC - 0 likes


    First off, thanks for working this mod out. It allows me to track all my Mistweaver monk abilites inside my Grid. GridStatusHots just doesn't quite cut it, unfortunately.

    However, I am asking for some updating on GridStatusHotter... Currently, I have to disable it completely before entering battleground PVP or a LFR/25m Raid. I have attempted to fix this myself SO many times by disabling other addons (including everything but Grid and GridStatusHotter) to solve the problem, but no juice.

    What I'm encountering, is when I enter into a group with a large amount of people, GridStatusHotter skyrockets it's memory usage to the point where I bog down to 2/1 FPS and am ultimately stuck ALT+F4'n WoW. When I say skyrocket, I'm not saying that lightly. This mod instantly blasts up to an upwards of 30mb-60mb of memory usage.

    Right now I am gaming on a 2011 MacBook Pro, I have a Windows 7 partition loaded which I use soley for WoW. The game plus all my mods run like a champ otherwise without a hitch... exept this recent problem. I bet if I were gaming on a souped up PC with 16gb of RAM, an i7, solid state drives, beastly video card, etc. I might just be able to absorb this mods high memory usage. Such is not the case, unfortunately.

    At any rate, I love this mod and I need it to heal successfully on my monk. I'm willing to get in touch with you, if you want, and work closely together with you (email, screenshots, testing, etc.). I'm begging you though, can you make this mod less of a memory hog?



Date created
Sep 10, 2012
Last update
Apr 21, 2013
Development stage
  • enUS
GNU General Public License version 3 (GPLv3)
Recent files
  • A: r9 for 5.1.0 Apr 21, 2013
  • A: r8 for 5.1.0 Apr 20, 2013
  • A: r7 for 5.1.0 Apr 19, 2013
  • A: r6 for 5.1.0 Jan 30, 2013
  • A: r5 for 5.0.5 Jan 30, 2013