Skada Damage Meter

489 - Greater Blessing of Might attribution

What steps will reproduce the problem?
1. Group up with several retribution paladins (2 or above), and several non-paladin members
2. All retri paladins place their Greater Blessings of Might (GBoM) on non-retribution dps specced palyers, in a way that those players will end up having several GBoMs from different paladins at the same time (say player X will have GBoM from paladins A, B and C)
3. All players deal damage
4. Look up retribution paladins damage done details on how much damage GBoM did on skada after fight is over.

What is the expected output? What do you see instead?
 Expected output: all paladins have their GBoM damage registered appropriately
 Real output: damage attribution to buff owners from GBoM is messed up. GBoM damage is attributed to wrong owners, different players may even see different results and paladin positions on damage done. Today I even had skada attribute other paladin's GBoM damage to me, even though I was outside the raid (I buffed ppl, killed a boss, went outside, they pulled next boss, I was on damage meters while sitting outside the raid).

What version of the product are you using?
1.5-11

Do you have an error log of what happened?
There are no errors as per lua errors.

Please provide any additional information below.
A little info on how GBoM is supposed to work and does work on warcraftlogs for example (it doesn't experience skada's issues).
GBoM is a buff placed on a player, that adds a 10% chance to all their attacks to deal 30% additional Holy damage. This damage is then attributed to a paladin that buffed that player. This way paladin that buffed 3 other players gets 3 additional damage done sources in form of those players. Several paladins can buff same target and all 3 can benefit from it.

User When Change
NomadDC Oct 02, 2016 at 21:27 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 1 comment
  • Avatar of Zarnivoop Zarnivoop Oct 29, 2016 at 14:55 UTC - 0 likes

    Could you supply a combat log of this in action?

  • 1 comment

Facts

Last updated
Oct 21, 2016
Reported
Oct 02, 2016
Status
New - Issue has not had initial review yet.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
2

Reported by

Possible assignees