Setts Ult not correctly registering where him, or target are [Gameplay Bug]

WhyYouMadBrosef··1 votes·1,360 views

Regarding Setts ult, I have found that the game doesn't seem to properly register where Sett and his Ult target are during the animation of Show Stopper. I have had this issue a few times and it has gotten me killed and cost me kills because of it. While Ulting an Illaoi, her tentacles slap where I was and still dealt damage to me, as well as I have used The Show Stopper to pull a Kindred out of her ult, but it still did no damage even though she was clearly outside of her ult radius, as it registered her as still being in the ult until directly after impact.

I have also encountered a problem where I attempted to use Sett's E [Face Breaker] and the target took damage, was hit by the slow, but was not pulled towards sett. This may have been due to the large size of the wall.

Show Stopper vs Kindred Show Stopper vs Illaoi Face Breaker Bug?

3 Comments

Wordson1x1 votes

I don't see what you're trying to show sorry. However the Illaoi bug yeah that's easy to see unlike this one. PS: Kindred and Sett are really buggy champions

WhyYouMadBrosef1 votes

What this video shows is that since Sett's ult does its damage upon impact, if you ult kindred out of her ultimate, it should have killed her (or at least dealt damage) but due to the fact that until after setts ult damage goes through the game does not register Sett and his target i(n this case, Kindred) have moved that seems to be a rather large bug. In the video you are able to see the zone for kindreds ult and that even after hitting her out of it she takes no damage and has to jump back inside of it to get healed.

For clarity, in the video kindred, Sett and Rumble gain a small gold shield Icon above their Level (meaning they cant be killed due to kindreds ult) but it's not until after the damage of setts ult goes through that the icon disappears (because the game did not register that they had moved until then)

TheBrothersGrymm1 votes

I mean the damage it does should be looked into first

More from Report a Bug