Tattoo of the Dragons Rage Doesn't Stop Combination Attack Reset

Forum where closed and resolved bug reports live
Post Reply
Repinuj
Posts: 26
Joined: Sun Nov 17, 2024 5:02 am

Tattoo of the Dragons Rage Doesn't Stop Combination Attack Reset

Post by Repinuj »

Bitter has Tattoo of the Dragons Rage. It's supposed to stop combination attacks from resetting. It does not.
- You focus your powers on the Tattoo of Dragons Sight adorning your skin. You feel its magic flow through you, improving your ability to anticipate movement and granting you a +5% bonus to all attacks. (2025-02-02 03:42:37).
- (2 times) Imp attacked you and hit for 0 points of fire damage. (2025-02-02 03:42:51).
- You attack Emely Proctor with your Spear and hit for 27 points of holy damage. You started a combination attack! Your rage of the dragon scorches them for 0 points of fire damage! You gain 27 XP. (2025-02-02 03:43:00).
- Imp attacked you and hit for 0 points of fire damage. (2025-02-02 03:43:01).
- The shadows here seem to distort and bend at eerie angles as a chill and eerily soft breeze passes through the area. (2025-02-02 03:43:01).
- You attack Emely Proctor with your Spear and hit for 33 points of holy damage. You dealt 6 more damage from a perfectly executed combination attack! Your weapon was damaged during the attack. It is now less effective! Your rage of the dragon scorches them for 0 points of fire damage! You gain 33 XP. (2025-02-02 03:43:01).
- You attack Emely Proctor with your Spear and hit for 33 points of holy damage. You dealt 6 more damage from a combination attack! Your rage of the dragon scorches them for 0 points of fire damage! You gain 33 XP. (2025-02-02 03:43:03).
- Emely Proctor has exploded in a violent flash of hatred and hellfire, spraying heat and gore everywhere. You take 1 points of unholy damage. 5 characters and/or pets were affected by this attack. (2025-02-02 03:43:04).
- You attack Emely Proctor with your Spear and hit for 27 points of holy damage. You started a combination attack! Your rage of the dragon scorches them for 0 points of fire damage! You gain 27 XP. This was enough to kill them! You gain an additional 30 Experience Points! (2025-02-02 03:43:04).
Pharaoh
Posts: 33
Joined: Wed Nov 24, 2021 3:35 am

Re: Tattoo of the Dragons Rage Doesn't Stop Combination Attack Reset

Post by Pharaoh »

Dragons Rage seems to still be working fine on wards anyway. I took down a 1000 point ward and not once did the combination attack reset.

You attack the ward with your Origami Bow, dealing 22 points of arcane damage. The impact is absorbed with a resounding thud and the ward seems to ripple a bit. You started a combination attack! (2025-02-02 06:06:13).
- You attack the ward with your Origami Bow, dealing 24 points of arcane damage. The impact is absorbed with a resounding thud and the ward seems to ripple a bit. You dealt 2 more damage from a combination attack! (2025-02-02 06:06:14).
- You attack the ward with your Origami Bow, dealing 32 points of arcane damage. The impact is absorbed with a resounding thud and the ward seems to ripple a bit. You dealt 10 more damage from a perfectly executed combination attack! (2025-02-02 06:06:16).
- (10 times) You attack the ward with your Origami Bow, dealing 28 points of arcane damage. The impact is absorbed with a resounding thud and the ward seems to ripple a bit. You dealt 6 more damage from a combination attack! (2025-02-02 06:06:22).
User avatar
Kandarin
Site Admin
Posts: 1467
Joined: Sat Aug 07, 2021 12:10 am
Location: Theater of the Air

Re: Tattoo of the Dragons Rage Doesn't Stop Combination Attack Reset

Post by Kandarin »

There's a hotfix for this now. The issue was an undocumented feature where Dragons Rage combination rollover only applied on mundane, fire or arcane damage types (those eligible for Dragons Strength). This is too limiting for a 90 CP feature and had a direct conflict with Nexal Spark, so it's been adjusted to work on any damage type.

Also there was a bug here where Nexal Spark didn't display "This attack was charged with nexal power!" on a hit, so that's fixed too.

Thanks for flagging this.
Post Reply