安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题









Here's a hint if you want one: As far as I know, it is not possible to do anything in the beginning other than arrive at the target host at an unknown cycle. What could possibly be affected by the cycle count? It's a mechanic/quirk that is quite easy to accidentally ignore.
If two of the nogo registers at home is removed, i can devise of a simple way to determine #WAIT:
XA does link 800, link 800, copy 1 M
XB counts to itself with a file
XC kills XB when TEST MRD is true and grabs its file, and outputs it to GOAL (wiping its file and killing XA)
to garret: It is possible to determine between 0 and 1 by a quirk of the timegate: 0 actually means one cycle before opening, and 1 means two. So if you do link 800 twice, you will get through 0 immediately. But for 1, you will pause for one cycle. So determining 0 and 1 isn't a problem
It does still seem impossible due to size constraints before TARGET is available...
I mean - even if there was room to spawn anything, how could I determine between 0 and 1 for example ? Presumably I'm just too stupid, but have you actually solved it yourself ?