Skip to content
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

Ship Condition Update #87

Merged
merged 3 commits into from
Mar 10, 2024
Merged

Ship Condition Update #87

merged 3 commits into from
Mar 10, 2024

Conversation

thebrubaker
Copy link
Collaborator

@thebrubaker thebrubaker commented Mar 7, 2024

Overview

Taking ship actions such as navigating and extracting will now have a chance of a negative event occurring which degrades the condition of the frame, reactor or engine on a ship. Better ships will degrade at a lower rate than cheap ships (the goal is to think of drones as almost disposable, but your command ship should be maintained).

All of the values for event frequency, repair cost, and scrap earnings are ballparked, so things will need to be adjusted from player feedback. Some of the design goals include:

  • new players shouldn't need to worry too heavily about ship condition (so degraded performance is capped, allowing ships to continue to function non-optimally without becoming annoyingly slow or useless)
  • cheap ships such as drones should be disposable, probably at a rate of daily or every other day.
  • more expensive ships should be maintainable for weeks (so the entirety of the current reset)
  • repairing your ships early should be cheaper than repairing as a last resort
  • maintained ships should be less likely to take damage than poorly maintained ships
  • ships should degrade permanently with each repair, forcing an eventual scrapping
  • this feature should be more of a mid to late game optimization rather than something necessary to worry about early on
  • act as a significant credit sink in the game to remove credits and entice finding new shipyards

Negative Events

Currently only navigating and extracting have a chance of a negative event, but we will be adding most ship actions such as siphoning, docking, jumping, and warping into the logic. The traits of the waypoint involved currently increase the chances of a negative event (explosive gases for instance double the chances of damage to the ship)

Ship Damage

Ships take damage from negative events which lower the condition of the affected component. The lower the condition of the component, the more damage that will incur over time, so it is beneficial to keep your important ships maintained. Higher quality ships, such as the command ship, will take less damage from events than cheaper ships, such as drones. The condition of a ship ranges from 0 to 1, and will be restored to 1 when repaired. The integrity of the component will degrade with each repair, and eventually it will make more sense to scrap a ship than repair it.

Condition vs Integrity

Condition is repairable and is always restored to a value of 1. The integrity of the component is the long term wear and cannot be repaired. The integrity of the component is lowered every time you repair your ship.

Scrapping

Scrapping your ship will provide your agent with credits relative to the cost of the ship, the condition of the components, the mounts and modules attached, and the current price of ship parts / plating at the shipyard. You won't get a great price for your mounts and modules, so you will likely want to remove anything valuable. Cargo will be destroyed and not factored into the credits given.

Repairing

Repairing your ship costs credits and the cost of this repair will factor in the type of component, the condition of the component (more damaged components are more expensive to repair), and the price of ship parts and plating at the market.

Changes

  • adds endpoints for scrapping and repairing a ship (and GET requests for fetching an estimate)
  • updates frame / reactor / engine condition to a float between 0 and 1
  • adds an integrity value to frame / reactor / engine representing permanent wear
  • adds events property to extract / siphon / navigate endpoints
  • adds new event type for damage to ship condition

@thebrubaker thebrubaker merged commit c35fa54 into main Mar 10, 2024
1 check passed
@thebrubaker thebrubaker deleted the sa/ship-condition branch March 10, 2024 17:12
@@ -56,6 +59,8 @@
"required": [
"symbol",
"name",
"condition",
"performance",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps this was meant to be renamed to integrity

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Just pushed the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants