RECORD OR STREAM CONTINUUM! A How-to Guide

[Dwopple]

Week 8 matches

TWLJ
Cuphead vs Silence (was in a discord so there's people talking during the first half, RIP)

TWLB
Cuphead vs Accuracy
Silence vs Pandora

TWLD
Cuphead vs Silence
Cuphead vs Strike
Cuphead vs Pandora

[ogron]

great work porkjet and dwopple, thanks!

[ogron]

Just want to highlight this great play by ogron to dodge mikkiz's burst(s) while laughing at dreamwins lack of energy or aim.

[Dreamwin]

lool, i remember this. Was at 50 but missed a couple there. Sick 34 second jupe in the end too. Wonder how long it would have been if we didn't manually !jupe it? Good reminder that these things still happen and you need to be watching the clock from time to time. Glad it happened in that game instead of playoff game. Gl in playoffs everyone!

[Dwopple]

Late to post this, but here are the Quarter final recordings.

TWLJ
Pandora vs Lululemon

TWLB
Pandora vs Accuracy

TWLD
Silence vs Divine round 3 - forgot to press record for rounds 1-2, so all I snagged was round 3

[project dragon]

TWLB Semifinals: Strike vs Pandora



Timestamps:

00:44 game 1 start
29:06 game 1 scorebox
36:35 game 2 start
1:05:56 game 2 scorebox

[Dwopple]

TWL Semifinals matches

TWLJ
Bounced between both matches

TWLB
Cuphead vs Silence full matchup, and ending of Strike vs Pandora round 2

TWLD
Bounced between both matches, and full round 3 match of Pandora vs Strike LD

[PrOnEsSim]

TWL Playoffs - need to rework mic audio, lol

https://www.twitch.tv/videos/1016990806
Javs timestamp at 0:00 - Strike vs Cuphead

Base timestamp at 42:47 - Silence vs Cuphead

1:50:19 the end of Pandora vs Strike


TWLD Timestamp 02:08 - Pandora vs Strike (ALL 3 Rounds) - had 2 afk the last round.


Will cover next week's finals! good luck to the remaining teams.

[Dennys]

Hey guys, I streamed a bit of the matches yesterday as well. Did some commentary, feel free to use the VOD.

https://www.twitch.tv/cuch/v/1016959751?sr=a&t=0s

[ogron]

project dragon
Dwopple
PrOnEsSim
Dennys

Awesome work, thanks for recording all the games!

[project dragon]

One thing to note from the basing games:

Both matches had flag jupes, but only the Silence/Cuphead game got their jupe reset manually (turb @ 00:59:00 on TJ's vid). What is the official protocol for jupes?


There was one jupe in the pandora/strike game (https://youtu.be/iHgOuN6YHJM?t=3664) that lasted 20 seconds. You could argue that it doesn't make a difference as Strike lost by a minute, but I would say things could also possibly look different in FR when both terr's died at 14:02-14:56. I would say that Terr strats could be different if the previous jupe was reset and the score was 14:22-14:36. Pressure wouldn't have needed to go so offensive if he knew he had SOME time.

I'm not really arguing for anything to be overturned, and no team has filed a complaint, so I'm just looking at this from a officiating perspective. If staff now has powers to reset a jupe, it should be applied evenly for all matches.

[zidane]

interesting, not sure if anyone noticed during the game.. i definitely didn't. just watched the last few mins from where you linked and wish i had saved a mine near the end (1:05:12) as it probably would have wrecked them so that's tough to see. 20 seconds could have changed the terring dynamic in the final FR sequence so that's annoying but it's very possible there were jupes that went our way in the series also.

edit: to answer your question PJ i believe it's the players who are expected to reset the flag if there's a jupe, there is a command that i'm assuming only (C) or (A) can use. I have never used it myself but I've seen it a few times in twbd recently, most likely just no one on Strike noticed the jupe or knew the command

[Vehicle]

Regarding jupes, both teams have to have a cap or assistant PM the bot with "!jupe" to reset the flag, at which point it still needs to be re-claimed.

It's a bad system, but apparently it cannot be automated. There are plenty of (way less consequential) games that are won/lost on jupes, it'd be great if there were another way to fix it.

[qan]

Checked the logic for !jupe, as I wasn't sure, either.

Just one C/A from only one of the playing teams needs to issue the command. (Alternately, a TWDOp can also issue the command.)


The reason it can't be automated: the bug has to do with a difference in recorded flag state that players see vs what the bot sees. (Bots are fake Continuum clients. They sometimes aren't as reliable as the client itself.) So on the screen the flag state resolves correctly, but in the bot's mind, it thinks the wrong team owns it. !jupe tells the bot it's confused about the flagstate, so the bot resets the flag and then the holding team can reclaim it. It's not a great solution. A far better solution would be to figure out what difference there is between the Continuum client's handling of flag states and TWCore's. Unfortunately this involves something called "race conditions" (which are great fun to debug, as well as for your uncle to bring up at Thanksgiving). It's also not simple to compare how the client handles it, as the code is only available in a badly decompiled state. We have the dubious distinction of being the longest-running game without access to its own codebase. It's kind of beautiful, though, as this locks it permanently in time rather than having it at the whim of the flavor of the day coder.

[project dragon]

Thanks for the clarification everyone. It looks like the jupe I saw (I think there were others, but too lazy to check) was due to Ro dying as he touched the flag so I understand why it happened, but I appreciate the explanation on how jupes are currently resolved. Guess I haven't do much bot commands in a while...