|
Unfounded matchfixing accusations are not welcome. Refrain from making off-the-wall accusations without concrete evidence. |
On September 28 2014 13:04 chalice wrote:Show nested quote +On September 28 2014 12:01 dDazed wrote:
Out of curiosity what are the Chinese fans saying about the Homeguard bug? Anyone know? my guess is that most aren't even aware of it because it is such a non-issue.
Sure, when the bug is in your favor, it's easily dismissed as a non-issue. :D I wonder if people who have a hard time accepting or comprehending the term "taking damage" are Fnatic haters, or those football (soccer) lovers who thinks it's completely fine if referee's blindness sends home teams from international events, because "it's part of the game".
And as I said, if the same scenario would've happened between contenders to the first place, Riot would have to remake. Anyway, the most annoying thing for me is simply that Nick Allen can'release a statement that actually talks about the bug, and not bs like maw shield, which only shows he has no idea - or wants to have none - what was the problem in the first place.
|
On September 28 2014 14:25 Volband wrote:Show nested quote +On September 28 2014 13:04 chalice wrote:On September 28 2014 12:01 dDazed wrote:
Out of curiosity what are the Chinese fans saying about the Homeguard bug? Anyone know? my guess is that most aren't even aware of it because it is such a non-issue. Sure, when the bug is in your favor, it's easily dismissed as a non-issue. :D I wonder if people who have a hard time accepting or comprehending the term "taking damage" are Fnatic haters, or those football (soccer) lovers who thinks it's completely fine if referee's blindness sends home teams from international events, because "it's part of the game". And as I said, if the same scenario would've happened between contenders to the first place, Riot would have to remake. Anyway, the most annoying thing for me is simply that Nick Allen can'release a statement that actually talks about the bug, and not bs like maw shield, which only shows he has no idea - or wants to have none - what was the problem in the first place.
it's a non issue because it's literally 1 variable than fnatic had no control of, meanwhile they managed to fuck up that backdoor with 30 other fucking mistakes.
|
On September 28 2014 14:29 wei2coolman wrote:Show nested quote +On September 28 2014 14:25 Volband wrote:On September 28 2014 13:04 chalice wrote:On September 28 2014 12:01 dDazed wrote:
Out of curiosity what are the Chinese fans saying about the Homeguard bug? Anyone know? my guess is that most aren't even aware of it because it is such a non-issue. Sure, when the bug is in your favor, it's easily dismissed as a non-issue. :D I wonder if people who have a hard time accepting or comprehending the term "taking damage" are Fnatic haters, or those football (soccer) lovers who thinks it's completely fine if referee's blindness sends home teams from international events, because "it's part of the game". And as I said, if the same scenario would've happened between contenders to the first place, Riot would have to remake. Anyway, the most annoying thing for me is simply that Nick Allen can'release a statement that actually talks about the bug, and not bs like maw shield, which only shows he has no idea - or wants to have none - what was the problem in the first place. it's a non issue because it's literally 1 variable than fnatic had no control of, meanwhile they managed to fuck up that backdoor with 30 other fucking mistakes.
See, the way you see it is why you think it's a non-issue. You think because they screwed up a bug or two should not matter. It's no how it works. If you miss an easy goal, than it gives the referee the option to not give a red card to someone who kicks the shit out of you, because "well he played shit anyway", lol.
Does homeguard says it won't activate for 6 seconds if the user takes damage? Yes, it is written, it is clear as day. Does homeguard activate if you take damage at the end of recall? Yes, it does. Did the nexus was 1 hit away from destruction? Yes, it was. Is it 100% safe to say the homeguard bug did not affect the outcome at all? No, it's not, it's highly questionable - we can argue about it, but no one can be 100% sure.
I'm not mad about one of these teams winning or losing because of that either, they did not play well - wel, most of them -, but it can not justify denying the opportunity for a rematch after an obvious bug. Or adress it at least! Say something stupid that taking damage at the end is just an illusion, we are all drunk, case closed. Instead Nick Allen says it was the maw shield, which has been proven to be wrong.
|
Bearded Elder29904 Posts
Seems like C9 is pretty much fucked up. Last 3 games are Alliance/C9 vs Kabum - both wins should go to LCS teams and last one is C9 vs NWS, gg C9? I don't think they can repeat what Alliance did to Koreans.
|
I think it's a difficult call whether to say it should be replayed or not. Nothing inconsistent with the usual game mechanics happened, iirc, it's been reproduced that you always get homeguard when you recall after taking damage in the last half second.
When it comes to things like this, there will be certain ambiguities to how the engine mechanics work. To call for a rematch because an engine mechanic works differently to how spectators thought it would is a bit silly. Let's be honest, it's not as if Rekkles hit Loveling before his recall and thought "good, now he won't have homeguards" or something.
|
On September 28 2014 14:57 739 wrote:
Seems like C9 is pretty much fucked up. Last 3 games are Alliance/C9 vs Kabum - both wins should go to LCS teams and last one is C9 vs NWS, gg C9? I don't think they can repeat what Alliance did to Koreans.
Honestly, no team can really repeat what happened in that game. I don't think I'll see a Korean team repeat something like that either. I've never seen a game go that well for any team ever. Everything worked for Alliance, and they kept calm/controlled throughout the game. The fact that they seemed to have been aiming for that goal is amazing.
On September 28 2014 15:01 Shiznick wrote:
I think it's a difficult call whether to say it should be replayed or not. Nothing inconsistent with the usual game mechanics happened, iirc, it's been reproduced that you always get homeguard when you recall after taking damage in the last half second.
When it comes to things like this, there will be certain ambiguities to how the engine mechanics work. To call for a rematch because an engine mechanic works differently to how spectators thought it would is a bit silly. Let's be honest, it's not as if Rekkles hit Loveling before his recall and thought "good, now he won't have homeguards" or something.
I really like this post. Too bad people will ignore your points.
|
On September 28 2014 14:36 Volband wrote:Show nested quote +On September 28 2014 14:29 wei2coolman wrote:On September 28 2014 14:25 Volband wrote:On September 28 2014 13:04 chalice wrote:On September 28 2014 12:01 dDazed wrote:
Out of curiosity what are the Chinese fans saying about the Homeguard bug? Anyone know? my guess is that most aren't even aware of it because it is such a non-issue. Sure, when the bug is in your favor, it's easily dismissed as a non-issue. :D I wonder if people who have a hard time accepting or comprehending the term "taking damage" are Fnatic haters, or those football (soccer) lovers who thinks it's completely fine if referee's blindness sends home teams from international events, because "it's part of the game". And as I said, if the same scenario would've happened between contenders to the first place, Riot would have to remake. Anyway, the most annoying thing for me is simply that Nick Allen can'release a statement that actually talks about the bug, and not bs like maw shield, which only shows he has no idea - or wants to have none - what was the problem in the first place. it's a non issue because it's literally 1 variable than fnatic had no control of, meanwhile they managed to fuck up that backdoor with 30 other fucking mistakes. See, the way you see it is why you think it's a non-issue. You think because they screwed up a bug or two should not matter. It's no how it works. If you miss an easy goal, than it gives the referee the option to not give a red card to someone who kicks the shit out of you, because "well he played shit anyway", lol. Does homeguard says it won't activate for 6 seconds if the user takes damage? Yes, it is written, it is clear as day. Does homeguard activate if you take damage at the end of recall? Yes, it does. Did the nexus was 1 hit away from destruction? Yes, it was. Is it 100% safe to say the homeguard bug did not affect the outcome at all? No, it's not, it's highly questionable - we can argue about it, but no one can be 100% sure. I'm not mad about one of these teams winning or losing because of that either, they did not play well - wel, most of them -, but it can not justify denying the opportunity for a rematch after an obvious bug. Or adress it at least! Say something stupid that taking damage at the end is just an illusion, we are all drunk, case closed. Instead Nick Allen says it was the maw shield, which has been proven to be wrong.
literally complaining about a fly flying into your eye, as to why someone loses a tennis match.
|
damn wtf c9 is bff with lmq
|
On September 28 2014 15:02 wei2coolman wrote:Show nested quote +On September 28 2014 14:36 Volband wrote:On September 28 2014 14:29 wei2coolman wrote:On September 28 2014 14:25 Volband wrote:On September 28 2014 13:04 chalice wrote:On September 28 2014 12:01 dDazed wrote:
Out of curiosity what are the Chinese fans saying about the Homeguard bug? Anyone know? my guess is that most aren't even aware of it because it is such a non-issue. Sure, when the bug is in your favor, it's easily dismissed as a non-issue. :D I wonder if people who have a hard time accepting or comprehending the term "taking damage" are Fnatic haters, or those football (soccer) lovers who thinks it's completely fine if referee's blindness sends home teams from international events, because "it's part of the game". And as I said, if the same scenario would've happened between contenders to the first place, Riot would have to remake. Anyway, the most annoying thing for me is simply that Nick Allen can'release a statement that actually talks about the bug, and not bs like maw shield, which only shows he has no idea - or wants to have none - what was the problem in the first place. it's a non issue because it's literally 1 variable than fnatic had no control of, meanwhile they managed to fuck up that backdoor with 30 other fucking mistakes. See, the way you see it is why you think it's a non-issue. You think because they screwed up a bug or two should not matter. It's no how it works. If you miss an easy goal, than it gives the referee the option to not give a red card to someone who kicks the shit out of you, because "well he played shit anyway", lol. Does homeguard says it won't activate for 6 seconds if the user takes damage? Yes, it is written, it is clear as day. Does homeguard activate if you take damage at the end of recall? Yes, it does. Did the nexus was 1 hit away from destruction? Yes, it was. Is it 100% safe to say the homeguard bug did not affect the outcome at all? No, it's not, it's highly questionable - we can argue about it, but no one can be 100% sure. I'm not mad about one of these teams winning or losing because of that either, they did not play well - wel, most of them -, but it can not justify denying the opportunity for a rematch after an obvious bug. Or adress it at least! Say something stupid that taking damage at the end is just an illusion, we are all drunk, case closed. Instead Nick Allen says it was the maw shield, which has been proven to be wrong. literally complaining about a fly flying into your eye, as to why someone loses a tennis match.
literally complaining about a fly flying into your eye, as to why someone loses a tennis match, when it's written black and white that flies are not allowed to fly into your eye.
There is an enormous difference.
|
I'm pretty sure that Shield didnt really take that game seriously vs. Alliance, you can tell by the rammus ban and shit. It's too bad for C9 because Shield will be playing at 100% for sure.
|
Bearded Elder29904 Posts
Well yeah, I have to agree that Shook played a fucking impressive game vs NWS.
|
On September 28 2014 15:08 IMoperator wrote:
I'm pretty sure that Shield didnt really take that game seriously vs. Alliance, you can tell by the rammus ban and shit. It's too bad for C9 because Shield will be playing at 100% for sure.
They definitely had a really questionable pick/ban. I think Wickd's irelia is a must ban, since he's an absolute monster on it, and also because he's been unimpressive on other champions.
|
On September 28 2014 15:01 ketchup wrote:Show nested quote +On September 28 2014 14:57 739 wrote:
Seems like C9 is pretty much fucked up. Last 3 games are Alliance/C9 vs Kabum - both wins should go to LCS teams and last one is C9 vs NWS, gg C9? I don't think they can repeat what Alliance did to Koreans. Honestly, no team can really repeat what happened in that game. I don't think I'll see a Korean team repeat something like that either. I've never seen a game go that well for any team ever. Everything worked for Alliance, and they kept calm/controlled throughout the game. The fact that they seemed to have been aiming for that goal is amazing. Show nested quote +On September 28 2014 15:01 Shiznick wrote:
I think it's a difficult call whether to say it should be replayed or not. Nothing inconsistent with the usual game mechanics happened, iirc, it's been reproduced that you always get homeguard when you recall after taking damage in the last half second.
When it comes to things like this, there will be certain ambiguities to how the engine mechanics work. To call for a rematch because an engine mechanic works differently to how spectators thought it would is a bit silly. Let's be honest, it's not as if Rekkles hit Loveling before his recall and thought "good, now he won't have homeguards" or something. I really like this post. Too bad people will ignore your points.
I don't want a rematch, though I'd appreciate if Riot would offer it to Fnatic and they would decline it. I'd be really disappointed if they accepted it.
But hiding in the closet? As Riot Gaming? During WC? Hire me please, I can be a coward spouting nonsense 0-24 and ending my sentences with either "you are fined for [...]" or "case closed". The only thing Riot adressed is the maw-damage-homeguard interaction which is besides the point.
It's funny how Nick Allen shot himself on the foot. He said case closed because maw shield should work this way, but after it was proven it was not the maw shield he had to release another statement and continue the investigation. Howewer if he said so, he'd look even weaker, and I doubt Riot want to feed the community with more "Nick Allen best of" stuff to laugh at.
Though I have hope in Riot that they will once and for all clear up these interactions, and correct the tooltips accordingly, because it's 2014, it's a video game and we are talking about unwritten laws, like it's soccer with 100+ years of tradition and rubber rules.
|
Bearded Elder29904 Posts
What exactly are we talking about? What kind of bug in Fnatics game?
|
today everyone controls their destiny in group C, time to show whatever you've been hiding.
|
On September 28 2014 15:16 739 wrote:
What exactly are we talking about? What kind of bug in Fnatics game?
Khaziks is a bug champion, and prevented Soaz from killing nexus.
that's the bug.
|
Funnily enough, Kabum's bans have been pretty good for the entire tourney. They do their research at least. Just need to catch up on other things.
|
On September 28 2014 15:11 Shiznick wrote:Show nested quote +On September 28 2014 15:08 IMoperator wrote:
I'm pretty sure that Shield didnt really take that game seriously vs. Alliance, you can tell by the rammus ban and shit. It's too bad for C9 because Shield will be playing at 100% for sure. They definitely had a really questionable pick/ban. I think Wickd's irelia is a must ban, since he's an absolute monster on it, and also because he's been unimpressive on other champions.
Also, if you are going to pick ryze. Irelia basically has to derp really hard to not get the kill in a gank on ryze and the mu cab snowball in her direction very quickly.
C9 vs All was the perfect example of that. Meteos was out of position for like 20 seconds and the lane was over.
|
On September 28 2014 15:16 739 wrote:
What exactly are we talking about? What kind of bug in Fnatics game?
Homeguard is bugged. If you take damage at the end of recall you teleport home and the game thinks you did not take any damage thus the homeguard activates. Kha6 got a huge hp/mana boost and an initial speed boost and it affected the outcome of the game, knowing the nexus was 1 hit away from blowing up.
Though "taking damage" is still hard to understand for some people, even though it requires very little reading comprehension abilities.
|
On September 28 2014 15:08 IMoperator wrote:
I'm pretty sure that Shield didnt really take that game seriously vs. Alliance, you can tell by the rammus ban and shit. It's too bad for C9 because Shield will be playing at 100% for sure.
wut, rammus is a common pick/ban in korean soloQ and shook has pretty much only rammus games on his kr account (30 games with 77% winrate), he just beat c9 with it and nws planned to fp ryze who gets crushed by jungle camp( thats why balls was so behind he could never leave his turret)
im sure rammus ban was 100% serious
|
|
|
|
|
|
EPT
