Aurelion Sol + Shen Bug

The Scarlet One·11/8/2016, 10:51:56 PM·1 votes·937 views
Aurelion Slav

What we discovered in a random ARAM match, is a supposed Aurelion Sol bug when being shielded by Shen. My analytical mind forced me to try to reproduce the bug - it is repeatable all the time you do the sequence.

Its presented in the vid (excuse us for the language we used - it's Polish) I don't know if the intercation should work like that.

So, to explain - from 45s - as I was too anxious to post it to actually edit the vid. So let's start at 45 s.

  1. We see Aurelion using his E to traverse the river.
  2. Shen ults him - Aurelion receives the shield normally and everything seems to be working as intended.
  3. Third variable comes into play - in this case it's Varus autoattacking (around 0:51).
  4. Shield from Shen caused that Aurelion's E isn't interrupted.

Points of concern:

  1. Shouldn't it be interrupted by receiving damage? If not, then
  2. As you could notice, Aurelion's E goes on cooldown related to being in combat - that results in frantic clicking and unability to cancel Comet of Legend.

In regards to point 1 - if Varus managed to deplete the shield Shen's ult provides everything is interrupted normally.

I'm writing this here instead of my server (EUNE) because I feel it would get more attention (and it will get noticed by you faster).

Oh, and disregard build - building random cdr items. Sorry for the inconvenience but I will reply to any posts in European morning (in 6 hrs).

To give more info - I actually have second vid with tested case in which Aurelion gets CC'd while traversing - it works as intended I guess. Here's the link: Aurelion Slav gets CC'd

4 Comments

Clowning11/9/2016, 12:22:42 AM1 votes

"Performing any action (excluding Starsurge.png Starsurge) or taking damage from champions or turrets will Comet of Legend 2 end Comet of Legend early." -Wiki

If Sol is shielded by Shen, as long as the shield isn't broken, E should still continue because Sol took no damage.

azza42011/9/2016, 8:27:29 PM1 votes

did anyone notice the upper right hand corner? it appears the gameclock paused a second or more, and ping went from 44-100 something. maybe the second scenario was packet drop or latency? are you able to reproduce scenario 2?