If by any chance you happen to show up here again, I have a small feature request.
Currently there's only one 'Blocked' entry in melee damage, could you change that to
Hit Block: $player's $attack hits $target for ([0-9]*)\. \([0-9]* blocked\)
Crit Block: $player's $attack crits $target for ([0-9]*)\. \([0-9]* blocked\)
Full Block: $player's $attack was blocked by $target\.
Special attacks can be a crit and also be blocked (although quite rarely). For normal melee attacks only a Hit Block can occur (and supposedly a Full Block, but currently I don't know the string for this).
Yes, in some way.
Of course you won't be able to do an exact parse, but to examine your damage, deaths, etc. it is useful.
There could be a problem if they have cleared the data already or there's too much time between the first and last kill, as recount drops more detailed data after some time.
If there a file located on in a folder somewhere with historical data stored in it? That I can steal of people that were using it and search it for the data i need?
EDIT: Ok so my friend has the log of our FLK kill last night. I'm jumping for joy. But is there anyway for her to export the data, or transfer it to me? If we group up is there a way to synch the data to my module?
Any help really really appreciated.
EDIT: OK I've got her Recount.lua file .. and smart way to hack into this and graph it all up?
Anyone found a way around the intense freeze on a "/recount realtime raid dps" graph when the raid stops dpsing?
Its fine when everyone starts up and it goes from 0-20k or whichever it may-be, but upon the end of a fight when everyone stops.. and it quickly zooms down from 18000->1800->0 the change of the graph display causes a huge freeze up (similar to resizing it during a fight).