WEBVTT

00:00:08.340 --> 00:00:13.480
所以說，上次Team Cherry給我們絲綢之歌的
新聞已經是3000年前的事了

00:00:13.490 --> 00:00:17.010
絲綢之歌感覺好像是一場我們這一年來一起

00:00:17.010 --> 00:00:18.140
幻想出來的白日夢

00:00:18.140 --> 00:00:21.270
我差一點就要把頻道炸掉然後申請成為寄養家庭了呢

00:00:21.270 --> 00:00:26.290
但幸好，空洞騎士社群終於從一位意外的
同伴手上獲得一點慈悲

00:00:26.290 --> 00:00:28.380
那個人就是Leth

00:00:28.380 --> 00:00:34.050
如果你不認識他的話，Matthew Griffen，也就是Leth
最近開始用奇怪的方式

00:00:34.050 --> 00:00:36.800
提供我們絲綢之歌的新聞

00:00:36.800 --> 00:00:40.450
還記得那個絲綢之歌會在6月12日上市的

00:00:40.450 --> 00:00:41.450
謠言嗎？

00:00:41.450 --> 00:00:44.760
嘛，這件事情導致了另一個謠言：Team Cherry會在5月29日

00:00:44.760 --> 00:00:49.850
發布新消息，因為空洞騎士的預告片是在它上市前兩周出現的

00:00:49.850 --> 00:00:52.150
想當然爾，沒有任何東西在5月29被宣布

00:00:52.150 --> 00:00:55.510
但Leth在空洞騎士Discord上傳了一個謎題

00:00:55.510 --> 00:00:59.399
他認為給我們這個飢渴的社群一點東西可以抑制

00:00:59.399 --> 00:01:02.149
Team Cherry銷聲匿跡的痛苦

00:01:02.149 --> 00:01:05.530
這個謎題並沒有揭發任何東西，但能夠跟Leth在大家

00:01:05.530 --> 00:01:09.030
努力找出答案時互動還蠻有趣的

00:01:09.030 --> 00:01:12.110
現在看來，Willaim和Ari蠻喜歡Leth的這個點子

00:01:12.110 --> 00:01:16.560
所以他們開始給Leth一些可以當成謎題答案的素材

00:01:16.560 --> 00:01:19.570
這些謎底在前四個禮拜的每周一被宣布

00:01:19.570 --> 00:01:23.490
Leth甚至還給我了一個謎題，讓我放在自己的推特上

00:01:23.490 --> 00:01:24.490
給大家解開

00:01:24.490 --> 00:01:26.880
不過，我並沒有要花時間解釋這些謎題

00:01:26.880 --> 00:01:31.840
我推薦想要知道細節的大家看看fireb0rn和TacoTV的影片

00:01:31.840 --> 00:01:34.659
包含這些謎題本身和他們的解法

00:01:34.659 --> 00:01:37.260
他們在記錄這些東西上做得很好

00:01:37.260 --> 00:01:40.531
然後我知道我已經在這個頻道上討論
空洞騎士Discord很多次了

00:01:40.531 --> 00:01:43.130
但我真的覺得那是一個很好的社群

00:01:43.130 --> 00:01:47.049
大家很快速地就解開Leth的謎題，而且他們也

00:01:47.049 --> 00:01:50.500
做了很多空洞騎士和絲綢之歌的議題探討

00:01:50.500 --> 00:01:52.000
所以說大家都很棒啦

00:01:54.040 --> 00:01:58.480
在這個影片，我們會專注在謎底本身還有看看

00:01:58.490 --> 00:02:00.939
我們可以在其中猜想出什麼白癡的東西

00:02:00.939 --> 00:02:04.920
首先，我們看到了這個角色，基本上大家都叫他Huntress

00:02:04.920 --> 00:02:08.090
Leth在上傳謎題時都會附上一個zip檔案

00:02:08.090 --> 00:02:12.040
這些謎底的檔案都會需要密碼來解開

00:02:12.040 --> 00:02:15.739
這個zip檔的答案是Huntress

00:02:15.739 --> 00:02:20.269
檔案裡面有一個角色圖片、一個gif檔，還有一些短短的

00:02:20.269 --> 00:02:22.659
對話和一段敘述

00:02:22.659 --> 00:02:27.110
Huntress似乎是在一個山洞裡築了個巢，可能在Bonebottom

00:02:27.110 --> 00:02:28.139
附近

00:02:28.139 --> 00:02:31.099
我們也可以看到吊在天花板上的袋子

00:02:31.099 --> 00:02:34.629
特別注意看他們緩慢擺動的樣子

00:02:34.629 --> 00:02:38.230
這種沒有在空洞騎士裡懸吊物品出現的細節

00:02:38.230 --> 00:02:39.230
還蠻酷的

00:02:39.230 --> 00:02:43.279
Huntress一開始注意到大黃蜂身上帶著「他人的器官」

00:02:43.279 --> 00:02:48.950
接著她詢問大黃蜂願不願意給她那些器官，當作她孩子

00:02:48.950 --> 00:02:50.419
的「出生餐」

00:02:50.419 --> 00:02:55.840
Huntress被敘述為一個高大、年老的獵食者，等待她孩子們的誕生

00:02:55.840 --> 00:03:00.250
她相當輕視頭上的聖塔，還有前往聖塔的不幸傳道者們

00:03:00.250 --> 00:03:05.120
我們一定都有遇過這種跟別人要器官養小孩的人

00:03:05.120 --> 00:03:09.609
在這個例子裡，大黃蜂大概可以給這個角色從敵人上

00:03:09.609 --> 00:03:11.790
取得的收集物

00:03:11.790 --> 00:03:15.761
我們現在知道任務在絲綢之歌裡很重要，所以我們可能可以

00:03:15.761 --> 00:03:17.560
看到更多這種東西

00:03:17.560 --> 00:03:23.190
但以現在來說，我們只看過敵人掉落Rosaries和Shell Shards

00:03:23.190 --> 00:03:28.599
他也說大黃蜂可以她自己的器官，但我是覺得大黃蜂不會同意啦

00:03:28.599 --> 00:03:31.799
一個關於這個角色的細節是他看起來有點像

00:03:31.799 --> 00:03:36.631
很久以前Team Cherry給我們看的骨骸森林的圖片裡的生物

00:03:36.631 --> 00:03:38.579
一個原本會在空洞騎士裡的區域

00:03:38.579 --> 00:03:41.900
難道這些怪咖會是他的小孩嗎？

00:03:41.900 --> 00:03:46.171
Huntress同時也蠻清楚Pharloom的整體情況，這樣看來他似乎

00:03:46.171 --> 00:03:47.449
非常不喜歡呢

00:03:47.449 --> 00:03:51.769
她也有點鄙視聖塔，我們曾經在預告片裡稍微看過的地方

00:03:51.769 --> 00:03:55.809
這個地方大概被鈴鐺邪教控制了，此地似乎也是很多穿越

00:03:55.809 --> 00:03:58.279
Pharloom的蟲子的目的地

00:03:58.279 --> 00:04:05.010
所以說聖塔大概不是個好地方，但與此同時，這位小姐想要我們的器官

00:04:05.010 --> 00:04:07.610
所以我們大概不用太在乎她的意見

00:04:07.610 --> 00:04:11.290
最後一點，這張圖片的HUD怪怪的

00:04:11.290 --> 00:04:16.980
不知道為甚麼，線軸右邊的蓋子不見了，絲線本身還變粗了

00:04:16.980 --> 00:04:21.430
這有可能只是圖片出bug了，畢竟遊戲還在開發階段

00:04:21.430 --> 00:04:26.350
當然也有可能是，線軸本身可以被摧毀，就像空洞騎士的

00:04:26.350 --> 00:04:28.310
靈魂容器會毀損一樣

00:04:28.310 --> 00:04:32.970
但是，這個在角落的主軸也沒有發亮，根據以前的畫面

00:04:32.970 --> 00:04:36.080
在線軸的絲線充滿時，它應該要亮起

00:04:36.080 --> 00:04:39.070
我們在後面也看到他亮起的樣子

00:04:39.070 --> 00:04:41.920
所以說如果這個UI是錯的我也不會意外

00:04:44.600 --> 00:04:48.210
下一個角色名字似乎叫Grindle

00:04:48.210 --> 00:04:52.980
Grindle是一隻愛告密的蟲，他被鎖在我猜是鍍金城市

00:04:52.980 --> 00:04:54.630
的監牢裡面

00:04:54.630 --> 00:04:59.700
釋放他後，他會用貨幣跟大黃蜂交換資訊，但他的信用

00:04:59.700 --> 00:05:01.410
似乎沒有很好

00:05:01.410 --> 00:05:06.000
所以他大概會給我們很爛的資訊，因為說真的哪個角色

00:05:06.000 --> 00:05:07.970
會給我們直接的資訊啦

00:05:07.970 --> 00:05:11.540
從他的對話中，我們得知Grindle已經被關在這裡一陣子了

00:05:11.540 --> 00:05:15.940
我們也知道Grinldle試圖從Pharloom現在衰弱的狀態中圖利

00:05:15.940 --> 00:05:19.690
但我們沒有Pharloom現況的細節

00:05:19.690 --> 00:05:24.370
我們知道這是個被絲綢和歌曲詛咒的地方，但實際的細節還是

00:05:24.370 --> 00:05:25.980
有點模糊

00:05:25.980 --> 00:05:31.140
Grindle被稱為告密蟲，根據Google這並不是個真正存在的東西

00:05:31.140 --> 00:05:35.960
但他的頭是長的蠻像絲綢之歌第一個預告片中出現的敵人

00:05:35.960 --> 00:05:39.080
至暗示了我們可能會在遊戲中看到更多這個物種

00:05:39.080 --> 00:05:43.490
這個gif中也有許多值得探討的細節

00:05:43.490 --> 00:05:46.870
第一，我們在這裡還看得到其他被囚禁的人

00:05:46.870 --> 00:05:50.380
這隻蟲長的很像預告片中的其他敵人，不過這

00:05:50.380 --> 00:05:52.480
傢伙沒有戴頭巾

00:05:52.480 --> 00:05:57.780
或許他是教會的叛逃者，當然他們也有可能只是拿走他的頭飾來逞罰他

00:05:57.780 --> 00:06:01.440


00:06:01.440 --> 00:06:06.160


00:06:06.160 --> 00:06:09.420


00:06:09.420 --> 00:06:11.920


00:06:11.920 --> 00:06:16.220


00:06:16.220 --> 00:06:20.520


00:06:20.520 --> 00:06:24.400


00:06:24.400 --> 00:06:28.670


00:06:28.670 --> 00:06:29.780


00:06:29.780 --> 00:06:34.530


00:06:34.530 --> 00:06:39.200


00:06:39.200 --> 00:06:43.070


00:06:43.070 --> 00:06:45.510


00:06:45.510 --> 00:06:49.870


00:06:49.870 --> 00:06:50.870


00:06:50.870 --> 00:06:55.200


00:06:55.200 --> 00:06:57.140


00:06:59.710 --> 00:07:03.120


00:07:03.139 --> 00:07:07.860


00:07:07.860 --> 00:07:12.060


00:07:12.060 --> 00:07:14.020


00:07:14.020 --> 00:07:17.990


00:07:17.990 --> 00:07:20.640


00:07:20.640 --> 00:07:24.400


00:07:24.400 --> 00:07:28.840


00:07:28.840 --> 00:07:30.190


00:07:30.190 --> 00:07:35.550


00:07:35.550 --> 00:07:39.970


00:07:39.970 --> 00:07:40.970


00:07:40.970 --> 00:07:45.610


00:07:45.610 --> 00:07:48.210


00:07:48.210 --> 00:07:53.130


00:07:53.130 --> 00:07:54.130


00:07:54.130 --> 00:07:58.389


00:07:58.389 --> 00:08:00.570


00:08:00.570 --> 00:08:04.990


00:08:04.990 --> 00:08:09.030


00:08:09.030 --> 00:08:12.720


00:08:12.720 --> 00:08:16.419


00:08:16.419 --> 00:08:19.940


00:08:19.940 --> 00:08:24.190


00:08:24.190 --> 00:08:27.520


00:08:27.520 --> 00:08:31.310


00:08:31.310 --> 00:08:34.259


00:08:34.259 --> 00:08:38.659


00:08:38.659 --> 00:08:42.579


00:08:42.579 --> 00:08:43.579


00:08:43.579 --> 00:08:48.649


00:08:48.649 --> 00:08:54.220


00:08:54.220 --> 00:08:59.180


00:08:59.180 --> 00:09:03.180


00:09:05.500 --> 00:09:10.040


00:09:10.050 --> 00:09:13.660


00:09:13.660 --> 00:09:17.910


00:09:17.910 --> 00:09:21.420


00:09:21.420 --> 00:09:24.579


00:09:24.579 --> 00:09:28.850


00:09:28.850 --> 00:09:30.850


00:09:30.850 --> 00:09:34.220


00:09:34.220 --> 00:09:39.399


00:09:39.399 --> 00:09:40.580


00:09:40.580 --> 00:09:44.320


00:09:44.320 --> 00:09:49.920


00:09:49.920 --> 00:09:51.139


00:09:51.139 --> 00:09:54.610


00:09:54.610 --> 00:09:58.690


00:09:58.690 --> 00:10:04.420


00:10:04.420 --> 00:10:06.060


00:10:06.060 --> 00:10:10.180


00:10:10.180 --> 00:10:11.320


00:10:11.320 --> 00:10:16.189


00:10:16.189 --> 00:10:18.990


00:10:18.990 --> 00:10:21.040


00:10:21.040 --> 00:10:25.089


00:10:25.089 --> 00:10:26.670


00:10:26.670 --> 00:10:30.939


00:10:30.939 --> 00:10:36.230


00:10:36.230 --> 00:10:40.329


00:10:40.329 --> 00:10:42.449


00:10:42.449 --> 00:10:46.899


00:10:46.899 --> 00:10:49.370


00:10:49.370 --> 00:10:54.649


00:10:54.649 --> 00:10:57.440


00:10:57.440 --> 00:11:00.939


00:11:00.939 --> 00:11:05.240


00:11:05.240 --> 00:11:06.249


00:11:06.249 --> 00:11:11.180


00:11:11.180 --> 00:11:12.300


00:11:12.300 --> 00:11:16.640


00:11:16.640 --> 00:11:19.769


00:11:19.769 --> 00:11:23.750


00:11:23.750 --> 00:11:25.480


00:11:25.480 --> 00:11:27.830


00:11:27.830 --> 00:11:32.839


00:11:32.839 --> 00:11:36.740


00:11:36.740 --> 00:11:39.160


00:11:39.160 --> 00:11:43.470


00:11:43.470 --> 00:11:47.579


00:11:47.579 --> 00:11:50.559


00:11:50.559 --> 00:11:55.040


00:11:55.040 --> 00:12:00.320


00:12:00.320 --> 00:12:01.769


00:12:01.769 --> 00:12:07.089


00:12:07.089 --> 00:12:15.480


00:12:15.480 --> 00:12:17.410


00:12:17.410 --> 00:12:21.069


00:12:21.069 --> 00:12:22.069


00:12:22.069 --> 00:12:27.750


00:12:27.750 --> 00:12:30.839


00:12:30.839 --> 00:12:34.519


00:12:34.519 --> 00:12:39.459


00:12:39.459 --> 00:12:40.109