Energized
Inspired by the now discontinued add-on BuffEnough, Energized answers the simple question: "Am I buffed?" Energized functions as a LibDataBroker (LDB) feed whose icon changes depending on your disposition. The tooltip lists which buffs you're missing, along with who is likely to be responsible for the buff. Energized is optimized for max-level players, and primarily focuses on PvE (but also supports PvP content).
Features
- Smart buff grouping. Energized uses a very flexible grouping system that lets it handle all equivalent buffs and consumables in the game, with room to grow as more become consolidated.
- Low resource usage. Energized has been written for efficiency. It uses very little CPU time (particularly during combat) and very little memory. The configuration UI can be loaded separately for even more savings.
- Highly configurable. Every single buff and consumable rule in Energized is exposed to the user through an advanced configuration system. This gives you a visual display of exactly what is being checked, and lets you configure absolutely everything.
- Advanced tooltip. Energized uses a two-level tooltip, letting you mouse over any missing buffs to see all the people who could be providing them, and which buffs or consumables make up that buff group.
- Understands your needs. Out of the box, Energized contains smart defaults for your class (and in many cases, your spec). Like to change specs a lot? Energized knows when it happens and automatically adjusts.
- Quick disable. Don't care about a buff at the moment? Click it on the tooltip to disable it for this session. Joining a new group, reloading your UI, or logging out will enable it again.
You should also install
- Energized works best with an LDB display like Fortress, Button Bin, or Titan Panel. If you don't have a display, turn on Energized's minimap icon. There are lots of displays available — if you don't like one, try another!
- AddonLoader is highly recommended. This will let you keep the configuration UI unloaded until you need it.
Comments, bug reports, discussion
Help translate Energized
Click here to help translate Energized into your language.
Frequently asked questions
Does Energized require any configuration to work?
Nope! Energized is intended to work perfectly for the majority of players without any changes to configuration. Should you wish to dig deep, however, you can change literally anything about how Energized operates, including every buff and consumable it looks for.
Why is Energized slow to react when things change?
Energized has been written for maximum efficiency when it comes to CPU usage. It won't scan anything more frequently than once every few seconds (configurable). Certain types of actions (like changing your pet's attack mode) won't be picked up until Energized does it's automatic scan, which occurs every 10 seconds. In general, it'll just be a moment before Energized catches up. Just be patient — your framerate is better because of it!
Energized doesn't work very well for leveling. Why?
Energized is not intended to be used by leveling players.
How can I use different options for different specs?
In your Interface Options menu, click the + next to Energized, then select Profiles. Use this screen to create two profiles — one for each spec. Put yourself in the profile you want for your current spec. Then turn on Enable dual profile and select a profile to switch to when you change to your other spec.
300 seconds seems to be fine, most of fights are longer than 5mins isn't it?(I'm talking about raiding, not random pug heroics)
Nice to see it :). A few things before testing of it (all comments below refer to r67).
You have an Opt. Dep. in the TOC for ChatThrottleLib, but the mod doesn't reference it.
The 300 second default warning time for buffs going away is (IMHO) too long. BuffEnough's was 1 minute. I liked 180 seconds. 120 seconds may be a reasonable default compromise.
The durability slider should have an on/off checkbox. If moving it to 0% really does completely disable that check, it should be shown that it does. Similarly, the "Equipment/Not Equipped..." LDB/minimap button warning should have an on/off checkbox.
Noticed the second one on a low level alt I use for testing. Showed I was missing "8 items". For both, no need to use up resources checking for something a user might not want to check for.
Finally, an unfortunate development. After noticing one of my main characters lagging a bit on occasion (particularly immediately after combat) when earlier in the day they didn't, went onto the test character. Libs disembedded (LibBetterBlizzOptions not present, Ace3 r958, LibDualSpec-1.0, LibTalentQuery-1.0, LibGroupTalents-1.0, the other ones don't ever use CPU time), OptionHouse with CPU profiling enabled. And of course, no mousing over the LDB display for Energized (which usually increases the CPU usage of most mods).
The complete Ace3 r958 uses a median of 0.825 CPU/second continually & never spikes on its own. Every 10 "ticks"/seconds when out of combat, CPU usage for Energized spikes to (a median of) 1.75 CPU/sec., Ace3 (Energized using it) spikes to 3.2 CPU/sec. & LibGroupTalents "spikes" to 0.011 CPU/sec. for a total net spike level (excluding Ace3's base value) of 4.14 CPU/sec.. Which is quite high. "Spike" meaning it goes up to that and less than a tick later, they all reduce to their base values. 10 ticks/seconds later, it repeats.
In combat (fortunately), it appears to completely shut its scanning off (with "Keep scanning slowly in combat" disabled); no extra CPU is used.
Immediately after combat, though, it also consistently spikes the CPU usage. Its not on a "10 tick" timeline, it happens immediately after combat is over. Energized spikes to 0.030 CPU/sec. and Ace3 (Energized using it) spikes to 1.4 CPU/sec. for a net extra total of 0.61 CPU/sec.. Not much, but if that amount is added to in parties/raids (unable to test this there), it could be something.
BuffEnough r95 (solo): 0 CPU (through itself or disembedded libraries) when idle at all times (no spiking), 0.0-0.002 CPU/second in combat (unnoticeable). It does spike immediately out of combat to 0.7 CPU/second, though.
I first noticed the party lag spiking in particular with the latest alphas of Energized immediately when combat ended. Hope you can do something about the out of combat CPU usage.
Check out r65. Click any buff/consumable rule group in the tooltip to disable it for this session. Joining a new group, reloading your UI, or logging out will enable it again. I think this is a hot feature, one that I'll use a lot. Thanks for the suggestion.
Looks like tickets were disabled. This should be fixed now. However, please continue to use the comments here until this gets into beta/release. That way we can all contribute to the discussion in a more centralized fashion. Thanks!
This and the Vigilance issue should be fixed in r63. Next time you see an expected buff that you didn't expect (haha), don't forget to mouseover the tooltip to see why exactly it wants it. You would have seen that it wanted you to give yourself Battle Shout, which I removed in r63. I'm just mentioning it because it could potentially make troubleshooting easier down the road.
As always, when I mess with the out-of-the-box defaults, your profile might need a reset. The Ace3 defaults system is a teensy bit buggy with my multi-layered options table.
I'll work on the click-to-disable functionality, but I may not have time today for it.
r62, that issue is gone.
But..despite having Blessing of Might as priority #3 in the Paladin blessings panel, it shows it being "Expected" on the Protection Warrior when he's solo. Blessing of Kings & Sanctuary have higher priority, but are not mentioned. Also shows Vigilance being "expected" when solo.
Reset the profile, it didn't change those issues. Might need better detection of when in a party/raid vs. solo; haven't seen blessings being called for when solo (if you are not a Paladin) with BuffEnough.
That works too, sounds good. Whichever is easier to implement. Brought up the clicking as a universal option that could work for examples other than what I brought up for casters (i.e. Might vs Battle Shout).
I am unable to reproduce this. Try again with the latest revision.
I'll look further at BankStack when I get more time. What about just clicking the Missing buff in the tooltip to temporarily disable the check for this session? This could apply to anything, not just blessings.
Ticket page works for me. Possibly a temporary wowace.com problem.
Atm the ticket page shows 403 for me. Do I need something to be able to post a ticket?
No it didn't remove the Defensive warning. I was solo (not in a party/raid), tested several times. Made sure the LDB display update time had passed on each occasion.
I know how LibDualSpec works; forgot it was included in the embeds. Not elegant, but it works.
The most elegant solution I can come up with quickly for the blessing issue: some sort of limited selection click combination on the LDB display to enable or disable each of the four blessing priorities (as a click selection code example: BankStack).
Yes, checking for in-combat overrides isn't really viable. But the problem is far more prevalent than an edge case, at least for most people. It happens more frequently in 25s than 10s due to the higher likelihood of resto & elemental Shamen being in the raid, of course. But in approximately 75% of total raiding here, it comes up.
And as you say, no, its not the only problem. But in 2 years of using BuffEnough, the Blessing of Wisdom/Mana Spring Totem issue is the only current problem within its functionality that consistently creates hassle.
Setting different blessing priorities for different raid sizes (as this now allows) would only work if you ran with a constant 10 group (or 25) that never changed members. That's "harder core" raiding, which the majority of WoW players do not do.
Thanks very much for your reply.
Zidomo: You said (in regards to Defensive Stance):
Unchecking the option should have removed the warning. Did it not? I just checked the code and I don't see any issues with the toggle at least. I already fixed it to just check your spec (not oRA).
Zidomo: One thing you might not be aware of: Energized can differentiate between 10 player and 25 player raids (and heroic vs. normal raids). It doesn't do this out of the box, but you can use the Advanced tab to set your normal Blessing priority for 25 man, and create a second set of priorities for 10 man. This would work if you raid with a stable 10 man. I can write up a walk through of how to do this if you can't figure it out (hint: you have to create duplicate groups of all the blessings you want).
Regarding BoW: You can add Mana Spring Totem to the BoW group if you wish. This won't really solve the problem very well, though, because the shaman won't be dropping the totem until you're in combat already. I'll think on the problem, but I don't think there's an elegant solution. It really is only a few clicks to change your blessings, and this is a bit of a corner case. 10 man raids are very different from 25 man raids; BoW isn't the only problem. Almost every 10 man equivalent buff is given in combat only (totems/shouts), so it can't be checked pre-pull.
You aren't understanding how dual spec profiles work. Go to the Energize Profiles screen and create two profiles, one for each spec. Tell it which to use for which spec and it will switch profiles when you switch specs. This is standard LibDualSpec, I don't do anything special here. Edit: I added this to the FAQ above. Let me know if you still have questions.
Defensive Stance also requires you to be a designated tank at the moment. Not really sure why, since it's checking your spec. I'll remove that requirement.
Great. A few final things.
The biggest issue here with BuffEnough: the giant hassle it was to disable Blessing of Wisdom warnings/reporting when in a raid with a shaman who would (for sure) drop a mana totem. Ended up usually not bothering at all and putting out to raid chat what I was missing the buff...and people giggling ;).
What would be nice to see in Energized: a way to temporarily/quickly disable a particular blessing assignment (i.e. click combos on the LDB display, etc.). Sure, it may not seem a lot to go into options and switch things around as it is now. But in fact it is. Any time that occurs, remembering to set it back for the next raid never happens.
Related to the above, there doesn't seem to be a method to set two different blessing spec profiles for when you change specs (as a dual-spec character). Set it on one spec, changed spec, set up blessings differently on that spec, changed back to original spec, the blessings remained the same.
Finally, with r60 on a level 74 Warrior (Protection speced), one of the Special Cases options didn't appear to work properly. Despite having a nearly full Protection tree spec and "Check Defensive Stance" checkmarked, it still put up a warning in the LDB display about "Defensive" being "unexpected". Unchecking that option did not change things.
Gwelican: Currently Energized doesn't check your role in a random dungeon. Let me look into that, I can probably get that working better. Thanks for your feedback, and hopefully you let the Button Bin author know to update LibJostle (it was broken in 3.3.5).
Zidomo: Correct — when you turn off "Keep scanning slowing in combat" it becomes completely and totally inactive during combat unless you mouseover/out of the LDB icon. Everything restarts when you leave combat. The mouseover is basically your way to manually run a check during combat even with it turned off. The mouseover is a slave to the 2 second rule — you can never ever run a scan more often than two seconds for any reason.
Haven't tested it in combat in a party/raid with CPU profiling active yet (as I can't play here with the framerate slowdown). But wanted to know: if you have the in-combat scanning unchecked/disabled on the first options tab, does it do the per-10-seconds scanning (or any other scanning) at all in combat? Or is it completely inactive, restarting automatically after combat?
Stances are working properly.
Dk module looks cool. On my lock I checked weapon echants that looks cool as well, one thing to mention:
Buttonbin is a bit outdated, at least libjostle(if you ever encounter a problem that energized doesn't show up in your buttonbin, manually update your libjostle(http://www.wowace.com/addons/libjostle-3-0/files/31-r50/))
Thanks a lot Allara
Update: Did a random dungeon with my dk as a tank, and it was saying i should use blood presence, random dugeon works differently than the raid frame?
Reporting to raid/party/whisper has been added in r60. I've tested it limitedly. Check it out and let me know what you think. Make sure to check out the new options at the bottom of the General tab. By default, Energized won't report pet issues or unexpected buffs, but you can turn these on.
At this time, Energized is feature complete according to my design plan. If you have any suggestions, now's the time. In particular, I need experts of every class to certify the defaults. I'm a hunter, and I certify that class. :D
Zidomo: Various refactoring I'm doing keeps breaking consumables, sorry about the issues. r59 should fix consumables again (no guarantees I won't break them again later, please report if they stop working). Let me know if that works as expected now.
I changed the Armor as you suggested. You may or may not need to reset your profile to see it.
Blessings should be working. Can you check your Advanced tab, your Blessing of Wisdom group, the Blessing of Wisdom rule, and verify that Priority (me) is set to 2?
As you can see in my NYI list above, the reporting feature is still in progress. Thanks for testing and continue to let me know what you discover.
Good work. No CPU used when idle (tested with OptionHouse & disembedded libs). Still needs a channel output (i.e. via a Sink-2.0 output, etc.) to become a full replacement for BuffEnough, but nice work so far.
A couple of problems in alpha r54, though. It never shows Well Fed being missing when solo or in a party (or raid), despite it being selected as an alert (by default), as well as selecting "Solo", "Party" & "Raid" in the General tab. Always shows "You are energized" in the LDB display. The prior r44 tested here had no problem alerting to Well Fed being missing in the LDB display.
Other missing buffs (Mage armor, etc.) show up properly in r54, though.
Also, despite changing the default Paladin blessing priority on a Mage (put Blessing of Kings #1, Blessing of Wisdom #2, Blessing of Sanctuary #3), it called in the tooltip that I was missing Wisdom (with a single Paladin in a 10-man raid and I had already received Kings)
Finally, would be nice for the "Armor" in the LDB display to be changed to "Mage Armor" or similar. Showing "Armor", the first thing I thought of was my equipment, not the spell.
Blubibulga: Soul Link added, untested. Let me know how it looks.