The subforum name says "conventional", yet the posting of a comment thread without any updates to comment on says "unconventional". Which is to be believed?? 

  Looking forward to this one, Steve!

The difference for a PD STO and a normal STO is the fire control speed for the mount, so a weapon in a PD mount will shoot down missiles better. But like on ships and 37.5 cm laser firing every 30 seconds is a poor PD weapon even if it has a PD Mount as the weapon has a low rate of fire and poor speed, however a Twin Gauss turret would have its mount speed negated without the PD STO setting and is a good antimissile weapon but a dreadful anti-ship weapon. 
So like on ships different weapons serve different roles

Quote from: xenoscepter on April 17, 2024, 04:19:38 PM

--- Yes. 4 boat bays is more crew. 4x the crew requirement actually.

Huh?

4 boat bays = 4 x 3 = 12 crew
1 hangar deck = 12 crew

--- There is 20 crew set aside for the parasites crew.

1 Hangar Deck = 32 Crew
4 Boat Bays = 80 Crew for the Parasites alone.

EDIT: Nevermind! Boat Bays used to be 20 crew per bay. Now they're 5!

Suggestion: Improve Hangar Decks relative to Boat Bays to justify the 4k RP cost.

Quote from: skoormit on April 17, 2024, 09:50:25 AM

The research requires 4000 RP.
The Hangar Deck component has 4x the capacity of the Boat Bay, and has 4x the size, 4x the cost, 4x the crew, and 4x the HTK.
In other words, a Hangar Deck is almost entirely equivalent to 4 Boat Bays.

The only difference is using 4 components at 1 HTK each vs 1 component at 4 HTK.
I guess the latter could provide a terribly slight, terribly situational advantage.
But it hardly seems worth the effort to research.

Simple idea: reduce Hangar Deck crew requirement from 12 to 9.

And/or have Boat Bays and Hanger Decks all in the same tech, like what is done for Troop Transport Tech (including Boarding and Drop Techs)

Suggestion: Make it possible to override the interrupt for "Orders Completed" on a per-fleet basis.
Bonus: give the option to override permanently for this fleet, or just for the fleet's current order list.

Vague design thoughts:

On the Movement Orders tab, three radio buttons directly beneath the order list pane:
Stop Automated Turns on Completion (default)
No Stop (one-time)
No Stop (persistent)

In code, at fleet order list completion event, get selected radio value.
For the No Stop options, treat the event type as a non-interrupt.
For the one-time option, also reset the button value to default.

Split fleets should not preserve the setting (I think).

Bonus wrinkle:
Add the button setting to the Order Template object.