Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
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.