The Overtime Mystery

Surely a two time Overwatch League champion knows how overtime works
Socials:
/ supertf
/ ​
discord.gg/supertf
/ super_ow
Editor: stefayylmao
/ stefayylmao1
Intro & Outro songs are from the Catherine OST:
Thus Spoke Brooks & Lost

[@maxn8102]

Reminds me of the "impossible sigma jump" where he just gets involved with some dumb mythbusters type shenanigans. They're always fun vids

[@ayce7286]

yeah i love these types of vidoes

[@masonhughes_big]

I read this comment then scrolled down to see the first reccommended video being the impossible sigma jump

[@loganmacneil8835]

@@masonhughes_big same lmao

[@Noobish_Camper55]

Watching super spaz out for over an hour proving himself wrong over and over then at the end proving he was sorta right was great

[@amirriddle]

but not really for the context of the match he was talking about

[@endk.3500]

I think it’s funny that he just decided that the game was wrong in that instance

[@shardgunner4815]

Hi, so I’m no expert, but I don’t see how he’s right. Like, if he had said “you can be at 98%, so long as the other team is at 98% and has triggered ot, and then ot won’t trigger again and the game just ends”, but given the context of the game he played, and his testing, what he said just seems wrong. And I’m saying this as someone who had no fucking idea how ot was triggered. But after the testing, and explanation of the 3 second = 96.5% thing, it just all seemed to prove him wrong. No hate or arguing please, just understanding lol

[@apocalypseap]

@@endk.3500 He's human just like anyone else and we all have biases. The situation he was in was different from the one at the end. If OT isn't triggered first, then if you cap back with a percentage starting between 96.5% and 99%, OT is triggered, I guess?

[@endk.3500]

@@apocalypseap if you had it at 96.5 or higher percentage and the other team takes it, when you get it back and get to 99 it automatically triggers OT

[@13days13]

i love how super is one of the most widely known and recognizable content creators/streamers in comp ow but whenever he tries talking to his team nobody responds like he doesnt exist

[@apocalypseap]

And people in custom games are like "are you the real super"

[@ethernet6591]

@@apocalypseap it’s even better like in that one clip where the guy says that he isn’t

[@imprincesswolfy2565]

@@apocalypseap I used to play a lot of Widow HS custom games, and some times streamers/owl players would join, and back then being a plat scrub you can’t believe that “the real X” joined, (especially when once Muma joined and everyone in the lobby would destroy him time and time again). But you can always check their profile to see if they’re “the real X”

[@imprincesswolfy2565]

@@ethernet6591 yeah, like just check his profile 4head

[@ethernet6591]

@@imprincesswolfy2565 fr man has a public profile and it's pretty obvious from it that it would be him

[@senorgerman]

The second it happened, I knew this was gonna be it’s own video lol

[@LeLabersack]

Hallo

[@jhowgx]

Hes farming that 100 subs back

[@sparkz4224]

I don’t think super realizes that one percent is one second

[@lucakoherr6003]

I guess Bap died on point, so its that bug where you got beat in spawn, because you spawn and then get teleported. He spawned on point, contested for a millisecond and then went to spawn

[@kevinraymond8439]

it looked like that in the video, but bap doesnt even tp back to point, just where he died

[@lucakoherr6003]

@@kevinraymond8439 i thought he died on point, but I dont remember rn

[@loganmorris2793]

in the replay you see his name flash on screen for a couple frames. its either this or because blizzard codeed the game for two attackers

[@Pickled_Poet]

you have to be on point for 0.5 seconds in order to contest, therefore the death spawning bug doesn't trigger contest. If it did it would probably be more noticeable

[@kuzan421]

pretty sure its just the 96.5% thing chat was talking about. happens to me all the time at 97% and if its passed 96.5% it probably rounds up to 97%. its been like this forever and i hate it

[@Not_Ezro]

Super forced Stef to put out this video fast to make up the $500 he lost this stream

[@PanTF]

I've personally seen a capture at 98% go to 100% without overtime triggering, and also I love these kinds of videos.

[@Pom05124]

Same

[@zestmasterLemon]

Same but idk if it was after recap or not

[@noa7422]

Same, but I think it was 2cp not control though…

[@Unknown-el1jy]

I remember having a ranked game where the score was 3-3 on kings row. The game only allowed us to play 1 tie breaker as attack tho and we lost the attack but we lost the whole game instead of a draw. Can someone explain?

[@xiBlacKouTzx360]

@@Unknown-el1jy the game has bugs . I’ve seen the cart on payload go past the point the other team got it to and still trigger a loss

[@OmicronGaming]

If you think about it, if the 3 second rule was in place, it would actually be BETTER to be at 98 than 99. Here’s why: If you had the point at 99% and capture it back, it ALWAYS triggers OT. Everyone knows this. Standard OT lasts 5 seconds, which is how much time the team has to contest. However, if you capped it back at, say, 98.9%, and OT DIDN’T trigger, then that would be the 3 second rule + ~1.2 seconds of capturing progress, giving a grand total of 3 + 1.2 = 4.2 seconds, which means that having the point at a LOWER percentage is actually an advantage. I know that there’s still gonna be a lot of people arguing in this comment thread, regardless of whoever explains it, so we should all just wait for someone to make a video on how this mechanic works and how it should be fixed.

[@TMC_TimeLine]

5Head

[@stefayylmao]

Chatting

[@georgeruss6416]

Smart

[@dudedude6892]

5Head

[@kibasu]

im dumb

[@Complexxity_]

I've lost a game to the enemy team having 98% then re-capping after killing our team, we didn't get OT. My friends have lost games for the same reason too. He's not crazy, Overwatch is inconsistent BS.

[@noahboddie3482]

The situation that it happens bizarrely enough is if the thing ended on overtime. Its consistently inconsistent at least. pepeW

[@apocalypseap]

If OT is triggered before you capture, then OT doesn't start up again. That's probably what happened.

[@wallr54]

I agree OW is so fucked in terms of just consistency

[@chelronin7843]

I’ve had this happen countless times, both to myself and the enemy team. I think Super is right, it doesn’t make sense why it would work in the way chat was saying.

[@dankuzcodbdbd6092]

the overtime incident... despair smoketime

[@Patrock404]

Can't believe I just watched super test a game mechanic for 18 minutes

[@djoaieuh3286]

Ok so here's how I think it works : In the game's code, instead of having percentages, it uses a timer just like in 2CP. In 2CP if you touch the point when the timer is at or below 3 seconds you get overtime. However in KOTH you use 2 TIMERS, one for Blue Team, one for Red Team : When Blue Team has the point, its timer decreases and vice-versa for Red. First team to deplete its timer wins (btw going from 0 to 100% takes exactly 120 seconds so it wouldn't be impractical to use timers). Let's imagine Blue Team gets to 97%, that would mean they have approximately 2.5 seconds on the clock left. Red Team caps point, so the game registers that at 2.5 seconds on Blue's clock, someone touched point. Then Blue's timer freezes and Red's timer starts going down. If Blue cap back, the timer goes down to 0 seconds and then the game is like ''Oh but wait, at 2.5 seconds someone touched point, okk I need to trigger overtime'' And that's what happened, you don't need to touch point 3 ingame seconds before it reaches 99%, you need to touch when the TIMER is below 3 seconds, which could have happened 3 ingame minutes ago. In 2CP this isn't a problem because the timer never stops and represents actual ingame time. I can't know for sure if that's actually how the game is coded but it seems to be the only explanation. Additionally the game would work like this if Blizzard just took 2CP's timer and overtime mechanics and just pasted it on to KOTH (which is the smartest thing to do). Anyway thanks for coming to my TED Talk and I hope I was clear enough in my explanations.

[@dinyoungseon3627]

Yea I kinda feels like the priority of overtime logic is 'if the non-cap reach 97 or higher' -> 'If the non-cap team touches the point 3 secs ago' -> 'If the non-cap team touches the point before it reaches 97' , blizzard probably did this overwhelming logic to avoid latency issues since timer should proceeds on server's side - therefore local touching point event might happened slightly later than the 97% when it ticks on super's screen.

[@hybridsaul9614]

Yeah ur grand master

[@eyeles8887]

holy shit this for realsies makes so much sense, i think you actually just solved it lol

[@willowpets]

This doesn’t explain the end of the video, though. Super does the same scenario, except he just waits till his bar is 99 before handing over the point. Theoretically, the red timer should still “know” that he touched the point at ~98% and trigger overtime if that’s how it actually works, but it doesn’t trigger.

[@djoaieuh3286]

@@willowpets I honestly don't know for sure why that happens but I do have a guess (Again, no actual proof that this is how the game works, just the best answer I can offer). In all other scenarios overtime triggered but in the last one, it didn't. The only difference with all the others tests is that overtime triggered for Blue Team then Red capped back so I guess the problem should be there. My guess is that since Red capped in Overtime the game doesn't apply the usual ''3 second'' rule but instead just says ''If someone is on point when the timer reaches 0 trigger Overtime, if not then just win''. This mechanic would actually make sense to prevent infinite overtime scenarios. If OT were to trigger then Blue has a chance to cap back, then when they do Blue's timer goes in overtime, which gives time for Red to cap back etc... This mechanic makes it so that if both teams are about to win, it hard punishes the team that gets off point for too long. I actually don't think that's exactly it though, at least, I'm just missing something, at worst, I'm completely wrong lmao.

[@sammi-qg9nj]

The real mystery is how this situation NEVER happened in a single shock scrim...

[@Luca-mf8ot]

because a team always has a touch until 99% even if it means throwing the life for OT triggering

[@horsemindinghisowndamnbusi7719]

the edit at 11:16 was actually gorgeous, amazing job stef

[@angrychickengod3831]

super's career hit a low point when he needed to watch a KarQ video for OW advice

[@emilycrackerjack8599]

watching this live was both infuriating and so entertaining, happy it was made into its own video

[@rvrsl]

Probably one of the greatest steams I've ever been a part of, I was howling. You have to give it to Matthew, he's the OWL golden child and plays this game as a career being one of the most top tier players to ever play OW. The fact he could post this with humility is respectable.

[@imragehackingforefficiency]

Theres a video by Marblr released on May 19, 2022 explaining that OT happens earlier than you think, titled "Overtime Happens Sooner on Control Than Other Modes".

[@ObamaCum]

watching this live was like a fever dream

[@notareetbot6264]

It seems likely to me that within this game's spaghetti code, the capture percentage is treated as a clock that lasts for 99*1.2 seconds and gets paused when the other team has capped the point. Therefore, if OT is programmed to happen when the other team touches the point when there are 3 or fewer seconds left on the clock, when you flip the point past ~96.5%, you touched the point with

[@localmilfchaser6938]

programmer andy

[@awesomedrazons7502]

I’m with super on this one. I have like an engraved comp game memory when it was at 98% for the enemy team and they capped and no overtime occurred

[@apocalypseap]

If you trigger OT first when they have the point, then the cap switches, no OT occurs. That's probably what you saw.

[@julius-music]

He’s actually correct though. The only thing he’s missing is that the 3 second timer stops when he caps the point. For example: red team has 98% -> is approx 2.5s away from winning -> blue team caps -> red team timer is stopped at 2.5s. When red team caps back, the timer 'remembers' that blue team touched 2.5s ago -> OT is triggered. That’s totally independent from the real in game time. That last example is somewhat special bc (I guess) the game overrides both timers as soon as one OT has been triggered. If it didn’t do that, it would have to swap between OT indefinitely.

[@randy_handy]

0:05 Tell me something I don’t know super

[@StarKnight54]

super: I'm gonna be a little creative here Also super: does basic silver strat

[@lover3213]

Call KarQ! He should know, although his video doesn’t talk about this specific situation. Also; when a player respawns, their “body” first respawns and then immediately gets teleported to spawn. This means there is a split second where the body “exists” where it died. KarQ once accidentally nano:ed a body like this, and made this interaction more known. I think in the real comp game, the Bap who died respawned on point and “touched” it before getting teleported back to spawn. That’s what triggered Overtime! Hopefully this PHENOMENON gets more known in the future. Love everything that you do, it’s really true what Cavalry said, you kinda saved OW❤️

[@organa1626]

Super actually had this mechanic trigger in one of his previous videos where he respawned as Rein on Rialto and got shields from a Lucio Beat that had been used across the map.

[@lover3213]

Oh yeah that’s true

[@pcbangbros8350]

Yep, hence why people say "die on point"

[@drenorthegrand]

I actually slowed down the footage and it seems that the lucio is the person who triggered it, his outline shows up just before he goes to spawn and right before OT

[@lover3213]

Interesting… 🧐

[@PettyBees]

Watching this live had to be one of the funniest experiences ever.

[@fatalshards]

9:34 Percentage increase on a KOTH map is one second. For example, the increase from 71 to 72 and so on takes one second. With this in mind, if a team recaptures the point and they have 97-99% of the objective completed, OT will still trigger, because 97-99 is within the three seconds of the given time frame needed to trigger OT. With the exception of 96.5%, if a team recaptures a point at 97%, OT will still trigger because it is within the final three seconds of the necessary objective capture. The game recognizes that someone has at one point during the game, touched the point at 97%, causing OT to activate, since 97% is within the last three seconds of point capture.

[@michaeltaylor7160]

It's so weird bc I know for a fact that he's right after literally nearly 6-9k hours on the game but idk what the heck is going on

[@itsyuboi3218]

I’ve only got like 600 but I agree with super as well

[@QwaC]

2:41 the speed he did that with had me rolling 😂

[@olivar._.6760]

thanks for making my day better :) This video really came in clutch

[@danielsvacek8300]

I think Super is right. I had many games, when we had like 98% and when we captured it back it was instantly end, no OT.

[@Linus644]

I second this

[@TheHopelesssDwarf]

It’s because it’s based on time, as soon as you capture the point the “ 3 second timer” that decides whether or not overtime triggers will kick in. Because the game thinks their was an opposing team member on the objective right up till the point the objective is turned over to the opposite team it won’t start the 3 secs until that switch over, thus creating the triggered OT due to the game thinking the enemy was touching it . Because 96.5% is exactly 3 seconds away from the 100% capture it will always trigger OT. This will not result in OT only if OT was already in progress as the game would continue to keep triggering a new 5 seconds of OT making the capture even more difficult.

[@fps_DReX]

Exactly right!

[@jimmyjohn9223]

this was the funniest thing to watch i loved watching him slowly go more and more insane and making him angrier by chatting

[@alefal8101]

This one's gonna be in a future ow iceberg for sure

[@chandler5014]

He’s reliving the trauma all over again

[@yyny0]

That old ass clip is why they changed it. If you capped at 97% or further, they will always give you overtime to give you a fair chance to contest.

[@lot8113]

They get ot if they touch after 96/97%. Since the point was theirs when you capped at 96% they got ot. I'd usually say it happens only for 97%+, but apparently it was late 96%, so it still counted. The 3 second rule counts even when you cap back when the point is 3 seconds before or closer from being secured, because the opponent did touch it 3 seconds of less before (since it was theirs). It is weird that it triggered on 96%, but I guess it was late 96% so because of how the game counts time it worked. 11:55 "But I didn't touch it" Yes you did, as the point was yours. KarQ says that 1%=1.2, and he also says that it'll trigger ot as long as you touch after 96.5%. All of this makes sense. The confusion was caused by the fact that you didn't realise that team A capturing the point counts as contesting, so when team B capps it back ot triggers if team A had captured when team B progress was 96.5% or more. Repeating myslef here, just making sure it's clear. I haven't played the game nearly as much as super, and I trust his judgement, so a plausible theory may be that this particular mechanic (triggering ot or not if the point is capped back when it's a 96,5%) might have been changed. I don't believe this is the case, as it probably would have been in the patch notes and would have been covered by creators, but it is a possibility.

[@shiverian5970]

The simpler explanation is that it just assumes if the other team is gaining percentage it means someone is on point. So it assumes someone was on in the last 3 secs. This seems like some wraparound logic that has no reason to be in the game. It's be really easy to just keep track of both teams ot. Edit: could also just be that the game has a "contested" state for the point and that's what it uses to track if someone was on point. One of the things that sets that state is capping. Since you were on the point and capping it the game thinks it was contested, so someone was on point in the last 3 secs, ot triggers.

[@lot8113]

@@shiverian5970 seems reasonable. Still can't wrap my head around ot not triggering if the other team has 99%

[@shiverian5970]

@@lot8113 On pc now so I can write some pseudo code while percentOne < 100: if opposingPlayer in peopleOnPoint: secsSinceLastContest = 0 if percentOne == 99 and secsSinceLastContest

[@lot8113]

@@shiverian5970 the 98/99 thing comes down to the discrepancy between seconds and percents. As for the rest, your code is exactly how I would write it, except that programming in a game like overwatch is far more complicated. The amount of things to keep track of forces Devs to optimise the code to a much greater degree, to the point where most amateur coders would struggle to understand it all. I think your argument makes sense, but I also struggle to think that ow Devs would write code similar to this to manage the ot trigger in game. Their code probably looks much different, and that leads me to avoid conclusions (on why the game behaves the way it does) based on my own programming skills and knowledge (or - likewise - based on the ones of someone I can understand the code of). I don't know how good you are at programming, but unless you are a dev working for big company or making big games I think my point stands. Rather, I would approach the issue basing myself on game logic. I can't come up with a coherent explanation now, but I think that either you're right conceptually - as in, it has something to do with the way the game processes the ot trigger on both teams, but on a more macro level I'd imagine - or, more likely in my opinion, it is a somewhat intentional mechanic, surfaced during development and then left in, or added intentionally for reasons beyond me. Again, I do not know what your level of programming skills is, but mine is certainly not sufficient to come up with a sound explanation of such a phenomenon. I cannot even begin to wrap my head around my own wilder interpretations of the whole thing, so I suppose I'll live with the doubt. I really hope this video from super sparks further investigation from KarQ or other creators, as now, with this eternal doubt, I will struggle to sleep, for my mind will endlessly wonder in a riot of variables, constants, ifs, whiles, zeroes and ones. Sorry bro, really got into the writing there somewhere, I hope you don't mind.

[@shiverian5970]

@@lot8113 Oh yeah my programming skills are not even close to the realm of making games. I learned some python and im happy with it for the small things I do. I also don't know why the devs would have something like this in game but I assume it stems from them not differentiating between different teams enough. Why that happened i dont know. Thanks for taking the time to have this conversation lol, usually this doesnt happen on the internet

[@Pijonty]

7:29 The dono in the background while he rages is funny asf A nuisance while he is already mad

[@Hecubusx]

thanks for taking us all down your rabbit hole of madness

[@johnnielao2080]

The OT system works on payload if you touch it at 3 seconds or under. On control point however, OT only happens if you touch the point at 97%.

[@Riley_M]

This has actually happened to me a lot and was thinking I was just unknown of some certain conditions to get overtime

[@rissa8373]

this was so fun to watch in real time…. congrats on -100 :P

[@alexstafford5486]

I love the editing in this lmao

[@cellogramfr]

I think that it happens because there was an overtime less than 3 secs ago and it was not 99% so it caps instantly and skips the overtime but if u have 96.5% or more and no overtime in the last 3 secs, there will BE an overtime

[@calilycan3213]

I love how at the end of every loss theres always someone making excuses

[@alexgordon7312]

The point has two states of being capped and it treats those as two objectives, so if you were there for the last 3 seconds of the enemy having point (state 1) and then change it to yours (state 2), it saves the conditions in state 1 while state 2 is active and then when it goes back to state 1, since you were there in the last 3 seconds of that state, that's why OT triggers

[@westwoodwaters]

this is basically variety at this point. super and stefay combo unrivaled on youtube

[@Cergun_]

I’m in love with videos where super questions his sanity

[@gombeen]

Hey stefayy, im pretty down bad with Covid rn, and while I couldnt enjoy Christmas with my family, I just wanna say that these daily uploads and edits always cheer me up. Thank you bro, much love.

[@ichigoamv1473]

The reason this happens is cause there’s no double overtime in ow the first ot trigger prevents the 2nd from having its trigger unless it has the hard stop of a player being on point

[@magicmarker7658]

@supertf It was because your teams percent was at 96 when it flipped, so 3 seconds till overtime. The game must have thought that they were on point until it flipped.

[@depan55]

Nah, it's because the team with 96 is the attacking / non-controlling team. It seems the "bug" occurs when ot is already activated and then a team caps back with 96.6 - 99.9% which probably happens a lot in comp and owl games and that is almost more likely than capping back prior to ot

[@apocalypseap]

@@depan55 It's not a bug. It works as intended.

[@SilentHalt]

I love the subnautica music with the torb hammer, best part in my opinion.

[@NapstaMeme]

the drama, heartbreak, and death. such a great movie

[@dyl1068]

best youtube video of 2022 so far

[@ex2895]

You know super has grown when his intro clips aren't malds, just acceptance

[@GamerBlakeTV]

I love how super had to learn about overtime through KarQ like many of us did

[@mrneonm]

and then he didn't even listen to him

[@hydro_fallenstar3281]

love your content man

[@Necroneer]

5:38 LMFAO Oh man this video was great.

[@maxmccabe6484]

love the editing

[@philipadams9611]

Happy new year Mr. tf and Stef

[@nightfire_CSGO]

Dear lord this was too funny. For probably 10 mins I was wondering when this will switch to the usual gameplay and it never did. Its just 15 minutes of Super having a breakdown. Amazing.

[@EdinV]

from what I see it looks like it only goes to ot if you dont die before he starts capping, if you’re near it while he caps it goes to ot

[@Lily-zk1ic]

Super your vids make me acc happy

[@flashback4019]

Stef really just got a 20 min video out of this. What a chad

[@hardkoa1571]

love these videos

[@trevormay226]

12:50 karq answers supers question and he doesnt notice

[@IcelitRaven]

Karq was agreeing with Super. They were both talking about the window of time when someone needs to touch point to trigger overtime, but in Super's game, nobody from the enemy team touched point. That's why Super was confused. So the scenario that Karq and Super were talking about was: -Team A has point -Team B touches 3 seconds before Team A hits 99% (In Karq's words, Team A is at >96.5%) -Overtime is triggered. But the scenario in Super's game was: -Team A gets point to 96% -Team B captures point, gets it to 60% -Team A captures point back -The important part: Nobody from Team B touches point! Based on the 3 second rule that Karq and Super discussed, someone from Team B should have had to touch at this moment. -Overtime is triggered anyways tl;dr Both Super and Karq were talking about the window when someone from the opposing team needs to touch, which is 3 seconds before 99% is reached (about 96.5%). But the confusion was that nobody on the opposing team touched within that window in Super's game.

[@douchenozzlemcgee6111]

Nono. Look at 2:00 at .25 speed. The right side of point, Cheerios(their bap) get's respawned for one frame before he's transported across the map back in spawn. Must have been transported across the point as well, triggering OT.

[@ohnz6]

1:47 THE FIRESTRIKE COUNTS

[@evilMissRune]

love the torb remix of abandon ship

[@8bitDreamworld]

First super vid of 2022!!! Happy new year guys

[@sallyg7629]

that was a rollercoaster of emotion

[@Superman2890]

Steffay really making bangers

[@spinosaurus2001]

super really is the jerma of overwatch

[@giorgos-4515]

"my opinion is that i know i am not crazy" is what a crazy person would say

[@eykan_ow]

I was with Super on this one, and I'm baffled now.

[@douchenozzlemcgee6111]

Nono. Look at 2:00 at .25 speed. The right side of point, Cheerios(their bap) get's respawned for one frame before he's transported across the map back in spawn. Must have been transported across the point as well, triggering OT.

[@DerpyScrub]

the reason he didn’t get overtime at the end is because it was already triggered on his team capture. If no overtime has been activated, it will almost always become overtime after capturing at 96-97%. Some examples are, if the score is 50% against 96% and you have just recaptured 96%, that will become overtime no matter what. If it is 99% against 99%, overtime will ONLY be triggered again if you touch within 3 seconds.

[@TheStrGuitar]

I think you're right

[@apocalypseap]

Yeah there won't be two OTs in a row. The game doesn't allow this.

[@jakemoore5064]

18 minute super video?? Let's goooo

[@grr2960]

" im good " " im not good " ik he was giggling after, i would be giggling and snorting

[@thecarptain]

I love how he got pissed at the guy for killing him and capping too fast, and then explained that they had to wait 3 seconds when Super had 8% on the board

[@mscup8814]

Super loses his mind over a control point for the rest of the stream

[@tmujir955]

One of the best examples of confirmation bias ever

[@shadow4380]

Lmao KarQ said it, according to his math if you touch the point at ~96,5% it triggers overtime

[@bodacious12]

Flipping point in a 3 second window from reaching 99% triggers overtime

[@Anima_Kesil]

This was phenomal content

[@cassidydickerson4166]

The key change between the two, is overtime has already been triggered when the tracer caps after killing you as torb

[@Ysldolll]

The million robot “L’s” never fail💀💀

[@iiballisticpanda]

yea it’s like the lucio beat thing where their player instance spawned on they dead body anyways

[@MasterNick7412]

That Simpsons edit was the best editor added reference in a video I've ever seen hahaha 🤣🤣🤣

[@peternaur3456]

I think why it worked with overtime when it was 99 to 98 was since there already had been overtime, it did not trigger again, I am pretty certain this happen as well when your at 99 to 99 only 1 overtime triggers, but if they have 99 and you have 20 and they cap and no one on your team is able to touch it will still automatically trigger overtime even tho no one is on point

[@jackaboyawesome6624]

OMEGALUL Never ever doubt chat again!

[@clay1876]

Stefay really just made an entire almost 20 minute video over Overtime in Overwatch.

[@SadSongRy]

this entire video was just super being batshit insane.

[@dillonu.4975]

This game is an enigma

[@presa.]

2:02 there's a frame where junkrat is respawned but briefly near obj, could be the reason

[@RenounceDarkness_]

Props to the guy gifted 50 subs Super isn’t crazy the game is

[@Im.Jupiiter]

“Tracers ass kinda looks like orisas bongo”- super 2022

[@crypticrs]

the 'I thought this was your job' dono lul

[@supremefatness4085]

I was exhausted after watching this video

[@MADDOG-sq9oj]

The overtime incident... 2022, supertf

[@NotKewl]

"I know I'm not crazy" - Every crazy person ever

[@mysiv3504]

This must be my favorite video lol