Regarding the Aurelion Sol Remake

RiotRiot Penrif·8/22/2016, 9:54:14 PM·1 votes·34,392 views

TL;DR: We’ve identified the cause of this bug, and it’s unique to Aurelion Sol. We’ll be implementing a fix on 6.18 (the Worlds patch). Read on for all the details.

Yesterday during the NA LCS Semifinals between CLG and TSM, a game had to be remade due to a player seeing a Aurelion Sol's passive missile in the wrong place.

Aurelion Sol's passive has the longest lasting missiles in League's history by quite a large margin, and they exposed a set of technical limitations we had never hit before with missiles. Most pertinent: this is the first time a missile is defining its motion around a unit that does not share its visibility. Previous missiles that moved based on another unit, like Ahri's Fox-Fire, share visibility with their owner - you only see the missile if you see the unit as well.

In order to cope with this new problem, we put in some handling where the client is sent positional information about Aurelion Sol if one of his missiles is in vision but he himself is not. This allows the missiles to represent their movement without having to fully reveal the champion. However, there is a small time gap between the client gaining visibility of the missile and when it receives this positional information, and that gap is what ultimately led to Sunday's remake.

A brief timeline, based on Twitch's VOD:

  • 10:29 game time (43:38 video) - Aurelion Sol's passive spotted over wall by ward at blue buff
  • 10:31 game time - Aurelion Sol and his passive fully leave TSM's vision
  • Aurelion Sol remains out of TSM's vision until:
  • 11:06 game time - Aurelion Sol's passive spotted in mid lane by Rek'Sai

For a few frames at game time 11:06, TSM Bjergsen's client displayed one of Aurelion Sol's passive missiles at the position it would have been if Aurelion was at his last known position - game time 10:31. It had received the information saying that the missile should be made visible, but had not yet received an update on where the champion was, so it showed the missile relative to his last known position.

This Aurelion Sol defect has been present since he shipped. We had some code in place to mitigate effects of this nature for him, but they were clearly not enough. In the affected game, the circumstances were such that a player's decision making was negatively affected, and lead to a remake. We are fixing the issue by preventing the client from showing these missiles in the absence of accurate positional information. This fix will be a part of the 6.18 patch cycle, which is the patch Worlds will be played on.

Regards, ~Riot Penrif

40 Comments

Deep Terror Nami8/22/2016, 9:57:49 PM12 votes

Who is CLS?

patmax178/22/2016, 10:33:59 PM4 votes

Is this basically the same bug that leaves long trails all over the screen when things like Kindred's Wolf or a champ with DMP exit and enter fog of war?

Penta Penguin8/25/2016, 11:20:39 AM2 votes

Why did it take until the worst possible scenario for Riot to fully fix the bug, not just "mitigate" it? 6.18 seems pretty fast for a fix, but you let it sit for months until it ruined a pro match

RISE Shlack1238/27/2016, 6:00:20 AM2 votes

A known bug allowed to exist for weeks is only to have the bug rear its ugly head in a semifinals match in the NA LCS. So nothing was done to sort out this bug other than some vague "mitigation" code. Bugs like this should be fixed 100% before a champion is allowed into the competitive scene. LCS teams dedicated hours upon hours to picking up AurelionSol and building teamcomps around him, yet their time was wasted because you guys let a known bug into the largest stage League of Legends has to offer.

From a QA standpoint, this was a MASSIVE failure. Bugs should be dealt with before champions go live. There are no excuses. I realize that new champion sales are a major revenue stream for Riot Games, and this type of issue only serves to highlight the importance of getting a champion as close to bug-free as possible before they hit live. I realize this isn't always possible, so in cases like AurelionSol , he should have not been in the champion pool for LCS until the bug was fixed.

Simply put, you guys failed. Big time.

MammothKat8/23/2016, 2:07:18 PM1 votes

Will this bug also effect kleds R? The extreme movement speed with other effects may replicate the issue as server updates might not cope with rapid movement. Jw since this seems to effect trails and movement.

IncepTion v8/23/2016, 7:53:09 PM1 votes

I just had a game where this bug happened but with Ahri and her W.

warpenguin5558/24/2016, 3:23:35 AM1 votes

So lets say you walked into a glitch Sol Star, you dont take any damage do you?

Arthianne8/29/2016, 5:15:13 PM1 votes

I totally thought this was an actual remake and wtfed

statelesskiller9/1/2016, 9:22:53 AM1 votes

wait wait wait. you guys KNEW about this bug to begin with. DIDNT fix it and then comepltely ****'ed any team that had AurelionSol in there playbook because "oh hey its agitating someone now gotta remove it?" like im a CLG fan and everything. but if it was worth banning sol globally. then this should have been fixed before he even left the PBE. these are team which practice and are highly structured to play certains ways. and whenever a champion gets this kinda of "global" ban it prevents the team from reacting properly. as essentially the other team got a free ban. its potentially unfair to multiple team

78750242DEL19/5/2016, 10:43:26 PM1 votes

Riot's Spaghetti Code? NotLikeThis. xD

Tyrone Lannister8/22/2016, 9:56:51 PM1 votes

Unlucky :/

Rishal2110/1/2016, 7:50:35 AM1 votes

It was Bjergsen who noticed and it was TSM vs. RNG

Eedat8/22/2016, 10:09:24 PM1 votes

Can the bug be intentionally reproduced by either team? What circumstances cause it exactly? Why does it happen some times and not others?

Soníc8/22/2016, 11:13:54 PM1 votes

What about the similar problems where champion portrait flashes on the map nowhere near his location sometimes? Happens maybe 1/20 games to me, but everyone on my team sees it when it does happen...

DarkinPrime8/23/2016, 7:15:29 AM1 votes

how about you just fire everyone who had a hand in designing this champion? I am so god damn sick of Riot releasing champions that are full of problems and/or uninteresting and/or OP needing to be nerfed. Your last batch of new champions have been nearly all utter shit. How about you stop wasting players god damn time with amateur hour and fix the existing champions? I mean ya know, when you get around to reworking Rzye for the 9th time of course, or buffing champions who are in waaaaaaaaaaaaaaaay better states than many others who receive zero attention.

Your company is nearly a billion a year in revenue. At this point, everyone excepts more from you. You have the resources. Why do things keep getting fucked up? Why do you guys have to change dragon 8 times a year? Why do you guys make weird mastery changes that have to be nerfed (months later) after everyone immediately pointed out that a certain mastery on certain champions was totally broken. Why could EVERYONE see it immediately yet someone you guys missed it?

Your company reeks of incompetence and decisions based on what Marc Merrill thinks will bring more revenue--changing everything to cater to casual players, making new champions instead of fixing old ones to drive new sales, skins etc. But the reality is, people are really starting to get weary of you guys.

Get your shit together, Riot. Every month I play less and less, and eventually I will be done. The new champions haven't excited me and dynamic queue is frustrating. And I HATE when you guys try to say a champions is in a good spot because of their win rate which is usually only 1 or 2 percent more or less than every other champion. Your math reeks, and at this point I severly doubt if anyone who works at Riot has an advanced degree in mathematics.