1221
1222

Worlds[Spoilers] FNC vs OMG Homeguard Interaction Megathread (self.leagueoflegends)

NeutronRocksMod[M] が 投稿 - stickied post

並べ替え:
ベスト
ベスト
トップ
新着
注目
論争中
古い順
あなたは単独のコメントのスレッドを見ています。

残りのコメントをみる →

[–]TheDizeazed 871 ポイント872 ポイント  (427子コメント)

Full definitive proof in one video

[–]COUCHSURFING_RAPIST 381 ポイント382 ポイント  (91子コメント)

If this is real then it's definitely proof of a bug. The homeguard procced, not because of maw shield, but because of the recall.

[–]bebewow 105 ポイント106 ポイント  (17子コメント)

REMATCH HYPE TRAIN!

[–]SintSuke 13 ポイント14 ポイント  (11子コメント)

Nah. The difference was one auto attack on that Nexus, which Soaz could have gotten if Kha Zix didn't use Homeguards + Jump..

[–]Bamtastic 17 ポイント18 ポイント  (9子コメント)

There were many areas where Fnatic "could" have won. In Soaz used his ult on the nexus to kill the creeps so the supers would have been on the nexus they could have won. If Soaz would have simply just auto'd the nexus instead of trying to use skills on khazix, they could have won. If Cyanide didn't auto a creep and hit the nexus instead, they could have won.

There are many instances where they could have won, and khazix getting homeguards wasn't the only one.

[–]L43 3 ポイント4 ポイント  (0子コメント)

Of course Loveling getting homeguard buff COULD (and in my opinion WOULD) have changed it. He is closer to sOAZ than he should have been without it, and MUCH more healthy (35% of health tick per second rather than 10% IIRC). sOAZ may have been able to duel him at lower health, it may have triggered sOAZ to actually use his ult less effectively than he otherwise would have (such as on the minions), or Loveling may have stayed at the fountain a tick longer. Saying that it didn't affect anything this is ridiculous.

[–]frictionqt 0 ポイント1 ポイント  (0子コメント)

he ulted to stop homeguards/slow them on platform.

[–]titieb 0 ポイント1 ポイント  (0子コメント)

Right, but then again that's entirely the player's fault, whereas people are complaining (quite rightfully imo) about a bug which was in no way in control of any party, but in the end did affect the result of the match

[–]SeanMartin96 0 ポイント1 ポイント  (0子コメント)

I think he used the abilites to get his heat to 100 for the buffed aa's

[–]Etzlo 0 ポイント1 ポイント  (0子コメント)

let me rephrase: they definitely would have won if not for the bug

[–]Raganasan 0 ポイント1 ポイント  (2子コメント)

Well if you expect homeguards to work how they should work, why not ult the spawn to prevent any threat? I'm pretty sure that if the mechanic of homeguards was intended to work that way and it was clear to everyone he would have reacted differently and FNC would have won.

[–]Bamtastic 0 ポイント1 ポイント  (1子コメント)

People keep saying that khazix would have died if he didn't get the hp from homeguards or something, but you do not know this. If rumble tried to duel khazix instead of attack the nexus, then the damage that rumble did to the nexus would not be there in the first place which would then persuade xpeke and cyanide not try to finish the game either. You don't know what would have happened, because there are dozens of possibilities and when you change one thing, everything that happens afterwards will change too.

[–]Raganasan [非表示スコア]  (0子コメント)

I'm sure the equalizer would have at least slowed Kha down a bit. Also if he knew that a homeguarded Kha was coming around he migh have used the equalizer next to himself and the Nexus which would have won them the game as well I guess.

So it was not only the tiny little help OMG needed to win (doesn't even matter if Fnatic could have done better here or wheter or not they deserve it), it also affected their decisions, at least it's a valid assumption.

That being said. In this particular scenario the bug singlehandedly turned the game. I highly doubt FNC would have done anything different with a little more time. Why do it like that in the first place then.

At least that's what I think.

Edit: I just noticed I'm too tired too argue (I'm terrible when it comes to writing down my thoughts anyways) so I'll just leave it here.

コメントをもっと表示する (1 返事)

    [–]H5oD [非表示スコア]  (0子コメント)

    could is the correct term. But most people use would (which is incorrect). The discussed bug did cost soaz the timeframe for a possible "last" hit. But the 2 after him also had more than one possibility to land one more attack.

    A rematch would only be ok if soaz was the last one to attack the nexus. Then the bug would have resulted in fnatic "losing" the game. With the current situation the ones who could have destroyed the nexus didn't encounter this bug and had the information that the nexus had X HP/hits remaining and could have without a problem hit it X+1 times.

    The bug may be a sad thing to happen in such an intense game but non the less it wasn't gamebreaking at the moment it happened. Making it not gamebreaking at all.

    Something "gamebreaking" would e.g. 1 on each team remaining. Survivor wins the game. One guy is Nasus/Renekton using his ult with very few HP and the ulti going on cooldown but he still doesn't gain any bonus HP and dies. That does happen since those 2 ultis grant HP with a very short delay (note: I don't know if this is intended. But if it wasn't that would be gamebreaking in this described case) (note: don't ask me why he should use his ult right before going down and not early. This is completely hypothetical)

    [–]Ozymidas 0 ポイント1 ポイント  (4子コメント)

    Man, even if a rematch was the correct decision, it would make one of the most incredible, exciting matches of all time completely meaningless. What a fucking bummer that would be.

    [–]URF_reibeer 3 ポイント4 ポイント  (1子コメント)

    yeah it's way better to look back on "one of the most incredible, exciting matches of all time" and think:"yay we won/lost this because of a bug" (and because soaz didn't think far enough to switch an item for lichbane while waiting for respawn even though he knew he wanted to backdoor)

    [–]bebewow 0 ポイント1 ポイント  (1子コメント)

    Just like the first 3 games of the WE vs CLG.EU Season 2 Quarter-Finals Series. We still have them as one of the most awesome things in the history of LoL and in my humble opinion, the competitive integrity should not be hurt as it has been several times before.

    [–]Ozymidas 0 ポイント1 ポイント  (0子コメント)

    Yeah, I get that, but if a rematch happens I'm not the least bit hyped for it. Especially since tiebreakers are already a big possibility anyway.

    [–]MTwistTits or Ass 141 ポイント142 ポイント  (58子コメント)

    what the shit, you got gold from that?

    [–]LiquidLogiK 131 ポイント132 ポイント  (13子コメント)

    MTwist's internal monologue

    god dammit i asked tits or ass on amas nearly a hundred times hoping for some gold and never got any and this fucker gets it off of the most generic comment ever

    [–]MTwistTits or Ass 45 ポイント46 ポイント  (11子コメント)

    there was no gold when i started, we were men back then working for no reward!

    [–]Silkku 8 ポイント9 ポイント  (8子コメント)

    Pff, it's always been for the sweet delicious karma. Gold is just a cherry on the top

    [–]MTwistTits or Ass 4 ポイント5 ポイント  (7子コメント)

    Karma does nothing, its a number. Doesnt make anyone anymore right or wrong than they would have been with 0 karma or 1 million karma

    コメントをもっと表示する (2 返事)

      [–]Tryndameereeeeee[My Greatest Creation] (EU-W) [非表示スコア]  (0子コメント)

      This is literally the internal monologue I keep having everytime. BUT I GOT GIFTED GOLD ONCE IN MY LIFE AND NOW IT'S COMPLETE! xD

      [–]bebewow 0 ポイント1 ポイント  (0子コメント)

      Bitch, I get gold for killing minions!

      [–]Ramlevy 0 ポイント1 ポイント  (0子コメント)

      He probably got it from a salty fnatic fan.

      [–]Blacksworn 0 ポイント1 ポイント  (0子コメント)

      Please don't give me gold

      [–]pumbahusajo [非表示スコア]  (0子コメント)

      fnatic fanboys be like real hyped

      コメントをもっと表示する (40 返事)

        [–]Ladnil 0 ポイント1 ポイント  (0子コメント)

        If it's reproducable and consistent as the video seems to indicate, then intentional feature or not, it shouldn't force a rematch. The kind of bugs that force rematches should be things like full game crashes or random unctontrollable effects.

        [–]psycow_ 0 ポイント1 ポイント  (0子コメント)

        i'm gonna wait on the official verdict which i hope will be better worded than those short tweets by nick allen. if it's a bug (and it does seem that way) it definitely changed the outcome of the game.

        [–]SupDoodlol 0 ポイント1 ポイント  (0子コメント)

        Possibly, but it's less of a bug with homeguard and more about the "bug" of recall not being stopped if you take damage right at the end. Homeguard was programmed to give you the speed buff upon recalling or if you are standing in the center of the fountain (assuming you haven't dealt or received damage within 6 seconds). The reason it is fine to get the recall buff upon recalling is because recall take 8 seconds (or 7 seconds with the mastery) and thus it should be impossible to deal or take damage within the last 6 seconds if you successfully made it to base.

        The problem is, it is possible to take damage within that 8 (or 7) second window because of the bug that allows you to take damage at the last moment and still recall successfully. So basically if you argue it is a bug, you are arguing that is a bug for not interacting correctly with another bug that we have become accustomed to since the release of this game.

        [–]TiliCollaps3 [非表示スコア]  (0子コメント)

        Thats proof it isn't a bug because that's how the recall is coded.

        コメントをもっと表示する (10 返事)

          [–]ChristianMunich 111 ポイント112 ポイント  (168子コメント)

          Well done. Big dilemma for Riot.

          [–]Nestleworstcompany 47 ポイント48 ポイント  (1子コメント)

          Also worth noting that if you get shielded by an ally, receive damage smaller than the shield, walk into base, the HG will be on cooldown.

          Maybe the community should finally understand that its not about damage taken or not, its about the homeguard-recall bug.

          [–]AwkweirdVan [非表示スコア]  (0子コメント)

          It can only be about the damage taken. The intended function of homeguard is to not be affected by nullified damage, ie damage hitting a shield. It is ONLY supposed to be stopped when actually taking/dealing damage. Regardless of if there is a bug where homeguard is sometimes -mistakenly- affected by shielded damage, that bug did not occur in this game, and should not have.

          If it's not about damage taken this thread has no purpose. The point would be like saying "How come the bug didn't happen in this game? REMAKE PLS."

          On that note, there is 0 chance Rekkles dealt damage with his Kog ultimate, one ult was not enough to break a 400 damage shield on a 170 MR Kha Zix. The only chance something went wrong here is if the wraiths were able to deal physical damage to him before his recall completed, so that's what should be focused on.

          [–]BestKarmaEUW 151 ポイント152 ポイント  (100子コメント)

          No dilemma; Nick Allen has shown he will ignore it. The video is indeed well done and made me understand the bug much more; too bad it won't help.

          [–]NazZuto 59 ポイント60 ポイント  (39子コメント)

          No we should just make sure Nick Allen see it before it's too late it's clearly a bug. We shouldn't let him ignore it.

          [–]briedux[slepas] (EU-W) 37 ポイント38 ポイント  (38子コメント)

          He will ignore because he doesn't want chinese fans to be upset. Also, remakes are not something that Riot wants in the first place because it will make lol not aas legitimate as an esport.

          [–]Igeldsuch 141 ポイント142 ポイント  (13子コメント)

          this bug is A LOT more game decicive then the aatrox heal bug. this bug was literally win or lose for one team

          [–]Keytap 16 ポイント17 ポイント  (2子コメント)

          To /u/briedux's point, lots of traditional sports have games like this. The clock didn't stop, or the ref didn't call the foul - they all tend to side with the call that was made, if that makes sense. People don't like rulings being overturned, after all.

          [–]Caisha [非表示スコア]  (0子コメント)

          With that logic, then instant replays wouldn't exist. They created the replay in order to have definitive proof that the call was wrong, and then they can reverseit.

          You can't really do that in this game, so remakes are the only recourse you have against wrong calls/bugs.

          コメントをもっと表示する (1 返事)

            [–]Lemonian 29 ポイント30 ポイント  (3子コメント)

            Upvoted cause true, the remake of Gambit was bs this is clearly a remake that should happen.

            [–]chollyer 4 ポイント5 ポイント  (2子コメント)

            See, this is the trouble with them making that remake in the first place. It's set the bar so low for remakes - that this is leaps and bounds above that bar. Not having a remake in this scenario would be an incredibly poor showing for the integrity of this competition.

            [–]Lemonian [非表示スコア]  (0子コメント)

            I agree with you, if that remake hadn't happened there would have been 2 sides to the story for me.

            Cause on 1 hand it was a bug, cause there are enough videos out there to show now that it doesn't happen if you go into the base, only through recall and that the patchnotes say, this bug was fixed and shouldnt have happened.

            The only thing that goes through my mind is that Soaz autoattacked Kha zix 1 time, if he did that on the nexus they would have won.

            So for me this was 50/50 if that first remake had never happened.

            [–]OxyGenesis(EU-W) [非表示スコア]  (0子コメント)

            Riot explained that they only did a remake because SK spotted the bug and paused the game correctly, at this point riot/the referee should have offered to restart the game but neglected to do so. Therefore riot made a mistake and the only way to fix the mistake was to remake the game.

            The FNCvOMG won't get remade because no one spotted the bug at the time, therefore the result stands.

            [–]frostedz 2 ポイント3 ポイント  (1子コメント)

            Too bad you have to pause the game and report the bug to get a remake. This is clearly a bug, but Fnatic won't be getting a rematch because of this rule.

            [–]luksi2 1 ポイント2 ポイント  (0子コメント)

            That's bullshit, honestly. Do you really expect the players to notice every little detail? How could Rekkles possibly be chasing down and killing San and at the same time keep an eye out for a bug happening on the other side of the map?

            Sure, it was technically possible for Fnatic to have noticed, but it's inhumane to even expect such things from them.

            [–]MoonTemplar 0 ポイント1 ポイント  (0子コメント)

            that bug that you call it has been in the game for a long time. If you like less than a second left for recall you will back even if you get damaged, i dont know why that happens but it does and when you back yo uget homeguard

            [–]Mechanicserino [非表示スコア]  (0子コメント)

            Well to be fair OMG got no edge here, cos the bug works both ways.

            [–]turdburglersc 0 ポイント1 ポイント  (0子コメント)

            if its literally one team winning vs the other team winning 100% with no doubts, wouldnt it make more sense to just award the game to fnatic?

            imagine a scenario where team A wins a game against team B, but for some reason the game comes up with the victory and defeat screens the wrong way around, and the lobby also reports a reversed result. now in this situations we can clearly see the bug 100% caused a reversal of the win, so you wouldnt ask for a remake, you would just award the other team the win.

            why should fnatic accept a remake if without the bug they win the game?

            コメントをもっと表示する (1 返事)

              [–]Draki1903[Draki1903] (EU-W) 5 ポイント6 ポイント  (16子コメント)

              Hijacking a visible post.

              Riot please release a 1080p source video of the Khazix-Wraiths-Kogmaw interaction so that we can see for ourselves if he was 730 hp ->728 hp or 720 hp -> 728 hp. I can't tell the difference between 2 and 3 from the Youtube/Twitch mirror.

              [–]SovietUnion1337[I AM NOT BRAZILIAN] (BR) 28 ポイント29 ポイント  (12子コメント)

              here you go http://i.imgur.com/lj5z5FV.jpg

              [–]Zed_or_AFK 3 ポイント4 ポイント  (1子コメント)

              And please start streaming Worlds/LCS in 1080p... please?

              [–]Draki1903[Draki1903] (EU-W) 3 ポイント4 ポイント  (0子コメント)

              Bro, the long con doesn't work if you try to get to the final step so fast

              [–]ehrnio[M5 never forget] (EU-W) 0 ポイント1 ポイント  (0子コメント)

              It does not actually matter. The bug does not happen because of the shield breaking or not. The bug is that if you get hit with a shield on while recalling, homeguard will work. If you get hit with a shield on and just walk back to base you won't get homeguard though. That is why it is a bug, the HP is not relevant.

              [–]PaidToSpillMyGuts 0 ポイント1 ポイント  (0子コメント)

              not remaking an illegitimate game is more detrimental to the integrity of the sport than remaking a game to ensure fair results.

              [–]JohhnyDamage 0 ポイント1 ポイント  (0子コメント)

              Years ago the Miami Heat were flown to an empty stadium to replay the final three minutes of a game because one team was awarded an extra timeout.

              This happens sometimes.

              [–]Brandsworth[InsidiousBane] (NA) 0 ポイント1 ポイント  (2子コメント)

              Wouldn't ignoring the bug and just accepting the way things have happened actually harm the legitimacy of esports?

              [–]briedux[slepas] (EU-W) 0 ポイント1 ポイント  (1子コメント)

              There are still chinese fans.

              [–]Brandsworth[InsidiousBane] (NA) 0 ポイント1 ポイント  (0子コメント)

              Alright. Well considering the legitimacy of the actual bag, and the fact that it's been proven countless times, he's choosing between upsetting Chinese fans or everyone who clearly can tell this is a bug and could care less who wins, and just wants a remake with a fair outcome.

              [–]Khenir 0 ポイント1 ポイント  (0子コメント)

              Maybe legitimate as a sport, but you can bet your ass that if we used electronics to score, say, Judo, it fucking up would get shit remade.

              Referees get a pass, they're human, not infallible, Machines, not so much.

              コメントをもっと表示する (1 返事)

                [–]Madsemanden 9 ポイント10 ポイント  (0子コメント)

                Remember with him being proved wrong, they are probably looking further into this case and that could be the reason for them seemingly not reacting.

                [–]123tejas 0 ポイント1 ポイント  (0子コメント)

                You can ignore it, but its bullshit if they change the way the interaction works later. It's either a bug or it isn't.

                [–]KickItNext[Rockless Lobster] (NA) 0 ポイント1 ポイント  (0子コメント)

                The rules state that there can't be a remake unless the bug is reported during an in-game pause, like the aatrox bug between SK and GMB.

                [–]z0mbiem4ge 0 ポイント1 ポイント  (1子コメント)

                Riot should not punish OMG for this because they won the game fair and square from their point. They played their hearts out and it will be unfair to punish them for a error that isn't their fault. Ultimately it is a sometime that Riot's mess up on, not something OMG can control. So if anything, Riot should compensate FNC instead of trying to punish OMG

                [–]BestKarmaEUW 0 ポイント1 ポイント  (0子コメント)

                What do you propose?

                [–]Vasterole[Vasterole] (EU-W) [非表示スコア]  (0子コメント)

                Nick Allen must at least admit that the bug happened. His last decision was made claiming that there was no bug which is wrong.

                [–]XEV4NX 0 ポイント1 ポイント  (0子コメント)

                As a gambit fan, I'm mad as hell. Remake the game.

                コメントをもっと表示する (53 返事)

                  [–]Spreek 26 ポイント27 ポイント  (44子コメント)

                  Just goes to show that remakes should have never been an option (unless the bug literally made the game unplayable). Can you imagine a pro sports game being completely replayed because a referee made a bad call?

                  Remaking Sk vs GMB, a game with a very minor bug that had no impact on the result of the game, just opens the floodgates.

                  [–]GorillaBuddy 11 ポイント12 ポイント  (2子コメント)

                  They replayed the last minute of an NBA game a while ago because the scorers table incorrectly fouled someone out. In LOL it's impossible to replay only part of a game, but the concept is not completely unheard of. It's also not comparable to a bad call by a referee. That's part of the game and everyone lives with it. It's more like if a soccer team had 12 men on the pitch for a few minutes. That's total bullshit and shouldn't just be dismissed.

                  [–]Jayang 6 ポイント7 ポイント  (1子コメント)

                  That's part of the game and everyone lives with it.

                  If that is the case with basketball and other sports influenced by human discretion, why is it not the case that for league, we just have to "live with" the fact that bugs exist, and that they do impact the game?

                  And replaying the last minute of a game is much different than replaying an aentire game.

                  [–]Pixelpaws[Shira Frozenmoon] (NA) [非表示スコア]  (0子コメント)

                  The best counterargument I can think of is that the same bugs exist for all teams in the tournament. No, it 's not ideal and I hope it's fixed, but it's not like one team intentionally received an advantage.

                  [–]AChickenTender 13 ポイント14 ポイント  (32子コメント)

                  NOOOOOOO this would be like your teams basketball hoop was bent at the last second of a game ending shot.

                  it was a game altering bug. which does not happen in professional contact sports?

                  [–]Spreek 9 ポイント10 ポイント  (30子コメント)

                  It doesn't exist, but a bad call from a ref amounts to basically the same thing.

                  [–]acemzz 14 ポイント15 ポイント  (2子コメント)

                  Also, consistency is impossible when discussing subjective fouls. Computer codes do not leave room for much subjectivity. Either the game acted contrary to what Riot's rules state, or it didn't. I don't understand why you want to revert to the imprecision seen in physical sports. They are constantly trying to improve their own precision, not diminish it.

                  [–]Spreek 3 ポイント4 ポイント  (1子コメント)

                  Because it's unfair to both teams and to the fans to randomly invalidate results of games after they have already ended and force the game to be replayed.

                  Identifying what is a bug and what isn't and more importantly what qualifies as a game breaking bug is very subjective.

                  Alistar W-Q combo wasn't originally intended nor were most ability-flash combos, nor were a lot of other very common types of gameplay.

                  Likewise, there are other aspects of the game that have been "bugged" or work in a different way than you would expect for a very long time. For instance, the way chain CC works (where zhonya or flash mashing can work while you should be CC'd) has been wonky since the game first came out. We can't remake every single game that has had this happen.

                  [–]gnome1324 [非表示スコア]  (0子コメント)

                  Comparing Ali WQ to this bug is pretty unfair. This situation should never happen in the first place and the only reason it wasn't fixed is that it's usually such a niche problem that it wouldn't have a game-losing effect at least on such a public scale. I'm sure this has happened in solo queue many times just because of the sheer number of solo queue games worldwide, but it was likely either seen as a fluke or not noticed at all.

                  The bottom line is that this shouldn't happen at all. The text of the enchantment literally contradicts the actual gameplay which should not be allowed. Either the damage on the last tick of recall should interrupt the recall or the homeguard buff should not trigger. Being able to damage on the last tick is a longstanding bug which really shouldn't exist, but again it's never had such an obvious game-losing impact on such a public scale and everyone is used to it. There's no excuse for the homeguard bug though.

                  Lee Sin R->flash and other such skill->flash behaviors are bugs but it's become an accepted and known behavior. Same with Alistar. It wasn't intended, but they decided they liked it and allowed it to stay. This isn't the same.
                  This is an unintentional interaction that hasn't been acknowledged or dealt with, and Riot Nick Allen's statements prove this by them being blatantly incorrect. Seriously how hard is it to make a game and test this before you make a public statement?

                  [–]AChickenTender 1 ポイント2 ポイント  (17子コメント)

                  Somewhat but you have to compare it to something similar, refs will ALWAYS have a second opinion on a big and game ending shot. There is also MULTIPLE REPLAYS and CHALLENGE systems involved in contact sports. but again this game was OVER. the only way omg could have won is if a bug miraculously came into their game allowing them to save their nexus.

                  [–]peffi 0 ポイント1 ポイント  (12子コメント)

                  In soccer, the refferees decisions are instantaneous. Replays and slow-mos are not taken into account afterward, nor do refs wait for them. Just throwing that out.

                  [–]xpackageboyx 5 ポイント6 ポイント  (3子コメント)

                  Yeah and that is one of the most retarded things in soccer. So many bad referee calls has decided games before.

                  コメントをもっと表示する (8 返事)

                    コメントをもっと表示する (4 返事)

                      [–]URF_reibeer 0 ポイント1 ポイント  (1子コメント)

                      it's not the same thing. if in a game of soccer one goal would break down and make it impossible for the enemy team to score would you still say the game should normally be played to the end and count?

                      [–]Spreek 0 ポイント1 ポイント  (0子コメント)

                      No, that would count as something that made the game unplayable.

                      And I'm not saying that nothing should be done about bugs. If possible, the game should be paused and the bug fixed or whatever decision that needs to be made should be made.

                      Deciding to remake the entire game once its over and ESPECIALLY after the teams have already played other games is completely unfair.

                      [–]xSn0wball 0 ポイント1 ポイント  (4子コメント)

                      I have to disagree with this, if a referee makes a bad call in a football game well that is just human error right there but if the ball randomly changes to a sphere in the middle of being thrown then its not like the refs are gonna say ok well lets keep playing this and count it towards the standings. Although I'm doubtful riot will remake on the world stage.

                      [–]Spreek 0 ポイント1 ポイント  (3子コメント)

                      The refs would stop the game and get a new ball.

                      They wouldn't however, look at back at the replays 6 hours later, notice a penalty that they missed and then force the teams to play the full game over.

                      Especially not after one of the teams has already played another game. Standings can change your entire strategy in the next game.

                      [–]xSn0wball 0 ポイント1 ポイント  (2子コメント)

                      ok but lets say the ball was a deep pass caught for a touchdown and assuming the change of shape of the ball caused the defender to misplay the ball the defensive team would 100% have a legitimate case that the touchdown shouldn't be allowed especially if that touchdown lost them the game.

                      I know that is an extreme scenario but so is the "bug" that happened in the OMG FNC game today

                      [–]Spreek 0 ポイント1 ポイント  (1子コメント)

                      Well sure, and they would probably replay the play. And in an ideal world, Riot would design a system for replaying from a specific point in the game.

                      But once the game is over, there should not be any change in the game result or a remake.

                      [–]xSn0wball 0 ポイント1 ポイント  (0子コメント)

                      Can't say i disagree with your statement Riot really fucked themselves with the remake they already had at this point if it is determined that there truly was a bug I think they would have to remake but had riot not already done a remake with SK and GMB they could just admit a bug happened and maintain the result of the game without having to answer to as many complaints. Just my opinion tho.

                      [–]psycow_ 0 ポイント1 ポイント  (1子コメント)

                      ref calls are a human judgement which is entirely different from a bug in a software. its more like if you had a clear shot on the goal in extra time, the ball would suddenly implode and your team lost the game.

                      [–]Spreek 1 ポイント2 ポイント  (0子コメント)

                      Why does it matter if it's a human making a mistake or a computer program (written by a human) making a mistake?

                      Again, I'm not trying to say that bugs shouldn't be fixed by riot or that a bug caught WHILE THE GAME IS STILL GOING ON, shouldn't be remedied (or at least making an attempt).

                      But remaking the entire game AFTER IT IS DONE, and especially after the team has already played another game is absurdly unfair.

                      [–]ItsJoeShmo [非表示スコア]  (0子コメント)

                      But in contact sports if a bent hoop prevented a single shot maybe they would put the time back on the clock and replay that single play. Compare that to league where you have to replay the entire game including champ select.

                      [–]JohhnyDamage 0 ポイント1 ポイント  (0子コメント)

                      I can imagine...because it has.

                      [–]nevillebanks 0 ポイント1 ポイント  (0子コメント)

                      Its amazing how many people here who are completely ignorant of professional sports make comments like this. This exact thing can happen in both the NBA (when someone fouls out incorrectly) and MLB (games played under protest). However due to sheer ignorance it still gets upvoted.

                      コメントをもっと表示する (6 返事)

                        [–]cxcharlie 2 ポイント3 ポイント  (15子コメント)

                        don't you have to call a bug immediately for a remake?

                        [–]rallysmash 93 ポイント94 ポイント  (11子コメント)

                        If the enemy team gets more passive gold generation than your team, is it still your fault for not reporting the bug even though you couldn't even see it?

                        [–]peffi 11 ポイント12 ポイント  (6子コメント)

                        That's some fucking philosophy level shit right there.

                        Althoug there is an issue with this comparison. With the gold generation, assuming it's a comparably hard to notice amount, the other team has no way of knowing. In this case, fnatic had all the information available. They just didn't think about it in the heat of the moment or weren't sure.

                        [–]rallysmash 24 ポイント25 ポイント  (2子コメント)

                        Yeah my comparison was just to show that this rule is not really good. You can't expect players to be scouting for bugs when they are focusing on playing the game, especially in such an intense situation.

                        [–]MittenMagick 20 ポイント21 ポイント  (1子コメント)

                        Yeah, what is Fnatic supposed to do, watch every last bit of every champion's health bar? That's a ridiculous basis for a judgment call like this one.

                        [–]Bloodrager[Splat] (EU-W) 2 ポイント3 ポイント  (0子コメント)

                        This. Putting aside whether this was working as intended or not I feel that if a categoric bug took place under similar circumstances you'd have to take into account the context in which it occurred. Saying 'You didn't pause!' 5 minutes in for a bug when there's no pressure is worlds apart from the ending of the Fnatic/OMG game.

                        [–]PaidToSpillMyGuts 0 ポイント1 ポイント  (1子コメント)

                        Okay, imagine being in Fnatic's shoes, where you think there may have been a bug. But pausing the game 72 minutes in after failing to take the win by one auto-attack makes you look like the kid on the playground who calls time-out before they get tagged. If they had paused, and it wasn't actually a bug, they would have been humiliated on an international stage. Its not fair to put them under that kind of decision-making pressure in the middle of a game.

                        [–]CyndromeLoL [非表示スコア]  (0子コメント)

                        Exactly. I don't think Rekkless was sitting there like hmm hey ref my bio-arcane barrage actually did damage to his health bar and here's my screenshot that I took. It's a fucking 70 minute game, and you're expecting them to track small shit like that? Just because it's nearly impossible for them to catch it doesn't change the fact that it's a serious problem that shouldn't have happened and pretty much cost Fnatic the game. (1 auto away is so damn close that you really can't say that it was anyone's game).

                        [–]Beercules1993 5 ポイント6 ポイント  (0子コメント)

                        10/10

                        [–]Pxtxr 0 ポイント1 ポイント  (0子コメント)

                        ARE U A LAWYER?

                        コメントをもっと表示する (2 返事)

                          [–]IndySkylander 4 ポイント5 ポイント  (0子コメント)

                          Referees have discretion for remaking after a match has ended.

                          [–]trevcat9 0 ポイント1 ポイント  (0子コメント)

                          No. Pausing and pointing out a bug is one of the ways to get a remake, but WCE officials can make a remake at any time if it is considered critical.

                          8.4.2 Restarts After GOR. The following are examples of situations in which a game be restarted after GOR has been established.

                          8.4.2.1 If a game experiences a critical bug at any point during the match which significantly alters game stats or gameplay mechanics.

                          From the worlds rulebook.

                          コメントをもっと表示する (1 返事)

                            [–]Its_not_him 0 ポイント1 ポイント  (0子コメント)

                            Stuff like this won't cause a rematch. Bugs have happened in pro games before and rematches pretty much never happen.

                            コメントをもっと表示する (2 返事)

                              [–]Maksago_ 45 ポイント46 ポイント  (31子コメント)

                              I would guess it has something to do with recall immunity

                              [–]JeyJ24 28 ポイント29 ポイント  (26子コメント)

                              THANK YOU.

                              You aren't in combat during the last moment of recall. It's the way the game is programmed. That's why homeguard activated.

                              [–]Fgame 17 ポイント18 ポイント  (1子コメント)

                              The tooltip on Homeguards quite clearly states 'Taking or dealing damage within the last 6 seconds', not being in combat. As is shown by the second half of the video, where he walks into the fountain instead of recalling, shield damage DOES count as damage to a character, contrary to what NickAllen said in his tweet.

                              [–]omgitsniklas 2 ポイント3 ポイント  (0子コメント)

                              There is a video clearly showing, where a guy made khazix running through kogs slow into fountain, taking 0 dmg just getting slowed, dont get homeguard procs. this is just the proof that hg works just like the out of combat thingy.

                              EDIT: typo.

                              [–]Mionee[🍰] 19 ポイント20 ポイント  (18子コメント)

                              But, the thing is... you are in combat. Mobi boots are cancelled after the recall if you try the same thing.

                              Completing a recall just happens to trigger the Homeguard effect, regardless of whether you are in combat or not, and this is the bug.

                              The 'other' bug is that, despite their tooltip stating that Homeguard rely on damage rather than combat, all evidence points to Homeguard relying on combat, since even non-damaging cc effects can prevent it from being applied, or break it. And quite frankly I think everyone assumed it was the case anyway? The 'damage' thing is a tooltip technicality noone even knew about a few hours ago, which even official patch notes contradicted.

                              (Obviously, whoever coded this just thought you'd never be in combat after completing a recall. It's an oversight, like most "bugs" in video games nowadays.)

                              [–]LeCthulhu[Rhythmalism] (NA) 10 ポイント11 ポイント  (17子コメント)

                              Nick Allen already said homeguard is not dependent on being in combat, but taking damage. Vman even posted screenshots showing that KhaZix did not take damage. Just let it go, honestly.

                              [–]Reishun 7 ポイント8 ポイント  (6子コメント)

                              one of the videos shows someone clearly taking damage in that 0.5 seconds that you cant be interrupted on recall, the damage still applied but Homeguards still activated that's inconsistent with the tooltip.

                              [–]LeCthulhu[Rhythmalism] (NA) 0 ポイント1 ポイント  (5子コメント)

                              https://i.imgur.com/lj5z5FV.jpg no damage taken. also, homeguard always activates on recall. Recall has an immunity period about half a second before you teleport. It worked as intended regardless.

                              [–]Reishun 4 ポイント5 ポイント  (4子コメント)

                              you miss what I mean, someone displayed a video in which someone autoattacked in the 0.25 period and the champion clearly took damage NOT immune the only thing that was immune was the recall. The homeguard then procced despite the fact that they took damage which is contrary to what the tooltip says, homeguard is meant to rely on the recent damage taken not the success of a recall.

                              If it is intended that the shield blocks damage therefore allowing homeguard to be procced then it should work from walking to fountain as well as recalling.

                              Something here is clearly unintended.

                              [–]Mionee[🍰] 5 ポイント6 ポイント  (4子コメント)

                              Nick Allen already said homeguard is not dependent on being in combat, but taking damage.

                              And he is wrong. It has been proven with countless videos now. The tooltip is wrong, the latest official patch notes regarding Homeguard contradict that tooltip, and all evidence lead to Homeguard working just like Mobi boots.

                              The question is "is it actually intended for a recall to trigger Homeguard even though you do not meet its requirements?". The answer can be yes or no.

                              Personally, I think 'no' is the answer, and that it is simply an oversight, aka a bug. A point could be made for the opposite opinion; regardless, the answer isn't "damage absorbed by shields do not cancel Homeguard", hence why people aren't satisfied with Nick Allen's statement.

                              [–]kinsano 1 ポイント2 ポイント  (0子コメント)

                              If the tooltip is wrong isnt that a bug in itself? If homeguard had cancelled even tho he took no damage and fnatic had won couldn't we be flocking to reddit with a thread about how he took no damage and homeguard clearly states it cancels upon taking damage?

                              [–]Zaeron[Zaeron] (NA) 1 ポイント2 ポイント  (2子コメント)

                              "is it actually intended for a recall to trigger Homeguard even though you do not meet its requirements?".

                              Except that you do meet its requirements. Homeguard has two requirements to trigger:

                              1) You walk into fountain and haven't taken damage for the last 8 seconds.

                              2) You recall to fountain.

                              EITHER of those situations will trigger homeguard.

                              [–]Mionee[🍰] 0 ポイント1 ポイント  (1子コメント)

                              The tooltip doesn't state anything regarding recalling, nor does it hint at it either. The tooltip simply states that it is disabled if you dealt or have taken damage in the last 6 seconds. It has been proven to be, in reality, disabled if you have been in combat in the last 6 seconds.

                              This is the only requirement. (besides the obvious one of being located within the starting platform.)

                              You're more or less saying 'X is not a bug' and justifying it with 'X happens in-game'. It's circular reasoning.

                              [–]Zaeron[Zaeron] (NA) 0 ポイント1 ポイント  (0子コメント)

                              X is not a bug because X has worked this way for more than a year and has been repeatedly observed to occur and is widely known to be the way that X functions.

                              Even if you wish to define X as a bug, X should not result in a game remake because X impacts both teams exactly equally and both teams gain exactly the same benefit from the mechanic X. Unlike a champion bug, X is not limited to being taken advantage of by a single team.

                              Further, unlike most bugs, X is widely known to be a thing and it has frequently impacted games in the past to some extent (see games where people tried to stop backs and they got away and instantly got homeguard in order to defend inhibs and such). It is commonly known that when you recall, you gain the benefit of X mechanic instantly.

                              Therefore, calling X a bug is a little strange, since X has worked the way it works since the mechanic was introduced, and has never been changed in any way, and is commonly known. Even if it were initially a bug, after existing and being widely used for more than a year, it has simply become part of the mechanics of the game.

                              [–]NeverPull0ut 1 ポイント2 ポイント  (1子コメント)

                              Yeah it's moments like these where unfortunately the League community really shows their age. It was the same thing with TSM vs Frost back in season 2.

                              [–]LeCthulhu[Rhythmalism] (NA) [非表示スコア]  (0子コメント)

                              People complaining about $3000 fines when Azubu Frost was fined like $30k lol. Circle jerking really gets annoying on this subreddit.

                              [–]leagueplanet 0 ポイント1 ポイント  (0子コメント)

                              homeguards won't apply after being affected by non-damaging cc (kog slow, not the damage part for example) and walking into fountain, you have to wait the full cooldown time before homeguards applies.

                              so in actuality, homeguards activating does depend on being in combat, its just that recalling overrules everything and grants homeguards regardless. whether that's intended or not is the question.

                              [–]typhyr [非表示スコア]  (0子コメント)

                              And others have posted videos showing that taking damage that is FULLY shielded by maw keeps homeguard from activating for 6 seconds. So clearly, the game counts shielded damage as "taken damage," in the case of homeguards.

                              The bug lies with recall. Either it's intended and they need to clarify that recall automatically applies homeguard buff, or it's not intended and recall should not automatically apply homeguard buff.

                              [–]PapaButcher [非表示スコア]  (0子コメント)

                              https://twitter.com/VManSeven/status/515925764621877248

                              [–]cosmicoceans 1 ポイント2 ポイント  (0子コメント)

                              KhaZix had the living artillery debuff on him though, even as he was in the fountain.

                              [–]PaidToSpillMyGuts 1 ポイント2 ポイント  (0子コメント)

                              If you're really "immune" then you shouldn't be able to take the kog-passive, cc upon landing or damage on the pad. but you do.

                              コメントをもっと表示する (2 返事)

                                [–]typhyr [非表示スコア]  (0子コメント)

                                I would guess that recall forced homeguards to start, regardless of ANYTHING else.

                                Homeguards are put on cooldown when taking fully-shielded damage, in that you can't activate them for 6 seconds after being hit. Taking damage while shielded is still taking damage, according to the game code.

                                Either recall literally makes damage taken in the last .5 seconds not count as damage, or recall has a command that immediately initiates homeguards on successful cast, which may be likely. Or successful recall cast resets the timer for homeguard, which would be a weird way to do that.

                                コメントをもっと表示する (3 返事)

                                  [–]Tymat 19 ポイント20 ポイント  (1子コメント)

                                  This is the video everyone needs to see. Remake or not, http://i.imgur.com/2ecE4zT.jpg

                                  [–]chollyer [非表示スコア]  (0子コメント)

                                  I'd like to see another video where Garen has a Maw and encounters a similar situation. Does his passive reset, or no? The passive has the same language in game as homeguards (setting aside the troubling difference between the patch notes and tool tip). If it doesn't reset, then maybe there is some consistency to this "not taking damage" bit.

                                  [–]lolAxle 10 ポイント11 ポイント  (2子コメント)

                                  DID HE GET THE ZED?!

                                  [–]ErickX 31 ポイント32 ポイント  (77子コメント)

                                  THIS.CHANGES.EVERYTHING.

                                  Or it should at least. It clearly proves that it's a bug. (For this threat, i really sugges we stop reffering to Kha'zix as a bug ok? )

                                  [–]BusinessCashew 57 ポイント58 ポイント  (46子コメント)

                                  It might be a bug, but if that's how it works for all recalls there definitely shouldn't be a remake. It's an unintended mechanic, but it's still a consistent mechanic that's a part of the game on the patch they're playing. We can't just go back and remake every single game where this bug occured if it happens every single time you take damage during the recall immunity period. It's like going back and replaying every single game with a Shyvana when her E was doing 20 damage more than it said on the tool tip. It's a bug, but it's not game breaking, it's a consistent game mechanic.

                                  [–]fr33noob1 15 ポイント16 ポイント  (4子コメント)

                                  To be fair...the new rule of the 6 second delay on home guard is fairly new and it can be safe to assume there has not been an instance where it affected a game to this degree...It quite literally decided the game, let's be honest.

                                  New patch...new bug. Specifically the interaction between home guard and recall. I see it hard to make a decision here though.

                                  [–]dresdenologist 7 ポイント8 ポイント  (2子コメント)

                                  It might be a bug, but if that's how it works for all recalls there definitely shouldn't be a remake.

                                  This is sort of the key. If this is the intended behavior on recall's last .5 seconds, then this would have happened regardless of the items and is perhaps overlooked design on a very granular level, but not a bug. If it only happens with homeguard'd mercs then there's a problem.

                                  I don't know if a remake should happen (highly unlikely given the decision already rendered) but this has to make a case for revising the rules for challenging bugs in-game, such as allowing the coach to do so in a limited quantity like in traditional sports. Putting the onus on just the players to call for a pause due to a bug is hard because of how intense the games are and how the players are reacting. But the coach is under no such pressure and can be watching the game to challenge any potential issues. As long as the circumstances are written so that it can't be abused I think this is a good way to introduce proper in-game investigation of bugs and issues so that we're not waiting after the fact on a potential remake.

                                  Still, remaking an entire game is frankly a huge decision in and of itself. In the worst case scenario I see this like you would in regular sports where things happens all the time that perhaps aren't right but the game (and results) typically stand. I'm not sure how I feel on the issue as it applies to League.

                                  [–]Ndukaoo 0 ポイント1 ポイント  (1子コメント)

                                  But no one was aware of this bug before it had happened. So you can assume and imply that the bug was abused. In this scenario, OMG COULD have known this would happen, it being a close game and what not. I'm not saying they did know, but the possibility is always left open, because NO ONE knew this would/could happen. This is the problem with bugs. In the SK vs Gambit match, the game was paused, BY THE PLAYERS, not by riot officials, SO it's up to THEM to see it coming. Imagine if soaz CAUGHT the bug in some way and called for a pause. then this would be a whole different story, i promise you.

                                  [–]Qari [非表示スコア]  (0子コメント)

                                  I've known about this for a long time. There is immunity in the last .5 seconds of recall from being put back in battle. It's been this way for as long as I can remember. If you hit an MF who is porting she doesn't lose her strut, for instance.

                                  [–]MKE7 21 ポイント22 ポイント  (6子コメント)

                                  That would mean that every reproducible bug can be labeled as an unintended mechanic.

                                  [–]fran13r 4 ポイント5 ポイント  (4子コメント)

                                  Not if they're specific to a champion or a certain circumstance, this is consistent with every champion and with every form of damage.

                                  IMO it should stay this way, recalling successfully should give you an advantage and your opponent should be punished for not stooping you in time.

                                  [–]MittenMagick 5 ポイント6 ポイント  (3子コメント)

                                  Except there already is the advantage of "I did damage to you but you got the recall anyway." They shouldn't get the added benefit of homeguards. It changes a game, especially in this one.

                                  [–]fran13r 0 ポイント1 ポイント  (2子コメント)

                                  That's not an advantage, that's your opponent failing to stop you. If you manage to get passed the immunity you should be rewarded, not punished by taking away your homewards.

                                  [–]MittenMagick 1 ポイント2 ポイント  (0子コメント)

                                  Getting a recall even though damage was done to you is the reward. Multiple times I took damage while I was low health during the last bit of a recall. If my recall had been interrupted, I would've had to stay and die. Thanks to getting passed the immunity, I got to leave, but I should not get my homeguards as those clearly state that taking any damage delays it by 6 seconds. There is no immunity for that.

                                  Damage was taken = no homeguards.

                                  EDIT: And to be clear, "damage taken" does not mean a drop in health bar. This has been shown many, many times already.

                                  コメントをもっと表示する (1 返事)

                                    [–]justMate 0 ポイント1 ポイント  (0子コメント)

                                    Let's adopt doublespeak as out language friends.

                                    [–]IndySkylander 5 ポイント6 ポイント  (0子コメント)

                                    Yeah, key is consistency. If anything this sounds like a problem with the wording in tooltips.

                                    [–]Enziguru 2 ポイント3 ポイント  (4子コメント)

                                    I agree with this. Since this occurs with every recall I don't think it should be remade. Or else we would need to remake all the games where this bug has happened because it might've changed the outcome.

                                    [–]androth 7 ポイント8 ポイント  (1子コメント)

                                    i think what makes it very special this time is that it could have potentially changed the outcome of the match a lot, which would possible change the way the whole group ends dramatically.

                                    [–]Enziguru 0 ポイント1 ポイント  (0子コメント)

                                    When Shen was bugged no game was remade when the teleport failed, no matter how gamechanging it was. Some even used the bug intentionally to remain in lane. Now it's a bug that affects a fan favorite and everyone starts begging for a remake. I realize I might be a bit harsh but games aren't only decided on the last 3 seconds.

                                    [–]tapanojum 0 ポイント1 ポイント  (0子コメント)

                                    I disagree. No need to remake "All the games". This bug is so minor that it has never been noticed in the past.

                                    The only reason we are aware of it now is because a very unlikely and bizarre situation occurred where that bug guaranteed OMG's victory. The nexus was 1 auto away from death.

                                    [–]Laranjack 0 ポイント1 ポイント  (0子コメント)

                                    this has nothing to do with stopping the recall but how the homeguards still activate against the tooltip and in different circunstances it acts like the tooltip AND ANY PATCH NOTES states this makes no sense and it has been shown that this is not as intended for sure, if its not as intended it's a bug...

                                    [–]maxm0 0 ポイント1 ポイント  (0子コメント)

                                    This needs to be sent to the top

                                    [–]RDName 0 ポイント1 ポイント  (0子コメント)

                                    It's an unintended mechanic

                                    so a bug

                                    [–]tapanojum 0 ポイント1 ポイント  (0子コメント)

                                    This bug is absolutely minor and most unimportant, there would not be any reason to remake every single game this bug has occurred.

                                    However, in the Fnatic vs OMG game, this bug was the sole reason why the backdoor failed and OMG won the game. It's HUGE in this particular situation!

                                    [–]typhyr [非表示スコア]  (0子コメント)

                                    Then they should clarify it as a consistent game mechanics. Add it to the homeguard enchant tooltip. "Recall triggers Homeguard buff regardless of damage taken or dealt."

                                    コメントをもっと表示する (21 返事)

                                      [–]123tejas 9 ポイント10 ポイント  (29子コメント)

                                      Yeah, thing is if Riot choose not to remake, they HAVE to leave this bug in the game. Would be so BM to say its not a bug and then change the "homeguard interaction" in season 5.

                                      [–]grimeguy 10 ポイント11 ポイント  (26子コメント)

                                      Not at all. You don't remake every game that a bug happens in.

                                      [–]acemzz 14 ポイント15 ポイント  (23子コメント)

                                      You do if the bug impacts the outcome of the game, though.

                                      [–]grimeguy 1 ポイント2 ポイント  (21子コメント)

                                      Every bug impacts the outcome of the game in some way. Fnatic still had chances to win the game that they mechanically failed to accomplish after the bug occurred.

                                      [–]tapanojum 6 ポイント7 ポイント  (3子コメント)

                                      Bad logic, technically everyone still has a chance to win the game at nearly any given point in the game. SK vs Gambit, SK still had a chance to win the game but they still remade it because they noticed a bug with Aatrox early on in the game.

                                      Fnatic won this game with the backdoor, the bug stopped that victory.

                                      [–]grimeguy -1 ポイント0 ポイント  (2子コメント)

                                      Fnatic won this game with the backdoor, the bug stopped that victory.

                                      No. You don't know what would've happened if the homeguard had been interrupted.

                                      SK vs Gambit, SK still had a chance to win the game but they still remade it because they noticed a bug with Aatrox early on in the game.

                                      The game was remade because that was what the rules said to do. The rules don't apply the same way to this game, like that or not.

                                      [–]tapanojum 3 ポイント4 ポイント  (1子コメント)

                                      I don't know what would've happened 100%, but we can make some pretty safe guesses of what would have likely happened.

                                      1) Rumble kills the low hp Kha'Zix and continues to auto Nexus 2) Everything plays out the same way except Kha'Zix doesn't get the homeguard speed boost and Rumble has time to do 1 or 2 more autos on the Nexus 3) OMG wins bug or no bug

                                      This game was 1 auto attack from victory. Although it looks like Fnatic should have won had that bug not occurred, we can't say that for sure. Which is why I'm not asking for Fnatic to be awarded a win here, just a REMATCH.

                                      There is no denying that this bug had an unbelievable impact on the game. Probably the biggest impact a bug has ever had on the outcome of a game.

                                      If riot allows the integrity of their game to fall apart like this, their goals of making esports into something more can go out the door.

                                      [–]grimeguy 0 ポイント1 ポイント  (0子コメント)

                                      Hyperbole.

                                      コメントをもっと表示する (17 返事)

                                        [–]PlasmaCross 1 ポイント2 ポイント  (0子コメント)

                                        If this bug didn't interact with the game, then I'd like to know why the SK vs GMB did.

                                        コメントをもっと表示する (2 返事)

                                          コメントをもっと表示する (2 返事)

                                            [–]Destello 4 ポイント5 ポイント  (2子コメント)

                                            What is and what is not a bug is subjective to the expected behaviour. The expected behaviour is what the tooltip says. According to the tooltip what happened to the match is correct. The other cases are bugs.

                                            [–]Ravenhelm 0 ポイント1 ポイント  (0子コメント)

                                            Wrong, tooltips are basic information for newcomers. Relevant and more specific information about such details is found on the wiki or patch notes (like our issue). Otherwise we would have 5-meters-long tooltips with ap ratios and such.

                                            [–]MrHippopo 0 ポイント1 ポイント  (0子コメント)

                                            No, it is not. Maw should activate upon taking magic damage according to the tooltips, thus damage was taken if Maw activates. If damage was taken > no homeguard.

                                            [–]Vasterole[Vasterole] (EU-W) 1 ポイント2 ポイント  (0子コメント)

                                            I think it's ok if they don't remake it but they have to admit that this bug occured because Nick Allen has been spreading a lot of unresearched bullshit in the hours after this.

                                            [–]NazZuto 5 ポイント6 ポイント  (1子コメント)

                                            Wow it's a bug. This video really highlights it nicely as well. You should send this over to Riot promptly I think a remake is in order to be honest.

                                            Especially considering all the nonsense Riot created over the Gambit vs SK situation from what I can see Riot may have no choice but to remake.

                                            [–]Kingprawn2 1 ポイント2 ポイント  (0子コメント)

                                            But then you have to ask which one is the bug? The bug could be happening when you aren't recalling. The game thinking that you took damage when you really didn't. It's like in football when they have a review there must be indisputable evidence that the call was wrong. All this video does is make the play disputable and therefore the call should stand.

                                            [–]PapaButcher 5 ポイント6 ポイント  (1子コメント)

                                            It is indeed proof that there was a bug in that game, and frankly speaking, it was the game deciding factor. For people, that say that the shield was activated by sOAZ's ultimate even if that is the case, you can clearly see from the VODs and the images when that KhaZix came to the fountain Rekkles's ult hit him prior to base. This alone, should mean that there is a bug.

                                            It doesn't matter who dealt the damage, or popped the shield. There are a ton of videos demonstrating how Riot failed to include the recall scenario when they implemented the homeguard effect. They failed to realize that people can get hit within the last few seconds returning to base. They don't have game logic to deal with this situation in a recall. (In Riot's mind, recall avg 6-7 seconds - therefore, apply homeguard effect when user returns to base which is completely wrong)

                                            TLDR: As previously stated, you'll need to be out of combat (not take any damage) for at least 6 seconds for the homeguard effect to take place. This does not take into account recalls at all, which means there is broken functionality.

                                            [–]schmanthony 0 ポイント1 ポイント  (0子コメント)

                                            Yep, there's no question that this interaction between recall - damage - homeguard conflicts with homeguard's tooltip. Anyone still arguing otherwise hasn't looked at the evidence.

                                            Here's why there won't be a remake regardless of whether Nick Allen admits he's wrong:

                                            Upon discovering the bug, the disadvantaged team correctly paused and identified the problem, which was easily visible and verifiable upon replay.

                                            That's from Riot's statement on the remake of the Gambit/SK game. In order for a remake to happen, the team has to pause, identify the bug to the referee, and decide whether or not to remake pending the ref's call. All this has to occur during the course of the game.

                                            As successful as reddit has been this time in breaking down this scenario, it's not going to bring a remake.

                                            [–]BackInRed 2 ポイント3 ポイント  (1子コメント)

                                            Your move, Nick Allen

                                            [–]Bronze94 1 ポイント2 ポイント  (0子コメント)

                                            Involves Gambit? No.

                                            Guess no remake.

                                            [–]Vanilla7050 1 ポイント2 ポイント  (1子コメント)

                                            Sorry but, he takes ZERO damage after home guards activate until he fights with Rumble, so where is the bug? He does take damage before hand, but not after...

                                            [–]iBIinked [非表示スコア]  (0子コメント)

                                            Homeguard only activates if the champion has not been in combat for 6 seconds. The bug is rarely noticeable because the recall time is normally enough to proc the homeguards, except it seems that Khazix took damage right before he recalled to base and homeguards still somehow procced.

                                            [–]Devastrator 1 ポイント2 ポイント  (1子コメント)

                                            Someone should tweet this to Nick Allen, "Maybe you should check your code..." I don't have a twitter account, so unfortunately I can't.

                                            [–]Vixerox 1 ポイント2 ポイント  (0子コメント)

                                            I've tweeted it at him already, as i'm sure multiple others have

                                            [–]Zed_or_AFK 0 ポイント1 ポイント  (0子コメント)

                                            I love you just go HAM on your mates after the test!

                                            [–]depredator56 0 ポイント1 ポイント  (0子コメント)

                                            that shows that having maw of malmortius is irrelevant, kha take a physical damage in the last second of recall and HG works instantly when he arrived at the fountain. (sorry for bad english)

                                            [–]oxYnub[oxYzjeaaaaah] (EU-W) 0 ポイント1 ポイント  (0子コメント)

                                            Not really, it actually proves the exact opposite. Homeguards while recalling are bugged

                                            [–]Darzee96 0 ポイント1 ポイント  (0子コメント)

                                            That's it, nice video, please remake!

                                            [–]jonsonsama 0 ポイント1 ポイント  (0子コメント)

                                            Aren't these games played on a different patch?

                                            [–]Infernosaint 0 ポイント1 ポイント  (0子コメント)

                                            This just shows that there is a difference between recalling and not recalling. The problem is, SHOULD proccing Maw shield count as taking damage or not? You don't take actual damage, and according to wording of Homeguards, I would say no. But apparently it is coded as though it should, but recalling negates that.

                                            This makes it far too easy for Riot to just say "It's supposed to work as in the FNC vs OMG game, and the fact that it doesn't work like this, when just running to fountain, and not recalling, is a bug." :(

                                            [–]melgibson666 0 ポイント1 ポイント  (0子コメント)

                                            I wanna have a conversation with Nick Allen to see if he really believes his own bullshit and that this isn't a bug.

                                            [–]SupDoodlol 0 ポイント1 ポイント  (0子コメント)

                                            "Definitive proof of a recall bug"

                                            Homeguard is coded so that you get the speed buff if you successfully recall. Because in that scenario, you would have had to avoid damage for 7-8 seconds. There is nothing wrong with coding the item like that. The problem is that the recall damage bug exists. Calling that a recall bug is saying that they should have programmed the item to work "correctly" in it's interaction with another bug.

                                            [–]L43 0 ポイント1 ポイント  (0子コメント)

                                            Homeguard should proc when you walk into the fountain according to the tooltip. You technically found a bug, just the wrong one (or so Riot will say). They need to add to the tooltip about the buff not being applied if damage has been received in the last 6 seconds, and porting cancelling the effect. I think it's otherwise working as intended (unfortunately).

                                            [–]Penthakee [非表示スコア]  (0子コメント)

                                            The beautiful thing is that this is a 2-in-1 bug.

                                            1) why does he have homeguard

                                            2) why the fuck can he even recall. Dmg should stop recalls. This bug is in the game for a long time. You get damaged in the last moment, you still finish the recall.

                                            [–]FreddyKirderph [非表示スコア]  (0子コメント)

                                            http://gyazo.com/6851508d441572a14c0c2be2d685cc54 Just putting it in here.... :P

                                            [–]MaxPayne4life [非表示スコア]  (0子コメント)

                                            Upvote this to the top.

                                            [–]crimsomreaper -4 ポイント-3 ポイント  (2子コメント)

                                            leave it to /r/leagueoflegends to find a way to mess up a great game;if fnatic would've won you guys would just look for a bug to save omg

                                            [–]AChickenTender 1 ポイント2 ポイント  (0子コメント)

                                            thank you for this,it's so sad to see a win (literally taken away) because of a bug.

                                            [–]hearthstoneisdumb 0 ポイント1 ポイント  (0子コメント)

                                            There's nothing to say against that anymore

                                            [–]Elyou243 1 ポイント2 ポイント  (0子コメント)

                                            need to get u as the top comment.

                                            [–]veystass 1 ポイント2 ポイント  (0子コメント)

                                            This definitely shows inconsistency with the taking damage with/without maw shield. I don't think it deserves a remake, but at least they can fix the bug so it doesn't happen again.

                                            [–]Dolgan 0 ポイント1 ポイント  (1子コメント)

                                            How does this proof that there was a bug in the Fnatic game? The official Riot answer is: 1. Maw shield was procced from Kog ult. 2. Shield absorbed damage. 3. Kha'Zix got no damage. 4. Homeguard activates if you take no damage. 5. Points 1-4 are intentionally coded this way.

                                            [–]Meckel 0 ポイント1 ポイント  (0子コメント)

                                            it proves , that the matter is not with maw , but with the backcall granting homeguard. 1 clip is showing how a Kha backcall , getting hit with almost full hp ( so no maw procc), and he is still getting homeguards

                                            [–]Braintje 1 ポイント2 ポイント  (0子コメント)

                                            HAHAWHAHAHAWHAWHAWHAW

                                            [–]samacora 1 ポイント2 ポイント  (0子コメント)

                                            /u/riotmagus well?

                                            コメントをもっと表示する (13 返事)