CWDT - Cast When Damage Taken Support - Bug?

hello foros,

this is one of my most, if not all time frequented to gems and i'm not sure if i'm delusional or there is currently something off about it?

maybe i should have read the patch-notes and it is in there.... but i have not, either way;

"my" CWDT is not triggering spells in order..... i am using icestorm > punishment > temporal chains; RGRR on a Whispering Ice staff.

and all it does is either spam temporal chains and occasionally icestorm, or trigger both together.. but never Punishment...

and if i socket the same gems on my body armour, then all it does is spam punishment...

the whole wiki page has been edited without any context or reference, simply collated cwdt into cws as if the interaction was always similar then links to some random reddit post of a shadow staring at kuduku....

all while the link after said one https://www.reddit.com/r/pathofexile/comments/kyosh1/comment/gjjrwmq/?context=3

literally proves that there was trigger order per item.

not to mention the page having no change of skill interaction from its 2.4.0 update section:

2.4.0 - The spell that is triggered is determined based on the order in which it is socketed, and will cast supported spells in sequence, even across multiple attacks. These items and skills also have cooldowns which limit how often a skill is cast.

Took a quick glance at your character, but I don't see any increased curse limit.

The default maximum number of curses (hexes and marks) you can apply to a single enemy is 1. When you try to apply two different curses, whichever is cast second is the only one that would apply. Trigger skills cast in an order based on where the gems are socketed.



Aside from that, there's also mana costs to consider. If you don't have enough mana to cast all three, then it will cast what it can.

Yep as Jadian is saying, it might be possible that both are casting but punishment is being overridden by temp chains because of curse limit.

You can put triggered skills on your bar, they will be greyed out, and unusable, but you will be able to see when they are triggering.

Looks like you have change your setup now, so hard to say, but if punishment is not triggering at all, like Jadian is also pointing out, it may be mana cost. If the mana cost for the second spell is too high, it might be getting skipped over.

i am fully aware of my curse limit of 1 and i am also fully aware of the relevance of that in the context of CWS....

i am referring to CWDT which is supposed to have a trigger order, but now seemingly doesn't... all while there are no update references to that change, but rather the change inexplicably trying to be broomed under the rug as if CWDT was always a trigger every single linked skill skill.

CWDT allows you to trigger punishment and get hit during its cooldown to trigger debilitate to afterwards override punishment with temporal chains to benefit from reduced expiration rate on debilitate.

this interaction also allows you to have the highest uptime for malediction from curse clusters...

why is this inadvertently being changed? and if it's not is CWDT not currently bugged?

the wiki page is literally posting conflicting information between ;

Multiple triggered skills
Triggers and cooldowns are properties of skills, not support gems or items,[8] and different skills are independent by default. This means that multiple skills granted the same trigger can trigger independently, simultaneously, with their own cooldown(s). Examples of triggers with this behaviour are, among others,

Cast when Damage Taken Support, Cast when Stunned Support, Spellslinger, Kitava's Thirst, Vixen's Entrapment, Null's Inclination.

^__ this section and the fact that the bottom section which references to changes and updates stating 2.4.0;

The spell that is triggered is determined based on the order in which it is socketed, and will cast supported spells in sequence, even across multiple attacks. These items and skills also have cooldowns which limit how often a skill is cast.
These cooldowns apply per-triggered-skill, rather than applying to the trigger gem itself.

----> and no further updates to the mechanics interacting differently in terms of CWDT triggering skills.

i've also taken the freedom to glance through patch-notes and found nothing insinuating even the remotest change to how CWDT works,

but i am not insinuating i may not have missed it.


on the contrary, i would like to, sadly, admit that i'm wrong, but unless given reason to i can not see this as anything else but a bug.

and it's not as if the issue can't be fixed, i am not making this post because i believe my build has been bricked....

if one simply separates each curse over lvl 1 CWS 0% and lvl 1 CWDT 0% then a similar(practically the same) effect can be achieved.... it's just WAY less controlled than simply having an order on CWDT.

which leaves the remaining fact that this change is HUGE, yet unmentioned? blasphemy....

"

sandbagtako#2638 wrote:

CWDT allows you to trigger punishment and get hit during its cooldown to trigger debilitate to afterwards override punishment with temporal chains to benefit from reduced expiration rate on debilitate.

this interaction also allows you to have the highest uptime for malediction from curse clusters...

why is this inadvertently being changed? and if it's not is CWDT not currently bugged?

It sounds like you think that there is one damage tracker on the CWDT, so that reaching the damage taken threshold once would cast Punishment and reset the counter, then meeting it again would cast Temporal Chains. This is not the case.

From the wiki page:

"

Damage counter and trigger cooldown: The Cast when Damage Taken gem itself does not have a counter or cooldown, only spells it supports do.[1] Each supported skill has an internal damage counter that tracks the total accumulated damage taken from hits.

Trigger order: If multiple triggers proc simultaneously, skills triggered follow a set order.

If multiple skills are linked with CWDT, they will trigger simultaneously, not one at a time like you were expecting.

Because they trigger simultaneously, the trigger order does take effect--but that would at best be like 1 server tick between casts, which is not such a large difference that you can expect the interaction you described to work.