Another thought...
There's indeed already enough of milspec packages in units.csv, even without writing every variant configurations of thrusters for every ship as a separate line. Which would still leave us with the abovementioned issue, avoiding which is the entire point of having unified parts - except instead of fore vs. aft parts we'd get "I have such-and-such thrusters for Llama, but not thrusters of the same size and power for Plowshare, oops".
The only way to handle it right now is to indeed use "matched thruster packages", but generate them procedurally (i.e. runtime whenever the base's manifest is first requested or changed) from available parts, and only for the specific ships - requesting player's and locally sold.
Not too hard, but this would eat resources.
Main Engine as Upgrade
-
- Elite Venturer
- Posts: 753
- Joined: Sat Apr 15, 2006 2:40 am
- Location: chthonic safety
Re: Main Engine as Upgrade
"Two Eyes Good, Eleven Eyes Better." -Michele Carter
-
- Elite
- Posts: 1363
- Joined: Sat Aug 04, 2007 3:42 pm
Re: Main Engine as Upgrade
Not anymore, everything milspec has been deleted. You will not see them in the next release.TBeholder wrote: There's indeed already enough of milspec packages in units.csv,