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
One of the unfortunate realities of technical writing is that no matter how you choose to deliver information, no format will work for everyone. I chose this format because I thought it had the best odds of accomplishing what I wanted for people, and I put the warning at the front, but that's the best I've got I'm afraid.
If you have figured the entire game (or most of it) and are stuck on a specific thing, it doesn't matter much. But if the situation is the opposite and you don't know a lot of stuff yet, then it'd be easy to spoil the wrong thing for yourself.
Personally I don't mind the style, but then I'm one of the people who is in the former category.
@Mahr I'm so sorry to hear that! Can you tell me more about what you were looking for, so I can give that section of the guide some attention? Or do you mean that the style of the guide as a whole didn't work for you?