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
also the brig, it has now a property that bots won't interact with the door and therefore won't get stuck.
- deepcharge launch tube isnt connectet to deep charge loader, so you can't drop them
- motor of bay door "submarine" is still on, so it's making noise on pasive sonar
- third oxygen shelf from left in airlock room, isn't wired
- one of memory components near drone control monitor isn't wired
* Couple logic components visible on top of the drone nav terminal
* May I suggest automatic drone docking and undocking based on the docking hatch's proximity_sensor output?
* Only reason I'm probably not going to use this in my single player campaign is that the railgun periscope is in ♥♥♥♥♥♥♥ Argentina xD
-Fixed sprite depth
-Docking the drone is now automatic, to undock you still need to do it in the nav terminal
-Sub is intended for multiplayer crew, unfortunately it can't fullfill all of the needs for a singleplayer campaign
For automatic undocking of the drone, if you want to, you could wire trigger_out on the periscope to a not component, to set_state on the docking hatch so it undocks the moment you start moving, and docks when you let go (and are near enough).