Scorching Ray Damage Bug
|
So before heist patch, i was running Tier 16 hall of grandmaster runs to farm some cards. Everything was fine..
Until heist patch got released.. Now i can't even kill the lvl 85 guys in HoGM. Not just that, it's been very noticeable on the Damage difference being way lower than before the patch was released. There must be something wrong with the debuff application on enemies, or just the DoT itself isn't applying the right amount of damage per second during a fight. Also tried it in 1v1 pvp against a guy with 75 fire resist and no HP Regen due to vaal pact. But scorching ray took longer than expected to kill his character. it felt like i was using lvl 1 scorching ray and not lvl 20. My Path of building Total DoT Damage is 180k per second with lvl 20 gem. But it feels like i'm only doing less than 5% of that damage per second. Please take a closer look on this. Thanks! https://64.media.tumblr.com/23b1b4870b0837ddabd1b84ba3fd26f3/106ec0d8f3d2610d-4a/s540x810/eb5db47e1fb5f65dcf7f253ba6d4cd125b08f92d.gifv Last bumped on Sep 23, 2020, 6:06:11 PM
This thread has been automatically archived. Replies are disabled.
|
|
|
HoGM has pvp scaling applied to player's damage.
SR had that much effective pvp damage only because of the scaling bug. The bug has been silently (finally) fixed with 3.12 patch. The pvp damage scaling constant (T override) for the skill hasn't altered yet and so the skill deals (close to) zero pvp damage. So far you have to use Block Chance Reduction support with a decent hit-based build or a different skill other than SR that ignore pvp scaling. Or you may wait for the promised "pvp balance patch" Problem: impostor syndrome Solution: nerf everything Result: depressing mess Last edited by a_z0_9#4860 on Sep 23, 2020, 5:21:31 PM
|
|
" Thanks for your report, this is intended. There was a bug with Scorching Ray in PvP where every stack after the first WASN'T being scaled which would have resulted in significantly higher damage output than intended when in an area where PvP scaling was enabled. |
