Установить 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 (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом











Remember folks, always double-check if the reactor is actually turned off!
@Cardinal: Thanks for reporting. Seems like I forgot to disable the code to make the reactor go critical when swapping modules for the outpost reactor type. All other's have had the code disabled or didn't even feature the code as I was just testing it, but I guess I overlooked the outpost reactor after testing. It's now fixed.
I've also increased time to react to the reactor going critical since it could still be quite challenging in multiplayer due to latency.
I suppose this is expected behaviour, but it makes beacon missions not worth early game.