-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ability Draft] Rot and Tether are still working while character is infested, swallowed or gobbled up #263
Comments
In the case of Tether + Infest, it doesn't seem to be a bug. Per the Tether tooltip: "The tether breaks when the allied unit moves too far away, or Io cancels the tether." - in the case of Tether + Infest you're not cancelling the tether nor moving out of range. The unit is hidden, but still having its position updated. |
This is a BUG tracker, not a personal wish list or balance feedback collector. |
Tether automatically ends when IO is swallowed by Dismember under normal circumstances, or when the tethered target is Swallowed or Infests someone else. This seems to imply a "hidden aspect" to Tether that it should end when IO or IO's target becomes hidden, but it is coded in a strange way such that Dismember is the only hide that Tether checks for, in all pick or ability draft. It is debatable whether this is a "bug", but it is certainly an inconsistent interaction spawned by a bit of jankiness in the game code. Also, per Rubick's new aghs, this "bug" extends to All Pick under niche circumstances. All that said, I don't agree that Rot should necessarily end when Pudge is hidden. There is no precedent for that. |
Rot + infest & rot + dismember work with rubick in demo mode. |
Description
Rot ability shouldn't deal damage while character is infested in another hero, is swallowed with dismember shard upgrade or gobbled up with Snapfire shard upgrade. Also It's still working during Primal Split.
Same applies to Tether - Tether should be interrupted by infesting target or by getting swallowed by target.
No match IDs for now - would update whenever this would happen again.
Example Match ID (and possibly Timestamp)
0
The text was updated successfully, but these errors were encountered: