Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem











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.