'Trigger a socketed spell' bugged

Crafted the 'trigger a socketed spell when you use a skill with an 8 second cooldown' on my weapon, yet a lot of skills were not actually triggering it.

Ran an entire map where my main skill, spectral shield throw, was not triggering it, nor was a different skill I had, hydrosphere. Yet placing my totem / shield charging did trigger it.

For some reason, this was fixed when I placed lightning strike instead of spectral shield throw in my setup. Was able to put back SST and now everything triggers it like normal.

So, something was preventing the craft from working correctly for awhile, even after I had changed zones / ran a map.
Last bumped on Sep 8, 2021, 3:00:25 AM
Little confused on why this was moved out of Bug report? What I described was clearly a bug with the trigger mod.

But okay.
Do you have enough mana for the hydrosphere to be casted after using sst? Trigger spells have like a 1.5 mana multiplier now and the cost needs to be paid to spit out the spell
Trigger a socket skill seems to be buggy in some ways for me too.

I have a B-G-B convok. wand with "trigger a socketed skill" crafted on it, and Spirit Offering/Desecrate/Despair socketed on it.

While constantly moving, sometimes (but not always), Spirit Offering casts say a couple/few times, and then doesn't cast anymore, no matter what. I'm left with the combo Desecrate/Despair, until I stop moving.

While staying idle, the 3 spells cast normally one after the other, no problem.

I tried to find a way to make this issue happen every time (like starting moving with Despair casted first), with no luck so far.

I wonder why the sequence goes wrong sometimes as it seems to be kinda random, which is a GGG thing, but in this case, it's not supposed to be.

Any thoughts?
"
Bleu42 wrote:
Crafted the 'trigger a socketed spell when you use a skill with an 8 second cooldown' on my weapon, yet a lot of skills were not actually triggering it.

Ran an entire map where my main skill, spectral shield throw, was not triggering it, nor was a different skill I had, hydrosphere. Yet placing my totem / shield charging did trigger it.

For some reason, this was fixed when I placed lightning strike instead of spectral shield throw in my setup. Was able to put back SST and now everything triggers it like normal.

So, something was preventing the craft from working correctly for awhile, even after I had changed zones / ran a map.
"
Holyman1170 wrote:
Trigger a socket skill seems to be buggy in some ways for me too.

I have a B-G-B convok. wand with "trigger a socketed skill" crafted on it, and Spirit Offering/Desecrate/Despair socketed on it.

While constantly moving, sometimes (but not always), Spirit Offering casts say a couple/few times, and then doesn't cast anymore, no matter what. I'm left with the combo Desecrate/Despair, until I stop moving.

While staying idle, the 3 spells cast normally one after the other, no problem.

I tried to find a way to make this issue happen every time (like starting moving with Despair casted first), with no luck so far.

I wonder why the sequence goes wrong sometimes as it seems to be kinda random, which is a GGG thing, but in this case, it's not supposed to be.

Any thoughts?

Have you checked whether you have enough mana to cast all the socketed spells?

Since 3.15 triggered spells still require paying their mana cost with the only exceptions of Mjölner and Cast on Death, so if you reserve most of your mana you simply might not have enough to trigger a high level Spirit Offering / Hydrosphere.

This explanation would be consistent with the skills triggering when you use low cost skills like placing a totem / using Shield Charge with few linked support gems.

Lightning Strike does have a lower mana cost than Spectral Shield Throw, though I cannot speak to the consumption per second without knowing the attack speed of your build for both skills.
"
DER_PSYCHOPATH wrote:
"
Bleu42 wrote:
Crafted the 'trigger a socketed spell when you use a skill with an 8 second cooldown' on my weapon, yet a lot of skills were not actually triggering it.

Ran an entire map where my main skill, spectral shield throw, was not triggering it, nor was a different skill I had, hydrosphere. Yet placing my totem / shield charging did trigger it.

For some reason, this was fixed when I placed lightning strike instead of spectral shield throw in my setup. Was able to put back SST and now everything triggers it like normal.

So, something was preventing the craft from working correctly for awhile, even after I had changed zones / ran a map.
"
Holyman1170 wrote:
Trigger a socket skill seems to be buggy in some ways for me too.

I have a B-G-B convok. wand with "trigger a socketed skill" crafted on it, and Spirit Offering/Desecrate/Despair socketed on it.

While constantly moving, sometimes (but not always), Spirit Offering casts say a couple/few times, and then doesn't cast anymore, no matter what. I'm left with the combo Desecrate/Despair, until I stop moving.

While staying idle, the 3 spells cast normally one after the other, no problem.

I tried to find a way to make this issue happen every time (like starting moving with Despair casted first), with no luck so far.

I wonder why the sequence goes wrong sometimes as it seems to be kinda random, which is a GGG thing, but in this case, it's not supposed to be.

Any thoughts?

Have you checked whether you have enough mana to cast all the socketed spells?

Since 3.15 triggered spells still require paying their mana cost with the only exceptions of Mjölner and Cast on Death, so if you reserve most of your mana you simply might not have enough to trigger a high level Spirit Offering / Hydrosphere.

This explanation would be consistent with the skills triggering when you use low cost skills like placing a totem / using Shield Charge with few linked support gems.

Lightning Strike does have a lower mana cost than Spectral Shield Throw, though I cannot speak to the consumption per second without knowing the attack speed of your build for both skills.


It wasn't mana cost related, because I was able to swap my SST for another skill, then have the trigger work, then swap BACK to sst and suddenly it worked fine.

I've only encountered this bug once though which was at the time of my last post here, and haven't seen it since.
"
Holyman1170 wrote:
Trigger a socket skill seems to be buggy in some ways for me too.

I have a B-G-B convok. wand with "trigger a socketed skill" crafted on it, and Spirit Offering/Desecrate/Despair socketed on it.

While constantly moving, sometimes (but not always), Spirit Offering casts say a couple/few times, and then doesn't cast anymore, no matter what. I'm left with the combo Desecrate/Despair, until I stop moving.

While staying idle, the 3 spells cast normally one after the other, no problem.

I tried to find a way to make this issue happen every time (like starting moving with Despair casted first), with no luck so far.

I wonder why the sequence goes wrong sometimes as it seems to be kinda random, which is a GGG thing, but in this case, it's not supposed to be.

Any thoughts?


you need desecrate to trigger first. change the socket colours from B-G-B to G-B-B
poe is going down fast. Diablo 4 and Baldur's Gate 3 have no performance issues. play them instead
You've already been told multiple times what the problem is, and spacece7373 told you again.
"
Holyman1170 wrote:
Trigger a socket skill seems to be buggy in some ways for me too.

I have a B-G-B convok. wand with "trigger a socketed skill" crafted on it, and Spirit Offering/Desecrate/Despair socketed on it.

While constantly moving, sometimes (but not always), Spirit Offering casts say a couple/few times, and then doesn't cast anymore, no matter what. I'm left with the combo Desecrate/Despair, until I stop moving.

While staying idle, the 3 spells cast normally one after the other, no problem.

I tried to find a way to make this issue happen every time (like starting moving with Despair casted first), with no luck so far.

I wonder why the sequence goes wrong sometimes as it seems to be kinda random, which is a GGG thing, but in this case, it's not supposed to be.

Any thoughts?
You've already been told multiple times what the problem is, and spacece7373 told you again.
and that's why the thread was moved away. Error 40 is not a bug !! :)

Report Forum Post

Report Account:

Report Type

Additional Info