安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Similarly I have spent 15 minutes trying to understand why regional trains are not going to coach yards. Yeah, it's separate techonology.
Might be I dumb, but I played a lot of OpenTTD and NEVER had such kind of issues trying to understand how to build intersections/signals/etc. I think a lot of stuff needed additional tooltips "why it's not working", "why the train stopped", etc.
And then the subtask instructs you to
And the tooltip for the command says:
However, I realized recently that because the most recent value is pre-set, the subtask may be instantly marked as done in the subsequent passes through the tutorial (because you set it to 3 so it was already pre-set to 3 when you start the tutorial again. So I made a change recently:
It was rolled out on May 14.