Boards›Esports

Controversy on Fanatic vs OMG game

TauNoob1·9/27/2014, 11:40:38 PM·9 votes·4,770 views

I was wondering if we could get any clarification about the bug that occurred during Fanatic's loss to OMG on 9/27/14. For those of you reading that don't know about it, when SOAZ attempted to backdoor OMG's nexus OMG's jungler, was hit by Kog'maw's ulti during the last .5 seconds of his recall and managed to get back to base. We all know that the channel cannot be interrupted during this time however Loveling's homeguards kicked in when he returned to the fountain, replenishing a massive amount of health and giving him the movement speed to get to and kill SOAZ quickly. The homeguard's tool tip clearly states that a champion must be out of combat for them to kick in, and this was not the case with Loveling. Yes he returned to base during the uninterruptible part of his recall, but he was in combat in terms of the homeguard enchantment (getting hit with Kog's ulti) and should not have gotten the buffs it provides. Without the health and mana it gave, SOAZ would have easily been able to kill Loveling and Fanatic most likely would have gotten the single hit on the nexus that would have won them the game. I'm not asking for a rematch or anything like that, I just want to hear riot's opinion on the bug and see if anything can be done to prevent this in the future.

Video of the bug and its results: https://www.youtube.com/watch?v=NlRfO1dObeQ

Edit: Riot has since said that there was no bug and the game will not be made up. In that case can we get the tooltip changed as to clarify that homeguard will always proc after a recall? Source: http://na.lolesports.com/articles/official-statement-fnatic-omg

13 Comments

Vulpes Inculta9/28/2014, 2:49:36 AM6 votes

Apparently, because Maw's shield was procced, it didn't count as Kha taking damage. It was stated everything was "working as intended" since Loveling technically was not in combat due to having not taken a hit. However, this statement troubles me, because Boots of Mobility count you as being in combat if you take damage, even if it gets soaked up by shields, including Hexdrinker/Maw. (Edit: V1.0.0.120: Will now mark you in combat for receiving/dealing any damage, even if it is absorbed by shields.)

Consistency, Riot. Please. You can't tell us one thing, but have another thing happen. I'm aware the case isn't the same, but in the terms of shielded damage not counting in one case but it does count in the other makes me side-eye. I really think this issue needs to be addressed properly.

Edit: Before anyone complains, I agree Fanatic could have made better choices in how they got that Nexus, but this bug was still game-breaking, as SOAZ may have had a fighting a chance without Loveling's Homeguard buffs. And, yes, I also agree SOAZ should have teleported to the ward that was in OMG's base instead of the minion wave. The ward was closer to the Nexus, and he could have used that time to land an extra auto or two. But as they say, hindsight is 20/20. There was a massive chance they could have won if it weren't for the Homeguard.

Edit 2: Kha'Zix took 7 damage, even after the shield procc. Even with the inconsistent definitions of "being in combat", he should not have gotten the Homeguard buff. He took damage, just the majority of it was soaked up by Maw. http://i.imgur.com/Sbb6FiH.png Another in stream screenshot I found of the instant the ult hits, before the shield procced: http://puu.sh/bQ2Tb/7537d7f6f5.jpg

Edit 3/Final: TL;DR Riot has inconsistent definitions of what being in combat is. Fanatic may or may not have won. Kha'Zix took damage. Homeguard still works after taking damage after recall as seen in numerous tests by other users and it should be fixed.

NeroUS9/29/2014, 1:29:31 AM4 votes

Riot's response leaves me less satisfied than I was before. It seems to dodge the essential issue, which is that a person can be in combat in the ordinary common sense use of the term and still complete a recall.

This means that the whole idea that a person who completes a recall is assumed not to be in combat is not a safe assumption to make and ignores the reality of the grace period that is affixed to the teleport spell.

In other words, Riot is saying that they "deem" the player not to be in combat. This is different from him not being in combat and points, to my mind, to an inconsistency that they are trying to brush over after it affected a world championship game.

Zlave9/28/2014, 9:35:35 AM2 votes

OH MY GOD AN UPDATE?!

NeroUS9/28/2014, 5:53:01 AM2 votes

Agreed. This is a serious issue in worlds; especially when the result of this match might end up determining the group.

Old Man Teeto9/28/2014, 10:51:05 AM2 votes

I watched that game, nothing looked broken. I've recalled and been hit at the end of the recall a ton but still had homeguards.

I think it's more that it was a super close game and we'd all LOVE to see them go at it again.

lorewise9/28/2014, 3:48:40 AM1 votes

I don't see how homegauard helped that much here, he didn't have that far to travel from fountain to Nexus.

Earl Eulrich9/28/2014, 10:42:46 AM1 votes

Fnatic just played that horribly wrong...backdooring with Rumble of all champions is just a stupid idea (especially if you throw an equalizer away from you vs a melee and then go to isolate yourself instead of hugging your minions), then going in 1by1by1 also doesn´t help - and if cyanide actually would have gotten a jungle-item for 80ap at some time he would have still killed the nexus after all the missplays.

Or they could just have grouped and won it from there after catching them recalling... They could have closed out the game a lot smarter and easier, worthy of a S4 world champion.

Complaining because of a minor appearence like that in a 70min game is just salty and unjustified. Sure, i would have been happy to see them win, but ultimately they didn´t play well enough that game.

And I don´t think it´s a bug...it´s just the way recalls work. If you reach the uninterruptable-part of the recall-animation you´re effectively back in base already, doesn´t matter if the animation is still going on somewhere else for 0,2-0,5sec.