The Squire strange interaction with triggered skills
|
I was trying to play a trigger build so I tested the concept with how many trigger I can achieve with one attack, and I found a weird bug when you socket a trigger support in the second slot of the Squire.
I have 6 triggers that should trigger in 1 attack 1. Fiery Impact 2. Fire Burst 3. Fissure 4. Call the Pyre 5. Void Shockwave 6. Prismatic Burst However, when I socketed all of them in the mace + the Squire, a trigger support that socketed in the second slot of the Squire will not work. https://youtu.be/vRbHup6mflQ In the video I swapped three trigger support gems, and the one I socketed in the second slot of the Squire will stop working. -------------------------------------------------------------- Then I tested further and found another, even weirder bug. Pyre Support will trigger Call the Pyre on melee hit against ignited enemies, but if I socketed Fissure on the second slot of the Squire (which will make it not work, as I said above) a melee slam will trigger Call the Pyre instead of Fissure, even when the skill wasn't hitting ignited enemies, or hitting any enemies at all. https://youtu.be/lU5rholeBVA ---------------------------------------------------------------- At first I thought this weird bug was because there are hidden limit of how many trigger one attack can do, but then I tried socket all the skills in body armour instead (Volcanic Fissure of Snaking - Fissure - CDR - Pyre - Shockwave - Prismatic) and when I attack with VFoS, all 6 trigger supports trigger normally (both Fiery Impact and Fire Burst are trigger on hit), so I think it's not a trigger problem but rather the Squire bug. Also, this second slot Squire bug will not happen if there is only 1 trigger support, for example, only socket VFoS in the mace and Fissure on the second slot of the Squire without any other trigger support will still make Fissure funcion normally. Last bumped on Apr 25, 2026, 1:56:27 AM
|
|















