*Swing timer. This is quite a heavy feature (requires listening to the very busy combat log events), and i think it is more suitable for an independent addon.

How much CPU usage would this use if you were to implement it? Really like this castbar, but as a hunter it would be convenient to have a swing timer aswell. Maybe as a plugin or a lua option (so casual users wouldn't accidentaly enable it and suffer a slight performance decrease).

I'm not sure what you mean. When Putricide casts Malleable Goo, it will warn you what Putricide is currently targeting, so it only tracks up to one target.

I mean the /say warning. On the normal version, 2 people are target by the Malleable goo and it's announced correctly from both persons. However, on heroic (there are 3 Malleable Goo), only 2 persons will do the /say warning, not 3.

Please, just use something else then. You interpret virtual numbers like they actually mean something with obviously no idea about programming or performance measuring in general.

Those numbers are meaningless without context. What does 5 actually mean? It uses 5 CPU per second? wtf defines "1 cpu"? I'm sure you don't know.

If you think Bartender uses too much CPU, just use something else.

/discussion

Well you're right that i have no idea what it actually means. It does end up higher on CPU than Skada though, and that's a damagemeter. I don't mean to take cheapshots at your addon in any way though, i'm just simply reporting what i've seen.

I'm hoping CPU usage will be worked on once you got time for it. Just compared Bar4 with Dominos and Bar4 uses ~4-5 CPU while idle and minimum 15 while in combat. Dominos uses 0 cpu in combat with barely any spikes. This could be because Dominos uses alot of blizzard's code though, so i may be out of line here.

Yes, that's an accepted feature I'm going to work on. See the ticket about the proximity window.

I'm not sure it wouldn't work since I haven't changed anything about detection for a while. Your client would default to English phrases. What version are you using?

I'm allways running the latest version to be found on wowace. so currently v471. I think this started occuring after v468, several of my guildmembers also reported no timers/bars after updating to v468. It's quite random though, so i'll see if it still happens on the raid tonight.

What language client are you using? One reason it would break is if a missing localization caused AceLocale to send an error, causing Blizzard's error handler to break the addon. I may just turn off AceLocale sending error messages since I have a script to submit them. It has caused way too many problems.