03-17-2024, 04:06 AM
(03-17-2024, 03:05 AM)ACuriousGrey Wrote:(03-16-2024, 06:49 AM)Chance Wrote:After looking into it following the most recent reboot, I found two things that I think should be addressed with Chronos. One that I'm certain is unintentional, and another than I think is intentional but I'm going to include it for context, anyways (which is probably part of the reason Neather is taking more damage when using Chronos than not).(03-16-2024, 06:40 AM)NeatherRealmer Wrote: Bug: Chronos DoT is now doing more damage than intended after the last reboot, I was testing against Fatal with a mage. On the low end it can double the total damage of an ability or when you start messing around in the higher numbers the DoT seems to be still amplifying the total damage received to a slightly lesser extent.
An ability which did 4k damage pre-chronos proceeded to do 8k after activating Chronos. Then when testing an 11k average ability it was getting around a 28% damage increase compared to normal.
Relevant Media: Here is a 128 bit Gif of the strange double tick rate. https://gyazo.com/e87cd6f7c2051d6994ec003fd5ff45c5
Another fix will be live in 3-4 hours (when we reboot)
1) The ticks caused by the DoT can each individually crit, along with the initial hit being able to crit (I do not believe this is intentional)
2) The ticks caused by the DoT are affected by DR, meaning that if you have negative DR, the ticks will do more damage collectively than the original hit would have. If you have positive DR, the ticks will do less damage collectively than the original hit would have (but the effect is significantly less noticeable)
There might be something else going on with Neather's scenario because I can't recreate to the the same severity, but I'll test it when I can get more information about it. These two are just the two things I can consistently reproduce.
Additionally, for note for any future bug reports, the 0 that hits first is intended. That's the original damage being turned to zero, and the following DoT = the original damage.
I don't think the fix went live last reboot, will in the morning