Jump to content
  • 0

Secondary damages are not applied after patch 2.0


Question

Posted (edited)

After patch 2.0 applied, I bought the White March and played game. I found that secondary enchant damages are not applied(see the screenshot attached)

 

At the screenshot below, the rogue(names Gunter)'s jolting touch damage should be 88 (71.1+17 burn damage). However, it doesn't have secondary burn damage thus result in only 71 damage.

post-146121-0-09810100-1440749199_thumb.jpg

Edited by Klaus

5 answers to this question

Recommended Posts

  • 0
Posted (edited)

??????????????

 

Dude, it does have it. 71,1 + 17 burn dmg. It's like there in your very own screenshot :p

 

It always showed it like that while floating dmg was a sum of both. Not really sure what to tell you :p

 

the formula is DMG - DR = DMG(post DR) +%elemental dmg to damage that got through DR.

Edited by Killyox
  • 0
Posted

??????????????

 

Dude, it does have it. 71,1 + 17 burn dmg. It's like there in your very own screenshot :p

 

The screenshot shows 71 TOTAL damage (check the line below the pop-up). Klaus is right. It's a bug.

  • 0
Posted

Unfortunately, not the total damage will be displayed (only the primary) until you look with your mouse at the exact result in the combat log. Nevertheless, the total damage inflicted is correct, what you can see by the red values above your target.

post-155839-0-87065000-1440775831_thumb.jpg

post-155839-0-91626200-1440775835_thumb.jpg

  • 0
Posted

 

??????????????

 

Dude, it does have it. 71,1 + 17 burn dmg. It's like there in your very own screenshot :p

 

The screenshot shows 71 TOTAL damage (check the line below the pop-up). Klaus is right. It's a bug.

 

It shows dmg that you did and after substracting DR it adds elemental dmg (which is shown when you mouseover). Total dmg done is correct (the one floating above enemies) and dmg upon mouseover is also correct. 

 

It's just that dmg displayed without mousing over does not include added damage but that damage is still there and was done. IF anything this is UI oversight/glitch or w/e. IIRC it has always been like that.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...