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.
It scans every 2 seconds out of combat, 10 seconds in combat. So things are delayed. I can't reproduce any bugs with aura checks. If you can get me a reproducible case, I'll look into it. (Open a ticket once you do.)
It's fine now, it's a bit on and off. Noticed the same with int/fort, i had both buffs, but sometimes it told me i was missing them (i had the minor versions of them, mark of fortitude instead of prayer of fortitude for example)
Unable to reproduce. I fixed an issue with BoS a while back, please try resetting your profile.
It's telling me i'm missing BoSanc even though there's no prot pally in the raid. Is this normal behaviour? Playing a hunter btw. Also i noticed that it's not possible to find this project page by searching for ''energized'' on the project search box.
All my testing is with embedded.
Weirdly enough, there was no spikes at all when running it disembedded (i even ran the same addons i did when running embedded). Did you try reproducing this when running embedded? I have no idea whatsoever what's causing this, but running disembedded gives me no freezes at all.
You should disembed and profile, that'll let you know for sure if it's my code or the libraries. I'm not able to repro the issue so it'll have to be you doing the testing :) Make sure you use the latest revision of Energized when you do.
Yeah, whatever lib is doing it is spiking 200 CPU/sec though, while profiling. Not running disembedded, but it's either LibTalentQuery or LibGroupTalents as those are both loaded by energized alone (no other addons using them).
That's not Energized, it could be LibGroupTalents or something. I'm pretty sure the issue you described isn't anything Energized is doing. But just in case it is, the latest revision definitely clamps down the number of raid scans it will do.
Edit: To clarify: Energized itself does not scan anyone's talents, ever. LibGroupTalents and LibTalentQuery do this. If performance issues arise out of those libraries, their authors need to be notified.
It was after a fresh relog though (the cache of known casters probably got reset), and maybe it kept trying to scan the raid for talents etc
Hmm, no idea how that could be caused by Energized. I've been away from my raid plenty of times and never had it happen.
I'm working on an optimization right now where the raid scanning will also be put in a throttle. It might fix the issue?
Ok, might have run into an issue. Left the raid halfway through, then got reinvited (after a relog). After accepting the invite, the game locked up for a fraction of a second every few seconds. This might have been because i was in a different zone and Energized was trying to scan the raid for potential buffers, i don't know.
Edit: It's fine as soon as i rejoined the group in the instance.
Actually, I just had a thought. I do have something that can improve CPU usage a bit more outside of combat only. Let me work on it.
I'm just trying to keep the discussion in perspective. You both appear to be expecting the add-on to magically do something with zero CPU time. It's not possible. :)
At this time the add-on is optimized to the best of my ability. If you encounter any reproducible performance issues (reproducible means I can reproduce it — I cannot reproduce the hitching up after combat ends), I will absolutely look into it. I am hoping that deferring the re-register for a few seconds helps a bit. We have to re-register, though, or the add-on would only scan every 10 seconds even outside of combat. That's unacceptable.
Regarding warning times, they are configurable for a reason. :) I am not changing the defaults.
I'm not trying to criticize either, the CPU in combat is actually very low (around 2 CPU with no spikes), so good work on it. It's the first time i've profiled it properly in a 25man raid. Good work, keep it up.
Its been a while since tested/used BuffEnough on my (separate server) test character; it might have changed here. Regardless, its not the length of a boss fight was referring to...its the gap between (some) bosses combined with shorter time period buffs & personal preferences (on level 80s) that may benefit from a shorter default.
EDIT: well, I see you have made a re-register change + some other changes in the latest r68. So thanks :).
The party lag experienced after combat may have been something else. The only system state change between earlier in the day & the party after-combat lag was upgrading Energized. The most extensive (CPU) testing done on it here (solo) was with r67, however. I wasn't calling you out, criticizing the mod or anything similar in my last post. Was trying to provide some constructive feedback for improvement.
It's scanning the raid when it changes. Really, guys, I'm not interested in hearing about every bit of CPU Energized uses.
There are spikes of around 25 CPU whenever someone joins a raid (possibly when they leave too). Nothing major, it probably just caches their talents or something.
Guys, if you want the add-on to actually DO anything, it has to use some CPU. It's not going to get any better than it is right now. Nothing has changed in my scanning algorithms since r53. I experience no performance issues during full nights of 25 man raiding.
BuffEnough default warn time is not 1 minute, it's 5. See line 638 of Config.lua in BuffEnough. 5 minutes is the length of most boss fights. I'm not changing the default.
Energized is not written for players below the max level, nor is it optimized for solo play. I will consider adding additional toggles for your requests, but please be aware that Energized is a party/raid add-on for max level players.
Spikes of 4 CPU is really nothing to worry about, you should only start worrying if it spiked up to 10-15 CPU.
Edit: Didn't realize that this happened when you were solo though. You should test it during a raid or even a random 5man group and then see if the CPU usage is 4-5 times worse than solo. Then it would be an issue ofcourse.