This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What is the expected output? What do you see instead?
Their damage or other effects should be attributed to the Enhancement/Retribution player
GBOM damage should record as paladin dps even if cast on a ally
http://us.battle.net/forums/en/wow/topic/20742764120
blue post :
Posted by Celestalon
Stormlash and Greater Blessings are indeed intended to be numerically valuable contributions to group success from Enhancement and Retribution (part of their fantasy is in buffing their allies). Their damage or other effects should be attributed to the Enhancement/Retribution player, as far as contribution to the group's damage goes. We'll ensure that the combat logging events are there to allow this to be done.
What version of the product are you using?
7.0.3
Please provide any additional information below.
maybe help you :
http://us.battle.net/forums/en/wow/topic/20749046025?page=7:
10/08/2016 10:52 AMPosted by Superwet Do damage meters show the blessing of mights we have on others as our own dps, or does it just add to theirs
depends on the meter (recount doesn't) and how many other paladins are in the group... If you have many Rets, the damage meters like to lump all the BoMs onto one paladin... One of the many reasons it should just be removed from the game.------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
http://forums.combatlogforums.com/t/logs-and-damage-meters/796
as i see wcl details and skada find a way(not fully) to fix it even if can do that it's good
pls at least fix it for 7.1 bcs 10-40% of our damage coming from placing 3GBOM on high dps party members
The problem is that it can't be properly fixed. Skadas method works nice if there is only 1 ret paladin and only 1 enh shaman in the group but it becomes a mess if there is more. Mainly thats the reason Recount did not implement this fix, and waiting for 7.1 to see if Blizzard manages to fix the combat log itself.
To post a comment, please login or register a new account.