Original Post — Direct link

The added cooldown portion is NOT added on top of the trigger cooldown. I am currently running storm burst CwC conduit and its proccing every 0.26sec because its overwriting the trigger cd with the cast time. I also tried a Mjölner setup with shocknova as my shock skill and cyclone as my CwC trigger. It also slaps insanely hard.

Both versions are super fun to play, but I prefer storm burst because of the range and visuals. Used ziz tree for his conduit build, works for both with a bit of attribute optimization.

External link →
over 1 year ago - /u/Mark_GGG - Direct link

The added cooldown portion is NOT added on top of the trigger cooldown

Cast while Channelling does not have a cooldown to add to, so the cast time adds to 0 seconds and results in a total cooldown time exactly matching the cast time (assuming no modifiers to cooldown recovery rate).

Cast while Channelling tries to trigger the spell every 0.x seconds while you channel. If the skill is on cooldown at that time, that will fail.

If the cast time (and thus cooldown) of Lightning Conduit is shorter than the time between attempted CwC triggers, it will trigger at the CwC trigger rate, because each time CwC tries to trigger it, it will be off cooldown and ready to go..

If the cast time (and thus cooldown) of Lightning Conduit is longer than the time between attempted CwC triggers (but shorter than twice that time), it will trigger at half CwC trigger rate, because every second time CwC tries to trigger it, it will still be on cooldown and fail to trigger.

over 1 year ago - /u/Mark_GGG - Direct link

Originally posted by RelevantIAm

If the cast time (and thus cooldown) of Lightning Conduit but lower than half of the CwC trigger the time between attempted CwC triggers, it will trigger at twice CwC trigger rate, because every second time CwC tries to trigger it, it will still be on cooldown and fail to trigger

I'm dumb, I don't understand this part. Sounds like you're saying it'll trigger twice but also that it will fail to trigger the second time.

Apparently I lost some of that part when rewording it, in addition to getting twice & half swapped around. Should be fixed now in my post.

over 1 year ago - /u/Mark_GGG - Direct link

Originally posted by RedJorgAncrath

Wait, so was mention of a cooldown in the gem description (neither lightning conduit nor CWC have a cooldown or added cooldown) a way to inform that this will work with CWC but probably not some other shit that adds a cooldown? The cast time added to cooldown must break some triggering setup. Otherwise it doesn't seem worth even mentioning or adding to the gem. Pretty confusing. :)

I don't understand what you're asking here

over 1 year ago - /u/Mark_GGG - Direct link

Originally posted by RedJorgAncrath

Ok yeah we're speaking different languages right now. :) I'll try to make my question simple:

  • Lightning conduit does not have a cooldown, but mentions that it adds its cast speed to "its cooldown (doesn't have one)" if triggered.

  • CWC doesn't add a cooldown.

  • Spellslinger doesn't either.

  • CoC doesn't have a mention of cooldown in gem desc, but wiki shows it might be a factor.

The gist is I don't understand why the cast speed is even added to the cooldown of this gem if it doesn't have a cooldown. I assume we're speaking about a cooldown it acquires via weapon mods or supports. And there might be some reason you added the cast speed to the natively non-existent cooldown.

Not having a cooldown is effectively the same as having a 0 second cooldown - several things rely on the fact that adding to the cooldown time will cause a nonzero cooldown. This is how the unique jewel "From Dust" works, for example.

Spellslinger and Cast on Crit do add cooldowns to supported skills, which are explicitly shown near the top of the gem tooltip for those gems.

EDIT: fixed incorrect support name