Lightning Warp and it's new behaviour (failing to cast on Ball Lightning)

As an enjoyer of Lightning Warp, I was slowly going insane trying to figure out why I could throw out a bunch of ball lightning's at enemies and bosses and then spam Lightning Warp only to have nothing happen.

I skipped over this in patch notes, but Lightning Warp now has the added "feature" of applying a debuff to an enemy you can't cull outright. This debuff makes teleporting into them, as soon as they are in culling range, automatic. This is fine, teleporting into stuff to blow them up is the entire point of Lightning Warp, it's also fun.

However, the reason it seemed bugged?

If you name lock anything, LW seems to prioritise reapplying the debuff rather than teleporting to a ball lightning projectile to do damage, even if there's plenty of those around. It's also an issue tracking a cluster of Ball Lightning projectiles through packs of enemies. It will then apply (or reapply) the debuff to multiple enemies.

Teleporting to a BL projectile is still possible but requires pinpoint mouse precision in a game that's not always as visually clear as what could be desired.

I'm proposing a different hierarchy of the behaviours when you name lock a target.

1. If possible: teleport to cull (and blow up) the target.
2. If possible: teleport to a ball lightning projectile resulting in an explosions that will damage the target now.
3. If the above fails, apply the automatic debuff.

The instant interrupt of immediately, and automatically teleporting to anything cullable with the debuff, is indeed fun and can keep working like it does. Even if it tends to teleport my Sorceress into danger.

A less refined approach would be to preventing the buff from getting reapplied if there's more than half the remaining duration left.

I hope you make one of my favourite skills less broken and more usable.
K. Thanks. Bye.