Well, even "quick snapshot" should give you some sane results. But it even counts damage warlocks doing to themselves with Hellfire ! If purpose was to create "very efficient" addon you can make one just with empty .toc. If purpose was to make METER addon that's another story ... Too bad Violation not METER addon in it's current state in too many pve events.
Violation is being developped with a specific goal, if the goal is not your goal, then too bad. There are plenty of alternatives out there and no-one forces you to use this one. Now stop talking down on Violation and the people that code it. Use SWStats please.
If I wish to use Violation as my threat meter, will I be able to publish my threat to KTM users? I know Threat-1.0 has an option for this, but I don't know how to toggle it on/off within Violation. Same goes for reading KTM data.
no option for that in Violation, individual modules don't have options (yet).
[2007/06/28 22:25:28-206-x1]: Violation\libs\Threat-1.0\ThreatLogger.lua:3: AceAddon: AceOO-2.0: Library "Parser-3.0" does not exist.
FuBar-33424\libs\AceLibrary\AceLibrary.lua:100: in function <...nterface\AddOns\FuBar\libs\AceLibrary\AceLibrary.lua:53>
(tail call): ?:
(tail call): ?:
AceAddon-2.0-40905 (FuBar):966: in function `new'
Violation\libs\Threat-1.0\ThreatLogger.lua:3: in main chunk
Install Parser-3.0 standalone for now, once we get the LoD module packs sorted I'll move the Threat modules into a standalone distro.
Is data pollable from BigWigs (like a triggered event) when a Bossfight starts?
If that is the case (and there's also one for when the fight ends, either the simple "Oh my, we're all dead!", or the "boss has been defeated" from BigWigs), then could one not "simply" (can you notice I'm not a programmer? :P ) generate a second table of data at that moment, record data in both tables, then later save the additional table with the Boss' name.
So that at the end of a raidnight, one would have a total view, and multiple single views, per Bossbattle. That's if that is technically possible. :)
It's all perfectly possible, without even needing BigWigs. But the solution needs to be an elegant and efficient one. Data size is not much of a problem. Violation typically grows about 15kib during a 4 hour raid with multiple resets. So it's safe to assume total data collected is around 15kib. (this is with all modules running).
It's just fitting it all in the generic scheme of things in the best possible way. I could hack in the historical data in probably 15 mins or less, but that wouldn't make it a pretty solution.
The only 'feature' I ask for is to make Violation to show correct (from a raid member perspective) data. It's a pity that implementing such a 'feature' is less important then being the lightest, most cpu friendly, whatever addon ever.
Correct is all in the eye of the beholder. We had a discussion about violation and it's collecting of data. It's not changing.
On a side note, the report menu has a few targets now.
really nice work with violation and i prefer it myself over sws due to its "lightweightness"
however what im missing is the ability to report to a custom channel, cause i find myself more than often hanging with the healers in a healing channel and would be nice to be able to report healing in that specific channel.