-
-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lost hypedrive equipment and capability after landing (but not its mass) #4854
Comments
Check your cargo hold, when the BreakdownRepair module decides it has been too long past the warranty, it removes your drive and then adds a comparable amount of mass of rubbish to your cargo hold. It does this without telling you, so that's still an issue, but this is just a feature of the game that doesn't give very clear explanation. It should perhaps record when this happens and have a bit of flavor from the repair team saying "Your drive is nothing but scrap, clear it out and you can buy a new one." Or make a scrapped engine equipment that it costs money to remove. |
There should have been a message in the CommsLog, stating that the hyperdrive has been destroyed. |
Probbably triggered by #4910 I don't see any statement that there wasn't any comms message about this, as you will get a message in your comms:
Please (re-)open, if it can be confirmed that broken hyperdrive doesn't display the message above. |
Observed behaviour
I departed for a mission with class 3 hyperdrive fitted on. After the flight (which involved 2 jumps by the way) I landed and found that ship had no jump capability and no hyperdrive fitted on (both from ship information and equipment list).
The 20 tons however are still occupied, so there's no room to replace it.
Expected behaviour
Have my hyperdrive still there (or, if it exploded after the last jump, receive some kind of warning and have its space/mass freed).
Steps to reproduce
Open the first autosave, do the mission and land on Riggs Station in Urla, otherwise check directly the last autosave.
pioneer 20200404 (2e44d93) on Arch Linux x86_64
The text was updated successfully, but these errors were encountered: