I thought about filing this as a bug, but concluded
that it was a pretty good candidate for the phrase
"it's not a bug, it's a feature." Still, it is a
feature that can be improved. :-) Here's the
feature-formerly-known-as-a-bug.
When you first tell stats in a player command file to
build let's say a Golem with lasers, run the command,
then change your mind to building a Golem with Heavy
Phasers or say an SSD with Blasters, and run the
command again, you end up with more hulls and weapons
etcetera then you probably want.
I think it would be best to do the following:
- check if a base has a command file build order
- check if that base is already building a ship
- if yes, cancel that build order, including all newly
build components
- build the new ship.
Hmmm, come to think of it, the problem may be knowing
which parts of the previous ship build order have been
ordered this turn and which were already in the
starbase inventory at the beginning of the turn. Simply
removing those parts would cause you to lose those
parts and be the equivalent of a phone call to the Tim
Continuum.
Logged In: YES
user_id=670686
The last paragraph is correctly voicing a concern. These type
s of things can only be done when we also read the *.dis files
which we don't do right now.