Add option to have ship schematics that only last one game

Hopefully easy to implement.

With the introduction of the ability to overwrite ship schematics, I was thinking that it would be nice to have the option of making the ship schematic you are putting together only exist for that one game instance, so that once you finish the game or delete the game save, it no longer exists. This will help prevent the ship designs folder from getting too cluttered up with a bunch of late game designs.

For example, I create a medium sized ship that I name reaper in game 1. This gets continuously modified and eventually has aaron defenses and nightmare torpedoes, etc.

When I start game 2 the reaper from the last game obviously can't be build right from the outset, so I create another ship I name Riptide which will be continuously modified in the same manner as Reaper.

This goes on for several games and before I know it, I have 20+ "junk" schematics in my designs folder that I will never use, and only serve to make that folder more messy.

6,444 views 4 replies
Reply #1 Top


For example, I create a medium sized ship that I name reaper in game 1. This gets continuously modified and eventually has aaron defenses and nightmare torpedoes, etc.

 

Not a bad idea.  What i do is just add a suffix to my ship name that i bump for each upgrade (x1,x2....)  Only the x1 shows up early and then as i research i get my x2,x3,....

when i get the tech for x2 i just obsolete x1 til next game

Reply #2 Top

Why don't you use some system with your ships?

If I build medium sized Reaper in a game it is Reaper M1. If I modify it later it becomes Reaper M2, and I don't overwrite Reaper M1.

I'm not saying I don't eventually have a clutter that needs to be cleaned up, but I don't have to create a new ship every game. My problem is making too many designs that are not much different than others, just because I like to design ships. 

Reply #3 Top

I think that is a great idea! :thumbsup:

Reply #4 Top

Why don't you use some system with your ships? If I build medium sized Reaper in a game it is Reaper M1. If I modify it later it becomes Reaper M2, and I don't overwrite Reaper M1.

I'm wondering if I perhaps have gone too far with this :) but I name my designs with a coding scheme that tells me the stuff it contains:

"Cruiser-EB2-B-MA2"

Which obviously :-) means "An escort cruiser (i.e. medium-size hull) with double second-tier (shield/PD/titanium) tech protection equipped with a single second-tier space drive (hyper drive plus) and armed with two first-tier (stinger) missile launchers." You can pack a lot into 7 letters...

When I get ion drive tech a new model will appear ("Cruiser-EB2-C-MA2") and so on with other techs that bring new devices or improvements that increase the amount of stuff you can fit into the hull. Obviously I don't have a ready design for every combination but if one is missing and I need it in the game I create it and it gets added to the library. Because the naming convention is based on the stuff the ships contain the designs can be reused. The idea is that eventually you have covered all those possibilities that *you* want and need and would have created in a game. It's like having a customized ship blueprint. Well, you still have to obsolete in the game ships that get replaced by better ones but you'd have to have done that anyway.