Book of Heroes

Suggestion- Stub- DOT Mechanic Revise

Bj_Knows

ModeratorTue Dec 17, 2013 8:32 am
Subject
Suggestion- Stub- Damge Over Time Mechanic Revise

Instead of having Damage Over Time (DOT) do damage every combat second. Have it do damage immediately before every combat action, when another DOT expires and then when it expires.

Ex:
Player A is hit by Poison Cloud DOT
Player B, casts 0.17 sec Reflexive Strike. Before calculating the hit for Reflexive Strike, the client would calculate the damage taken by Player A from Poison Cloud DOT in 0.17 sec.
Player A finished casting Toxic Blade after 0.51 sec. Before calculating the hit for Toxic Blade, the client would calculate the damage taken by Player A from Poison Cloud DOT in 0.51 sec.

When the DOT expired, it would do its final amount of damage.

DOTs would always do damage immediately before calculating a combat action (including Defend).

Since DOT damage is only important immediately before another action is taken (including Defend), this is a good simulation of continuous damage.

This would speed up characters in RPP Races when Monsters are very fast.

This would improve RPP/ Energy in Onslaught.

This would increase the effectiveness of multiple DOTs.

Bj_Knows

ModeratorThu Feb 27, 2014 1:49 pm
EricM wrote:Yeah, i totally understand the frustration behind it, but there really isn't much to fix if it isn't a bug right? It's one of the big side effects of using dots in the first place. Absolutely hate when I start a big attack and a dot triggers and shaves off all but a sliver of health on the enemy before the attack hits. Feels like a wasted attack. But same type of thing going on.

The Legacy of Blades Raid Phase 4 DOT issue, the Onslaught "Damage Bucket" DOT issue and Elixir of Speed vs DOT Issue are effects of checking DOT every 1 combat second. It really ups the randomness of DOTs.

Bj_Knows

ModeratorThu Feb 27, 2014 1:52 pm
A Quick fix would be to change the DOT Timer from 1.0 combat seconds to 0.25 combat seconds or 0.50 combat seconds so it occurs more often.
Not sure if this could be implemented... but what if it was continuous? A bleed of sorts...

Health just saps away continuously at a rate. Rather than 5k damage every 1.00 seconds, 50 damage every 0.01 seconds continuously for the duration of the effect. Would asthetically look cooler, and make timing alot easier.

Bj_Knows

ModeratorThu Feb 27, 2014 2:51 pm
EricM wrote:
Health just saps away continuously at a rate. Rather than 5k damage every 1.00 seconds,
50 damage every 0.01 seconds continuously for the duration of the effect.

If you have an Attack casting time of 0.63 combat seconds, you would see "50" 63 times before your Attack connected severly slowing you down in RPP Races.

Even a Quick Fix of every 0.25 combat seconds, would cause many people to cry "Fire Mages/ Bleed Justicars/ Poison Shadow Walkers got nerfed in RPP Races".
Bj_Knows wrote:
If you have an Attack casting time of 0.63 combat seconds, you would see "50" 63 times before your Attack connected severly slowing you down in RPP Races.

Even a Quick Fix of every 0.25 combat seconds, would cause many people to cry "Fire Mages/ Bleed Justicars/ Poison Shadow Walkers got nerfed in RPP Races".

Good point, didn't even think of the spamming 50s... probably not the best idea then.

It's a tough balance to reach honestly.