Does Burn Proc twice?


Hyperstrike

 

Posted

If you have proc IO's in it can it proc twice? Once at the start and once at the end?


 

Posted

I believe the answer is "no".

Because Burn does a bunch of damage up front, then summons a damage pseudopet to continue the damage ticks.



Clicking on the linked image above will take you off the City of Heroes site. However, the guides will be linked back here.

 

Posted

Quote:
Originally Posted by Hyperstrike View Post
I believe the answer is "no".

Because Burn does a bunch of damage up front, then summons a damage pseudopet to continue the damage ticks.
Thats what I thought, I have someone in game stating otherwise yet in all my hours I have never witnessed it.


 

Posted

There's three ways burn could handle procs. I'm not sure which is used by the game.

1- Both the frontloaded damage (dealt by you) and the DoT (dealt by the pseudopet) have a chance to proc.
2- The frontloaded damage has a chance to proc, but the DoT is flagged to ignore procs.
3- The frontloaded damage is flagged to ignore procs, but the DoT has a chance to proc.

4- It's possible that both are flagged to ignore procs, but that's highly unlikely.

In the cases of 1 and 2, there will be a chance for it to proc when you cast it.
For 1 and 3, there will be a chance to proc when the pet is summoned. If the pet lasts exactly 10s or less, there will be no second proc chance. If the pet lasts more than 10s, there will be a second proc chance on the first tick of damage after 10s has passed.
In the case of #1, there would be a small chance of it proccing twice on cast - for a 20% proc, there would be a 4% chance for a "double proc". Even a purple proc would only have an 11% chance, if it's even possible.

EDIT: City of Data says that the pet lasts 10s. That means that it dies just as the "Don't check for procs" timer runs out. It would need one more tick of damage added to have a chance for a proc on the final tick. That means that any prock checks are made at the beginning. And I think that it's likely that something is flagged to not check, so there wouldn't be a chance for a double proc.


@Roderick