Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Trung giản thể)
繁體中文 (Trung phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bulgaria)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraina)
Báo cáo lỗi dịch thuậ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.