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

Feature Request: DropShip/JumpShip Repair/Maintenance Locations per SO #286

Open
mnmib1 opened this issue Dec 26, 2016 · 2 comments
Open
Labels
(RFE) Enhancement Requests for Enhancement, new features or implementations

Comments

@mnmib1
Copy link

mnmib1 commented Dec 26, 2016

DropShip/JumpShip locations for repair/maintenance per SO p. 172. After travelling to a contract, my DropShip spends most of it's time on the surface, but I can't use any of the existing modifiers (Transport Bay is 0, Maintenance Facility is -2, and Factory is -4). Adding the DropShip/JumpShip sites to the end of the 'Mech/Vehicle sites would not be that hard I believe.

On Planetary Surface (DropShip only) -1
Naval Repair Facilities (Unpressurized Yard) (see p. 334, TO) -3
Naval Repair Facilities (Pressurized Yard) (see p. 334, TO) -5

@purpledragon2
Copy link

If I understand this correctly, you mean specifically for the dropship or jumpship. IF so, then +1

@pheonixstorm
Copy link
Collaborator

You are also forgetting the time impact as well. I think a yard also cuts the times for repairs in half.

@neoancient neoancient added this to the Post-Stable 0.42 milestone Dec 27, 2016
@neoancient neoancient added the (RFE) Enhancement Requests for Enhancement, new features or implementations label Dec 27, 2016
@Dylan-M Dylan-M modified the milestones: Stable 0.44, Development 0.45 Feb 11, 2018
@sixlettervariables sixlettervariables removed this from the Development 0.45 milestone Oct 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(RFE) Enhancement Requests for Enhancement, new features or implementations
Projects
None yet
Development

No branches or pull requests

6 participants