bug? | VLR.gg

#1

mangotan

first: before i say anything else, i missed maps 2 and 3. i was just watching back the vod, so im not sure what the discussion was when the round took place, potentially the answer is alr there
second: idk how much this would've actually impacted the game, i mean 100t still choked a massive lead to g2, but:

the timing of the round was pivotal for momentum - 100T win that round, it goes to 12 and match point, G2 build lots of confidence from a round like that since it was a full buy round

so why wasnt that round replayed? surely there's a reason, pls someone share thoughts. and no, you can't use the excuse of "damage already dealt", because if we look at precedent established by FPX/XSET, that was a round where damage was alr dealt and yet we still replayed because it had major implications. this eeiu mf literally thought he could shoot a gun and then couldnt, and was in a prime position to lock the round if he killed leaf. why was this round not replayed?

#2

HershieBoi

0

Frags

+

–

The rules say they would replay the round only if the bug is either game breaking or if there was damage done in that round. The bug was definitely not game breaking and it happened way into a round where damage was taken. So they should not replay the round.

#4

mangotan

1

Frags

+

–

i appreciate the clarification, but if i could ask: dyk where riot defines "game-breaking" bugs? because if you look at the exact timing of when this round happened, it literally could have changed the tides of the game. in no way was valyn expecting eeiu there, which would've brought it to a 4v3 scenario, valyn no astra wall now... and it's 11-8 so it's a big momentum changer

like i understand watching back the vod how 100T tossed a major lead, but surely this would quantify as "game-breaking", no?

#3

catNmouse

0

Frags

+

–

feel like eeiu should’ve called a pause there

#5

gluesniffer

0

Frags

+

–

hello mangotan :( im sorry for our loss

here: https://cdn.sanity.io/files/dsfx7636/news/b2626c898b248fe08f7cf5425d5b54e3deb1db31.pdf

According to this rulebook, there are classifications as to bugs, but only two are relevant here:
1) Game-breaking (in the seemingly inaccessible to public Esports Bug List)
2) Non game-breaking, but still game altering

Riot officials can replay round without a Challenge from the HC if 1) no damage has been done and it's a non game-breaking but still game altering bug, OR 2) it's a game-breaking bug, damage CAN HAVE BEEN DONE

IF damage has been done and it's a non-game breaking but still altering bug:
HC would have to request a Challenge "within the first twenty (20) seconds of a Buy Phase of the round immediately subsequent to the impacted round... in order to use a Challenge, the Team must have at least one (1) remaining Timeout for the map. If the Team does not have any remaining Timeouts, the Team may not request a Challenge" (Section 9)

I'll make a separate thread since my first one is kinda unclear (since I didn't fully do the research)

In the case of FPX/XSET, we don't know if it was a game breaking bug or not, but because it was the last round, Riot MAY HAVE made an exemption to not taking initiative IF IT WAS NOT a game breaking bug

Unclear what official procedure for the Vyse indicator bug is, though, because we don't have access (or, at least, I'm unaware of where it is) to the Esports Bug List

#6

mangotan

1

Frags

+

–

yeah, it's rough all good

but i was looking at the twitter posts following this and according to replies to Mikes' tweet a couple of pros have spotted this already... seems like it could be on the bug list? either way, i think it's rough to categorize this as a "non-game-breaking bug" when it literally would've prevented the acquisition of an ult that was important in deciding the outcome of that round and a kill that would've equalize the round.