Why did Riki keep channeling after my ally died and bought back?

November 1, 2026 5 answers
Asked by LoadoutLynx

I was playing Riki with Aghanim's and cast the ally-targeted version of the spell during a fight. I accidentally targeted a teammate who died right away and bought back, and then I got sent back to fountain while the spell kept going. What caused that weird interaction?

Answers

AltTabAce

That sounds like the spell was still tied to the original cast even though the target state changed. If the ally dies and then instantly returns, the game can end up treating the cast like it never cleanly resolved, so the channel or displacement keeps following through in a strange way.

In practice, this kind of thing usually happens when a spell has multiple moving parts, like ally targeting, relocation, and a lingering effect. The death and buyback probably caused the engine to reattach the cast to the revived unit or to the caster position in a way that looks broken even though it is just the rules colliding badly.

MapReset:

Yeah, that was my read too. It feels less like a pure visual bug and more like the game getting confused about where the spell is supposed to live after the target disappears and comes back.

Reply to this answer
TactiKite

The simplest explanation is that you hit a timing edge case. The ally died right as the Aghanim's version of the spell was being applied, then buyback happened before the game finished cleaning up the old state. That can cause the cast to persist longer than expected or snap to a fallback location.

When a hero gets removed and restored quickly, some effects are re-evaluated on the next game tick instead of instantly. If the spell was already in progress, the engine may have kept the active effect running and sent your hero back to fountain because the cast source got recalculated. Weird, but not impossible in a busy fight.

LoadoutLynx:

That makes sense. It looked like the spell never fully stopped, which is why the fountain teleport part was so confusing.

Reply to this answer
Overclocked!

This reads like a bad interaction between unit targeting and spell persistence. Since the ally version of the ability can affect teammates, the game likely stored the cast target as that hero, then the death and buyback made the stored reference unstable for a moment.

In fights, this kind of bug often shows up when something dies during an active cast, especially if the ability has movement or interval-based effects attached. So the weird fountain jump is probably the engine trying to finish the spell from a state that no longer matched the battlefield.

QuestMurmur:

Pretty much. The cast target changing underneath the effect is the part that makes it look especially cursed.

Reply to this answer
SnareBit

My guess is the ally died at the exact moment the cast got committed, and the buyback made the game think the target was valid again before the effect cleared. That kind of race condition can produce nonsense like teleporting to base or continuing an effect after the original target is gone.

If you can reproduce it consistently, it is the sort of thing worth reporting as a timing bug rather than just a visual glitch. The details matter a lot there, especially whether the spell was started before the death, during the death animation, or right after the buyback.

Reply to this answer
FrameHopper

Short version, the game probably got caught between two states at once. The ally was dead long enough for the cast to lose a clean target, then buyback came in so fast that the ability state did not reset properly.

So what you saw was likely the result of the spell finishing on an old reference while your hero got moved to the fallback location. It is one of those classic edge cases where Dota timing gets messy and the outcome looks totally random in the moment.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions