WEBVTT Kind: captions Language: en Style: ::cue(c.color000000) { color: rgb(0,0,0); } ::cue(c.colorA39FDC) { color: rgb(163,159,220); } ::cue(c.colorC7EFFD) { color: rgb(199,239,253); } ::cue(c.colorF6CDD0) { color: rgb(246,205,208); } ::cue(c.colorFEFEFE) { color: rgb(254,254,254); } ::cue(c.colorFFB266) { color: rgb(255,178,102); } ::cue(c.colorFFFC00) { color: rgb(255,252,0); } ## 00:00:49.290 --> 00:00:53.360 Good morning, everyone! 00:00:53.360 --> 00:00:54.950 Six in the morning 00:00:54.950 --> 00:00:57.200 is upon us once more. 00:00:57.200 --> 00:01:01.030 This time, though, it's Friday, 00:01:01.030 --> 00:01:05.470 the last workday of the week! 00:01:05.470 --> 00:01:08.886 position:61% You have to give your best today, so... 00:01:08.886 --> 00:01:09.686 position:56% Wake up! Wake up! Wake up! Wake up! 00:01:08.886 --> 00:01:09.686 position:56% Wake up! Wake up! Wake up! Wake up! 00:01:09.686 --> 00:01:10.187 position:56% Wake up! Wake up! Wake up! Wake up! 00:01:09.686 --> 00:01:10.187 position:56% Wake up! Wake up! Wake up! Wake up! 00:01:10.187 --> 00:01:10.654 position:56% Wake up! Wake up! Wake up! Wake up! 00:01:10.187 --> 00:01:10.654 position:56% Wake up! Wake up! Wake up! Wake up! 00:01:10.654 --> 00:01:11.180 Wake up! Wake up! Wake up! Wake up! 00:01:11.180 --> 00:01:13.070 Wake up, okay? 00:01:13.070 --> 00:01:15.800 If you're bad at getting up early, 00:01:15.800 --> 00:01:17.840 if you get habituated to 00:01:17.840 --> 00:01:21.200 watching Morning Coco Live, 00:01:21.200 --> 00:01:23.790 you may manage to always wake up. 00:01:23.790 --> 00:01:24.910 That said, 00:01:24.910 --> 00:01:27.200 we have lots of news 00:01:27.200 --> 00:01:31.150 to inform you about, so let's have a look, shall we? 00:01:32.400 --> 00:01:33.500 Aah... 00:01:33.500 --> 00:01:34.610 As you can see, 00:01:34.610 --> 00:01:36.630 there's been a crowd rattling 00:01:36.630 --> 00:01:38.370 above my head, every morning, 00:01:38.370 --> 00:01:41.480 for the entire week. This crowd is none other 00:01:41.480 --> 00:01:44.210 than today's viewer-commentators! 00:01:44.210 --> 00:01:46.320 Good morning! 00:01:46.320 --> 00:01:47.070 Ehehe. 00:01:47.070 --> 00:01:48.490 Good morning! 00:01:48.490 --> 00:01:50.270 Everyone's energetically 00:01:50.270 --> 00:01:53.300 saying "good morning" and "rattle rattle". 00:01:53.300 --> 00:01:56.380 We seem to have lots of things to inform you about, 00:01:56.380 --> 00:01:59.130 but we have to start it off with this. 00:01:59.130 --> 00:02:01.750 A pathetic report! 00:02:02.280 --> 00:02:03.100 Oh my! 00:02:03.100 --> 00:02:05.540 Some days ago, this stream 00:02:05.540 --> 00:02:08.280 called "Shadow Game" was realized, 00:02:08.280 --> 00:02:11.910 and it was perplexing, a totally random stream. 00:02:11.910 --> 00:02:13.420 It was broadcast 00:02:13.420 --> 00:02:17.800 from Aqua-paisen's channel, 00:02:17.800 --> 00:02:19.300 and, oh my...! 00:02:19.300 --> 00:02:21.670 Just to begin with, 00:02:21.670 --> 00:02:25.240 from the very start of this stream, 00:02:25.080 --> 00:02:55.080 line:71% Ms. Marine's choppy resolution 00:02:25.240 --> 00:02:28.320 Marine-paisen's resolution 00:02:28.320 --> 00:02:32.820 was very choppy, and everyone could tell. 00:02:32.820 --> 00:02:36.880 Just compare them; she's as choppy as it gets. 00:02:36.880 --> 00:02:40.870 You'd think she'd just been through the chopping board. 00:02:40.870 --> 00:02:41.910 And, to top it off, 00:02:41.910 --> 00:02:44.110 this stream's gimmick 00:02:44.110 --> 00:02:46.870 position:58% had a special rule: They'd play games 00:02:46.870 --> 00:02:50.290 position:58% and for each loss, their bodies would 00:02:50.290 --> 00:02:53.870 gradually start fading away. 00:02:53.870 --> 00:02:55.130 And you won't believe it... 00:02:55.080 --> 00:03:47.750 position:70% line:71% Disappearing and exploding in mere 30 minutes 00:02:56.060 --> 00:02:58.950 position:69% Both have pretty much disappeared 30 min in. 00:02:58.950 --> 00:03:00.930 Barely 30 minutes in, 00:03:00.930 --> 00:03:04.750 they're too transparent to be seen 00:03:04.750 --> 00:03:06.780 and the punchline was an explosion. 00:03:07.180 --> 00:03:09.050 This is... 00:03:09.050 --> 00:03:10.340 Hmm... 00:03:10.340 --> 00:03:14.560 This is pretty pathetic, don't you think? 00:03:14.560 --> 00:03:16.520 Let's see what you guys think: 00:03:17.530 --> 00:03:18.540 "wew" 00:03:18.540 --> 00:03:20.080 "lol" 00:03:20.080 --> 00:03:22.350 "explosions for a punchline? simply the worst" 00:03:22.350 --> 00:03:23.100 Uh... 00:03:23.100 --> 00:03:24.750 "what a mess lol" 00:03:24.750 --> 00:03:25.550 Hm... 00:03:25.550 --> 00:03:26.740 Many people are saying 00:03:26.740 --> 00:03:28.910 explosions for a punchline 00:03:28.910 --> 00:03:31.700 is simply the worst, now this is... 00:03:31.700 --> 00:03:35.050 We'll have to agree. This was pathetic. 00:03:35.050 --> 00:03:37.850 No doubt about it, if you ask me. 00:03:37.850 --> 00:03:38.790 Well... 00:03:38.790 --> 00:03:42.300 Speaking of pathetic... 00:03:42.300 --> 00:03:44.250 there was even more of it 00:03:44.250 --> 00:03:46.520 yesterday, wasn't there? 00:03:46.520 --> 00:03:47.750 Oh my! 00:03:47.750 --> 00:04:12.510 line:71% 7/2 Stream on Ookami Mio's channel 00:03:48.570 --> 00:03:50.570 Some days ago, we did― 00:03:50.570 --> 00:03:52.650 We did it yesterday, actually. 00:03:52.650 --> 00:03:56.380 The Onomatopoeia King Competition. 00:03:56.380 --> 00:03:57.560 I see that 00:03:57.560 --> 00:04:00.930 Ms. Kiryu C.Co participated, 00:04:00.930 --> 00:04:06.630 position:58% but this was a stream that took place on Mio-paisen's channel. 00:04:06.630 --> 00:04:08.870 And you won't believe it! 00:04:08.870 --> 00:04:12.450 Some of you seem to know already, 00:04:12.510 --> 00:04:54.480 position:59% line:68% Unbelievable: Oversleeps and doesn't make it in time for stream 00:04:13.590 --> 00:04:15.270 but much to everyone's surprise, 00:04:15.270 --> 00:04:16.920 unlikely as it may sound, 00:04:16.920 --> 00:04:20.650 Someone was late for this stream... 00:04:20.650 --> 00:04:22.100 Ms. Sakura Miko! 00:04:22.100 --> 00:04:25.090 Unbelievable, she overslept 00:04:25.090 --> 00:04:27.960 and didn't make it in time... 00:04:27.960 --> 00:04:29.710 This is... 00:04:29.710 --> 00:04:30.860 Well... 00:04:30.860 --> 00:04:33.340 Pathetic, isn't it? 00:04:33.340 --> 00:04:36.510 position:66% This is no doubt― I see someone trembling. 00:04:36.510 --> 00:04:37.910 This is, 00:04:37.910 --> 00:04:38.820 uuh... 00:04:38.820 --> 00:04:43.940 I guess even an elite can be pathetic sometimes. 00:04:43.940 --> 00:04:45.470 However, 00:04:45.470 --> 00:04:47.230 truth is, a little while 00:04:47.230 --> 00:04:51.710 before the stream started― The stream was scheduled for 7 PM. 00:04:51.710 --> 00:04:54.610 The stream would start at 7 PM, 00:04:54.480 --> 00:06:03.150 position:61% line:78% Tweets at 18:33 (Stream starts at 7 PM) 00:04:55.860 --> 00:04:56.880 and, as you see here, 00:04:56.880 --> 00:05:00.300 at 6:33 PM, 00:05:00.300 --> 00:05:02.710 Miko-paisen posted "Nyahello! 00:05:02.710 --> 00:05:06.190 This is today's schedule!" 00:05:06.190 --> 00:05:10.160 on Twitter, did anyone see it? 00:05:10.160 --> 00:05:11.330 The tweet was 00:05:11.330 --> 00:05:15.250 posted on 6:33 PM, 00:05:15.250 --> 00:05:17.340 so this should mean 00:05:17.340 --> 00:05:20.820 position:64% that she's preparing for the 7 PM stream. 00:05:20.820 --> 00:05:23.000 She oughta be, right? 00:05:23.000 --> 00:05:25.600 Or so you'd think, but... 00:05:25.600 --> 00:05:28.410 This got posted 00:05:28.410 --> 00:05:32.900 at 6:33 PM, but the exact hour 00:05:32.900 --> 00:05:35.580 the members gathered 00:05:35.580 --> 00:05:37.410 to prepare for this stream 00:05:37.410 --> 00:05:41.090 was 6:40 PM. 00:05:41.090 --> 00:05:45.840 position:63% So when the members gathered at 6:40 PM, 00:05:45.840 --> 00:05:50.500 position:59% they were like, "Miko-paisen tweeted 7 minutes ago, so there's no problem." 00:05:50.500 --> 00:05:52.130 "She'll soon be here, right?" 00:05:52.130 --> 00:05:53.090 "Any time now." 00:05:53.090 --> 00:05:53.970 "..." 00:05:53.970 --> 00:05:55.270 "Where is she?" 00:05:55.910 --> 00:05:57.680 "Why isn't she coming?!" 00:05:57.680 --> 00:05:59.660 "Where did she go?!" and so on. 00:05:59.660 --> 00:06:03.470 position:63% Everyone started to get nervous by then. 00:06:03.150 --> 00:06:43.280 line:71% Ms. Shirakami Fubuki's Soulful Call 00:06:03.150 --> 00:06:43.280 align:start position:0% line:57% @SakuraMiko MIKOOOOOOOOOOOOOOOOOO 00:06:03.470 --> 00:06:04.800 Even she, 00:06:04.800 --> 00:06:07.360 Fubuki-paisen let out a soulful 00:06:07.360 --> 00:06:10.090 call for her, to no avail. 00:06:10.090 --> 00:06:13.600 This call happened at 6:53 PM, 00:06:13.600 --> 00:06:16.730 position:63% 13 minutes after everyone had assembled. 00:06:16.730 --> 00:06:18.110 That's when it sank in. 00:06:18.110 --> 00:06:19.890 Everyone panicked, "Did she forget?" 00:06:19.890 --> 00:06:21.890 "No way she'd forget, right?" 00:06:21.890 --> 00:06:23.570 "But..." 00:06:23.570 --> 00:06:24.600 "Did she fall asleep?" 00:06:24.600 --> 00:06:25.690 "Is she sleeping?" 00:06:25.690 --> 00:06:28.770 position:61% That's what everyone was thinking then. 00:06:28.770 --> 00:06:30.170 But, even so, 00:06:30.170 --> 00:06:31.940 considering how she 00:06:31.940 --> 00:06:34.340 had tweeted three minu― seven minutes earlier, 00:06:34.340 --> 00:06:36.280 position:66% it's unlikely she'd tweet and sleep after. 00:06:36.280 --> 00:06:39.020 I'm sure you're considering that. 00:06:39.020 --> 00:06:40.700 Here's a secret for you guys: 00:06:40.700 --> 00:06:43.470 Remember this stream? 00:06:43.280 --> 00:07:41.050 position:61% line:71% 6/25 Stream on Murasaki Shion's channel 00:06:43.850 --> 00:06:45.950 Some time ago, 00:06:45.950 --> 00:06:48.930 I did this stream. 00:06:48.930 --> 00:06:50.950 On June 25th, 00:06:50.950 --> 00:06:54.530 on Murasaki Shion's channel, 00:06:54.530 --> 00:06:57.690 we aired this Kanji Battle stream. 00:06:57.690 --> 00:06:59.910 The thing is... 00:06:59.910 --> 00:07:01.850 When we did this, 00:07:01.850 --> 00:07:03.510 the members were 00:07:03.510 --> 00:07:07.770 me, Shion-paisen, and A-chan, this trio. 00:07:07.770 --> 00:07:09.190 But, actually, 00:07:09.190 --> 00:07:12.120 when we first assembled to prepare, 00:07:12.120 --> 00:07:14.610 only Ms. A-chan and I were there. 00:07:14.610 --> 00:07:15.680 So, we also 00:07:15.680 --> 00:07:16.450 *oh shion* 00:07:16.450 --> 00:07:18.990 considered that Shion-paisen 00:07:18.990 --> 00:07:21.530 was possibly still asleep. 00:07:21.530 --> 00:07:24.460 Just a vague suspicion. 00:07:24.460 --> 00:07:27.190 But, just like in the other case, Shion-paisen had, 00:07:27.190 --> 00:07:28.100 just a few 00:07:28.100 --> 00:07:31.330 position:56% minutes ago, roughly 10 minutes ago, 00:07:31.330 --> 00:07:32.780 she tweeted. 00:07:32.780 --> 00:07:34.880 So we figured it was fine. 00:07:34.880 --> 00:07:38.090 "She tweeted 10 minutes ago, it's fine." 00:07:38.090 --> 00:07:38.600 As such, 00:07:38.600 --> 00:07:41.150 Ms. A-chan and I waited for her. 00:07:41.050 --> 00:08:12.710 line:68% Shion tweeted minutes ago, but didn't show up for assembly time 00:07:41.050 --> 00:08:12.710 align:start position:0% line:45% Alright!! What will we do if Shion-paisen doesn't show up? 00:07:41.810 --> 00:07:43.150 Ultimately, 00:07:43.790 --> 00:07:46.370 position:69% she didn't appear when we agreed to assemble 00:07:46.370 --> 00:07:49.150 and airing time drew ever closer. 00:07:49.490 --> 00:07:52.630 Both Ms. A-chan and I were quite 00:07:52.630 --> 00:07:54.250 troubled by that. 00:07:54.250 --> 00:07:55.150 "Oh no... Oh no..." 00:07:55.150 --> 00:07:55.590 "wuh?" 00:07:55.590 --> 00:07:56.490 "How can 00:07:56.490 --> 00:07:57.700 Shion-senpai 00:07:57.700 --> 00:08:00.050 be asleep if she's made a tweet? Is she really sleeping?" 00:08:00.050 --> 00:08:01.320 And so on. 00:08:01.320 --> 00:08:02.600 But, in the end, 00:08:02.600 --> 00:08:05.790 when it was about airing time, 00:08:05.790 --> 00:08:08.210 Shion appeared, 00:08:08.210 --> 00:08:08.880 even though 00:08:08.880 --> 00:08:11.480 position:61% she didn't make it for assembling time. 00:08:11.480 --> 00:08:13.190 When she finally showed up, 00:08:12.710 --> 00:08:23.080 size:66% position:33% line:68% "Phew, that was close I was asleep." 00:08:13.190 --> 00:08:14.810 she said, "phew, that was close. 00:08:15.180 --> 00:08:16.880 I was asleep." She was asleep. 00:08:16.880 --> 00:08:18.490 We asked how was she asleep, 00:08:18.490 --> 00:08:21.840 considering she had tweeted 10 minutes earlier. 00:08:21.840 --> 00:08:23.610 And her reply was, 00:08:23.080 --> 00:08:48.710 size:84% position:42% line:71% "That was a scheduled post" 00:08:23.610 --> 00:08:25.690 "That was a scheduled tweet." 00:08:25.690 --> 00:08:27.030 This was when 00:08:27.030 --> 00:08:30.120 I learned how fearsome 00:08:30.120 --> 00:08:34.740 scheduled posts can be. 00:08:34.740 --> 00:08:36.310 Oh well. 00:08:36.310 --> 00:08:38.410 This is... kind of... 00:08:38.410 --> 00:08:40.700 When a tweet is scheduled, 00:08:40.700 --> 00:08:44.340 position:70% it doesn't matter how long ago it was posted, 00:08:44.340 --> 00:08:45.930 it becomes irrelevant. 00:08:45.930 --> 00:08:47.310 In regards to this, 00:08:47.310 --> 00:08:49.010 this is what Expert C had to say: 00:08:48.710 --> 00:09:57.380 position:66% line:68% The schedule post function has made stalking celebrities in real-time obsolete 00:08:49.940 --> 00:08:52.660 position:56% "The schedule fun― The schedule post 00:08:52.660 --> 00:08:54.800 function has made 00:08:54.800 --> 00:08:57.270 position:69% stalking celebrities in real-time obsolete." 00:08:57.270 --> 00:08:58.830 You can't stalk 00:08:58.830 --> 00:09:02.050 celebrities in real-time anymore. 00:09:02.050 --> 00:09:03.900 Don't you see it often? 00:09:03.900 --> 00:09:05.890 Checking out if, during Christmas, 00:09:05.890 --> 00:09:08.440 a voice actress isn't, y'know... 00:09:08.440 --> 00:09:09.350 Doing... y'know? 00:09:09.350 --> 00:09:13.050 position:64% Going to her BF's house behind our backs. 00:09:13.050 --> 00:09:15.110 The otaku do it every year. 00:09:15.110 --> 00:09:16.790 They do, don't they? 00:09:16.790 --> 00:09:20.130 By using this function, 00:09:20.130 --> 00:09:21.550 it completely 00:09:21.550 --> 00:09:24.540 throws stalkers off the trail. 00:09:24.540 --> 00:09:25.710 Since, y'know, 00:09:25.710 --> 00:09:28.600 they can post it ahead of time, 00:09:28.600 --> 00:09:30.470 saying they're at home 00:09:30.470 --> 00:09:33.980 position:58% eating dinner, posting a selfie even. 00:09:33.980 --> 00:09:36.220 But they can just post that 00:09:36.220 --> 00:09:38.740 way ahead of time now. 00:09:38.740 --> 00:09:40.120 Oh weeeeell... 00:09:40.120 --> 00:09:40.510 Well. 00:09:40.510 --> 00:09:43.200 But then there's Ms. Kiryu Coco. 00:09:43.200 --> 00:09:45.370 A very serious, proper, 00:09:45.370 --> 00:09:48.760 position:63% and sincere pro idol like Ms. Kiryu Coco 00:09:48.760 --> 00:09:50.320 would never do that. 00:09:50.320 --> 00:09:53.840 She never lies or fakes anything, 00:09:53.840 --> 00:09:56.280 I'll even tell you that 00:09:56.280 --> 00:09:58.720 she's already scheduled a post 00:09:57.380 --> 00:11:14.480 size:81% position:41% line:71% The ideal sincere pro idol 00:09:57.380 --> 00:11:14.480 align:start position:0% line:43% SEGA and I had a fantastic night together 00:09:58.720 --> 00:10:02.880 to go up on this year's Christmas. 00:10:02.880 --> 00:10:04.880 She doesn't lie. 00:10:04.880 --> 00:10:06.780 This is a prediction. 00:10:06.780 --> 00:10:09.380 She'll be with her BF, ＳＥ→ＧＡ↑, 00:10:09.380 --> 00:10:12.450 having a fantastic night. 00:10:12.450 --> 00:10:14.540 You can trust Coco, guys. 00:10:14.540 --> 00:10:15.850 As you can see― 00:10:15.850 --> 00:10:16.650 Well, to be honest, 00:10:16.650 --> 00:10:19.470 from where I comed from― 00:10:19.470 --> 00:10:21.480 came... 00:10:21.480 --> 00:10:22.650 Uh... Uh... 00:10:22.650 --> 00:10:24.840 Back in the US of Dragon America, 00:10:24.840 --> 00:10:27.250 Christmas is 00:10:27.250 --> 00:10:31.730 not a day you spend with your boyfriend. 00:10:31.730 --> 00:10:34.960 This is a Japan-exclusive thing, did you know? 00:10:34.960 --> 00:10:35.960 Erm... 00:10:35.960 --> 00:10:38.150 Christmas means family, 00:10:38.150 --> 00:10:41.490 a day to spend with your family. 00:10:41.490 --> 00:10:45.480 As for me, my family comes over from Friday to Sunday, 00:10:45.480 --> 00:10:47.550 position:64% and you can hear them on my streams even, 00:10:47.550 --> 00:10:50.960 so I'd personally like some distance from my family. 00:10:50.960 --> 00:10:52.870 By the way, 00:10:52.870 --> 00:10:56.340 my dragon relatives will be around, 00:10:56.340 --> 00:10:58.400 position:59% and, for whatever reason, some friends 00:10:58.400 --> 00:11:00.900 of my dragon relatives will also be 00:11:00.900 --> 00:11:02.320 staying over, what a nightmare. 00:11:02.320 --> 00:11:05.470 Tonight will be rumbly, I feel. 00:11:05.470 --> 00:11:06.420 Oh well. 00:11:06.420 --> 00:11:09.400 position:63% With that said, going back to the topic, 00:11:09.400 --> 00:11:11.440 position:56% Miko-paisen's tweet is what matters. 00:11:11.440 --> 00:11:14.680 What was the issue there, you ask? 00:11:14.480 --> 00:11:37.110 line:71% Confesses it was a scheduled tweet 00:11:15.290 --> 00:11:17.380 You guessed it, Miko-paisen had, 00:11:17.380 --> 00:11:19.280 as she confessed 00:11:19.280 --> 00:11:22.450 during the aforementioned stream, 00:11:22.450 --> 00:11:24.030 used the schedule function. 00:11:24.390 --> 00:11:26.480 If she scheduled it― 00:11:26.480 --> 00:11:27.050 Then 00:11:27.050 --> 00:11:29.540 forgot she scheduled 00:11:29.540 --> 00:11:32.630 and went to sleep. 00:11:32.630 --> 00:11:34.640 Then, during this, erm, 00:11:34.640 --> 00:11:37.240 onomatopoeia stream, she 00:11:37.110 --> 00:11:56.050 position:83% line:71% Filling in for the wait time while points are tallied 00:11:37.240 --> 00:11:38.500 had to, as punishment, 00:11:38.500 --> 00:11:41.830 position:77% fill in the wait time while points where tallied. 00:11:41.830 --> 00:11:42.580 Erm, 00:11:42.580 --> 00:11:44.810 I think you guys saw Miko-paisen 00:11:44.810 --> 00:11:47.490 having to deal with odd topics, 00:11:47.490 --> 00:11:49.710 but here's the behind the scenes: 00:11:49.710 --> 00:11:51.790 The one who 00:11:51.790 --> 00:11:54.210 thought up the second round 00:11:54.210 --> 00:11:56.180 of onomatopoeia she did 00:11:56.050 --> 00:13:30.380 line:68% Kiryu Coco suggested Misogi, the Shinto purification ritual 00:11:56.180 --> 00:11:57.130 was― 00:11:57.130 --> 00:12:00.940 That was my suggestion, which I secretly sent. 00:12:01.950 --> 00:12:04.680 position:69% I sneaked away a little to whisper that one. 00:12:04.680 --> 00:12:05.570 Erm, 00:12:05.570 --> 00:12:07.280 the second act by Miko-paisen, 00:12:07.280 --> 00:12:09.700 that second thing, it was my idea. 00:12:09.700 --> 00:12:11.510 I secretly sent it to Mio-paisen. 00:12:11.510 --> 00:12:12.880 I used... 00:12:12.880 --> 00:12:14.250 I sent it via Discord. 00:12:14.250 --> 00:12:15.090 Hahaheehee. 00:12:15.090 --> 00:12:16.310 "it was you?!" 00:12:16.310 --> 00:12:17.040 Yup. 00:12:17.040 --> 00:12:19.460 After that, Mio-senpai nimbly 00:12:19.460 --> 00:12:21.160 position:56% switched the actual theme with that. 00:12:21.160 --> 00:12:22.710 But, then again, 00:12:22.710 --> 00:12:26.250 she didn't tell me she'd use it. 00:12:26.250 --> 00:12:28.690 Since I was being sneaky, 00:12:28.690 --> 00:12:30.690 and there was no reply to it, 00:12:30.690 --> 00:12:31.620 I, y'know, 00:12:31.620 --> 00:12:33.480 didn't know if my 00:12:33.480 --> 00:12:36.380 secret suggestion 00:12:36.380 --> 00:12:37.680 would be used or not, 00:12:37.680 --> 00:12:38.580 then, later, 00:12:38.580 --> 00:12:41.740 when Miko-paisen was going "bowaaa" 00:12:41.740 --> 00:12:43.410 "bobobowa" and so on, 00:12:43.410 --> 00:12:45.590 I wrote something else entirely. 00:12:45.590 --> 00:12:47.450 I suggested it, 00:12:47.450 --> 00:12:48.210 erm, 00:12:48.210 --> 00:12:51.660 position:63% it was my idea, but I answered it wrong. 00:12:51.660 --> 00:12:53.490 position:56% Since I didn't know if it'd be used. 00:12:53.490 --> 00:12:56.360 Miko-paisen's second theme, 00:12:56.360 --> 00:12:58.990 I said it was a party-goer. 00:12:58.990 --> 00:13:00.070 "everyone got it wrong" 00:13:00.070 --> 00:13:01.420 Heeheeheehe. 00:13:01.420 --> 00:13:03.190 I had no idea! 00:13:03.190 --> 00:13:03.770 Gaddem. 00:13:03.770 --> 00:13:05.700 'Twas too difficult. 00:13:05.700 --> 00:13:07.850 With that said, guys, 00:13:07.850 --> 00:13:09.010 uuh, uh... 00:13:09.010 --> 00:13:10.990 Let's see the next one. 00:13:10.990 --> 00:13:12.560 "you really didn't know" 00:13:12.560 --> 00:13:14.160 I really didn't. 00:13:14.160 --> 00:13:16.910 That was 4D chess. 00:13:18.090 --> 00:13:20.290 She secretly decided to use it, 00:13:20.290 --> 00:13:23.680 position:78% so even if I was secretly in on it, I didn't know. 00:13:23.680 --> 00:13:25.400 That said, next report! 00:13:25.400 --> 00:13:26.360 Oh my! 00:13:26.360 --> 00:13:30.650 It's an ARK report, guys! 00:13:30.380 --> 00:13:57.780 position:72% line:71% Ms. Shirakami Fubuki enters the Crystal Isles! 00:13:31.460 --> 00:13:32.840 Yay! 00:13:32.840 --> 00:13:33.660 Why, 00:13:33.660 --> 00:13:37.010 position:63% it's Ms. Shirakami Fubuki! She's finally 00:13:37.010 --> 00:13:39.120 descending upon 00:13:39.120 --> 00:13:41.670 the crystal world! 00:13:41.670 --> 00:13:44.600 We'll finally see Fubuki-paisen 00:13:44.600 --> 00:13:45.620 play Crystal and 00:13:45.620 --> 00:13:47.370 come back to ARK, 00:13:47.370 --> 00:13:50.660 it's been quite a while, hasn't it? 00:13:50.660 --> 00:13:51.590 Uhh, right? 00:13:51.590 --> 00:13:52.730 Yesterday I was 00:13:52.730 --> 00:13:55.030 waiting if she'd come. 00:13:55.030 --> 00:13:55.790 Uhh... Oh? 00:13:55.790 --> 00:13:58.130 Meanwhile, elsewhere... 00:13:57.780 --> 00:14:12.550 align:end position:100% line:78% ARK stream aired July 2 @ Coco Ch. 00:13:58.130 --> 00:13:59.880 Ms. Kiryu Coco 00:13:59.880 --> 00:14:01.330 seems to have 00:14:01.330 --> 00:14:04.230 set her foot upon 00:14:04.230 --> 00:14:06.420 a whole new 00:14:06.420 --> 00:14:07.740 and unknown 00:14:08.150 --> 00:14:11.620 world of ARK― This doesn't look like 00:14:11.620 --> 00:14:14.600 Crystal Isles though...! 00:14:14.600 --> 00:14:16.480 Time for an ad. 00:15:52.010 --> 00:15:54.190 *hype* 00:15:54.510 --> 00:15:56.700 Here we have―! 00:15:56.700 --> 00:15:57.860 Waaah! 00:15:57.860 --> 00:15:59.950 It's finally here! 00:15:59.950 --> 00:16:02.760 Along with the blissfully peaceful 00:16:02.760 --> 00:16:05.480 world of Crystal Isles, 00:16:05.480 --> 00:16:07.000 comes―! 00:16:07.000 --> 00:16:08.440 ―comes two more 00:16:08.440 --> 00:16:11.140 different and dangerous worlds! 00:16:11.140 --> 00:16:13.000 We've kept you guys waiting! 00:16:11.250 --> 00:16:51.410 position:64% line:68% Two new official maps added to ARK server "Cross ARK" feature enabled! 00:16:13.000 --> 00:16:16.970 position:72% We added two more official maps to our server! 00:16:16.970 --> 00:16:19.470 I worked hard to add 00:16:19.470 --> 00:16:21.700 that Cross ARK setting! 00:16:21.700 --> 00:16:22.570 You see, 00:16:22.570 --> 00:16:24.740 the teleportation modules― 00:16:24.740 --> 00:16:28.610 position:77% I've enabled all the teleportation modules in ARK 00:16:28.610 --> 00:16:31.440 to allow you travel to other maps 00:16:31.440 --> 00:16:34.180 in the blink of an eye! And there's more! 00:16:34.180 --> 00:16:37.730 position:66%