Traps activating upon expiring have difference than upon being triggered

Hi there!
Currently playing blink/mirror arrow summoner with traps and lots of unstable payload jewels (chance for traps to trigger additional time). In gem/skill/item descriptions there is absolutely no indication about the fact that traps triggered by an enemy or by the Chain Reaction ascendancy would behave different than traps activating when they expire. It seems that goes for not only those particular skills but for all traps.


On expiring traps would never activate additional time. It is like traps activating as such and traps being triggered is different concepts. Please give some clarity about that and if it is not intended please change it - it would open some fun ways to build around.

Spoiler


That also makes using the unique Sunblast Belt by saboteurs actually punishing instead of rewarding.


Last bumped on Aug 31, 2022, 7:11:08 AM
This thread has been automatically archived. Replies are disabled.
Traps have always worked that way with regard to triggering. Well, sort of. In the earlier years of PoE, traps would simply "poof" and break if their duration ran out. But that was changed in like 3.1 or 3.2 for most traps, to allow them to auto-trigger.

Being actively triggered by an enemy and being passively triggered due to expiration are different things. Additional effects that explicitly require being triggered generally won't proc, because there's "nothing there" that caused them to trigger and subsequently affect in the first place.

And yeah, Sunblast isn't really intended for your typical Sabo. It's meant to be useful for trap builds on other classes that aren't so aligned with enemy trigger effects.
I have a pretty good sense of humor. I'm not German.

Report Forum Post

Report Account:

Report Type

Additional Info