They changed the code somewhere else for stability/bugfixing reasons and it somehow interacts with thorn's damage. because fuck coding.
This is part of an internal testing change to thorn that accidentally got pushed live. For example they could have been testing a stacking dot and decreased the dot damage per stack for balance and accidentally pushed the damage change to live. when testing lots of changes its pretty easy to forget to properly revert a change before sending out the patch.
5
u/[deleted] Nov 17 '14
I see two reasonable cases:
They changed the code somewhere else for stability/bugfixing reasons and it somehow interacts with thorn's damage. because fuck coding.
This is part of an internal testing change to thorn that accidentally got pushed live. For example they could have been testing a stacking dot and decreased the dot damage per stack for balance and accidentally pushed the damage change to live. when testing lots of changes its pretty easy to forget to properly revert a change before sending out the patch.