@Tiarz: The combat log provide a source for each spell effect. Addons use that information to attribute the origin of the spell. Clearly the log lists the person the absorb is on as the source of the effect, hence the attribution you are seeing.
In order to understand what is really going on I'd need to see a raw combat log that starts with the effect procing at the healer until it actually procs the shield. Depending on the nature of what is in the log this may or may not be fixable.
@Tiarz: the latest alpha commit should now track this absorb.
@gresyth: are you using some UI package. It seems to me that it may be setting the row height to non-integer values, which is not a recount bug but a bug in that UI package if that's the case.
@Lombra: Hmm, not sure. I think it should be possible but might requires extra leg-work as currently everything is organized around combatant lists. Don't have disposable time so I won't be adding one any time soon. If anyone else wants to take a stab at making one, they should of course just go ahead.
Wowhead no longer provides the spell ids of the actual buff effect. It used to be possible to click on the effect and get its spellid, but no longer. So the second is sadly not what allows tracking of the effect. I'll need the spellid of the actual buff proc which will be different than the spell that causes the proc.
There are numerous settings that help you control aspects of resource collection. For example you can reduce the number of historical battles collected. Some modules can also be deactivated by deleting them from the TrackerModules directory. Also make sure to only collect boss segments and delete data before every raid run. Do not have time-based data collection on unless you want to get very high detail on a specific aspect. It's best to have that off in normal use because it will collect a lot of data.
It may be helpful to let people know which addons you want to keep maintained. If the addon is worthwhile and someone has the time and is interested in keeping it around you are much more likely to find someone than on a blind call for experienced people. Noone knows what they are signing up for that way.
You can use the unit's GUI as table lookup to identify if it's a boss.
Recount needs this feature for boss-based segmentation and since Blizzard at some point changed that some bosses have boss levels and some don't, re-incorporating that information was necessary.
Advantage is that it avoids the need for target unit scanning (which can be slow in raid) as long as there are relevant CLEU events.
It is very likely that what you are seeing here has nothing to do with Recount but rather is a behavior of WoW's reading saved variables. If the data loaded is too large is opts to return an empty table. This really isn't anything that Recount can address.
In general I would recommend resetting data before a raid, and making sure that some of the heaviest data collections (time-based data) are turned off.
I recommend only keeping boss segments and and perhaps lowering "Recorded Fights" setting to something low.
0
@Mitzykins87: Totems are reported as pets.
0
0
*) The deletion popup mid-scenario when members join or leave the group.
*) Fixed the bug with the bossID flag bit missing.
Leaving this alpha for a bit until I get confirmation that it resolved the issues.
0
0
In order to understand what is really going on I'd need to see a raw combat log that starts with the effect procing at the healer until it actually procs the shield. Depending on the nature of what is in the log this may or may not be fixable.
0
P.S.: Latest alpha should have this band-aided. I'll flag this release soonish.
0
@gresyth: are you using some UI package. It seems to me that it may be setting the row height to non-integer values, which is not a recount bug but a bug in that UI package if that's the case.
@Lombra: Hmm, not sure. I think it should be possible but might requires extra leg-work as currently everything is organized around combatant lists. Don't have disposable time so I won't be adding one any time soon. If anyone else wants to take a stab at making one, they should of course just go ahead.
0
0
0
0
0
0
0
http://www.wowace.com/addons/libbossids-1-0/
You can use the unit's GUI as table lookup to identify if it's a boss.
Recount needs this feature for boss-based segmentation and since Blizzard at some point changed that some bosses have boss levels and some don't, re-incorporating that information was necessary.
Advantage is that it avoids the need for target unit scanning (which can be slow in raid) as long as there are relevant CLEU events.
0
In general I would recommend resetting data before a raid, and making sure that some of the heaviest data collections (time-based data) are turned off.
I recommend only keeping boss segments and and perhaps lowering "Recorded Fights" setting to something low.