I mean that's always been the case. G2 is extremely volatile and not at all consistent in their performance.

But god damn those 3-0s were fun to see.

 

@Fluffiness and I found a wild @Fenraellis in a game today I think:
https://www.leagueofgraphs.com/match/na/4304833115#participant4

 

It would be nice if the implementation of Challenges didn't completely screw ping consistency (**)... I could handle a consistent 130 to 170. It would suck, but I played at 130 ping for the first few years I played League. This, though... sometimes it's 30, sometimes 130, and sometimes 300+ (even though the display never went about 190, I had several times where inputs were lagged by 3+ seconds).
Ah well. Well done, nonetheless.

(**) At a guess, the servers are constantly checking for status updates on Challenges, and that's killing the packet reception.

 

We were having similar issues although it mostly went away after laning phase. I think the displayed ping and actual ping was very different.

Played a game right after and it was extremely unplayable so we called it there. Was a fun one though.

 

We made the mistake of trying two more matches. I think we won one, and then lost the other horribly... Or maybe we just lost both horribly. I just remember it being singularly unpleasant. The players on my team that were in Texas were apparently unaffected.

 

It was east coast specific until around 12 est and then it became countrywide. Riot really will break their game one day.

 

Jankos showing off that plum buff. Caps doing Claps things.

I don't care what happens from now on. At least we got a win in. And holy hell what a game it was. So many close fights, so many tense moments.