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
Crew status is the next big feature for the game. We are still working out how detailed this feature will become. While "Fog of War" is not something we want to entirely dispense with, crew death from radiation currently provides no notification.
We also agree that the "crafting" elements to repairs could be more up front. The number of parts required varies based on skill checks but this could definitely be more concise.
To be clear, we plan to update and expand Mars 2030 regularly throughout 2016 and beyond.
It's... Really not that hard to implement, and I honestly don't know *why* it wasn't implemented, because it's:-
1) Define keypress or mouse-loc for crew info (Possibly a "4" on the ship status screen?)
2) Show dem variables, using the same UI code as the ship info screen (Which is why I mentioned a 4 on the ship screen... Same area of code, too!)
3) ????
4) Profit!
It's... Genuinely baffling, because the variables are already there, and being called. As it is, you've called release, and... I've not seen that much improvement. Nmykita is quite correct in that there's very little feedback (What, precisely does an auto-nav virus do? It had no immediately visible effect. And no, don't tell me, because the *issue* is that the crew [game] knows, and I [the commander] don't), and that's a *big* issue in a game which is basically Oregon Trail (Risk management over a long journey.)
Since we pinned your post there have been 4 updates to Mars 2030. These were each critical to making the game run smoothly under every condition. Also an important step in rendering crew status accurately.
As it stands now, we seem to have eliminated all game breaking bugs. That is a big deal.
While we could add a basic crew status window pretty quickly, a better idea has come up that will take longer to implement. We think it will be worth the wait.
The lack of documentation, like what Auto-Nav viruses do and why failed repairs are un-fixable, is another important issue we will address.
For the record, a blinking light on your Auto-Nav means you are gradually going off course. It will also cause you to fail to enter the orbit of Mars if you happen to be close to the planet when it strikes.
GM-X