So, fleet sizes in hub missions are controlled by an enum that works off fractions of
FactionAPI.getApproximateMaxFPPerFleet(). I'm not sure how the figure is computed beyond the javadoc explanation, but it seems to work okay for "normal" factions in vanilla.
* Used to figure out how many fleet points raids/expeditions etc divide out for each "large" fleet.
* When going above 30 ships, fleets replace some smaller ships with larger ones. This FP limit is
* where that still produces fleets that aren't *too* top-heavy.
There's just one problem with this function: A mod can easily screw with the values without even meaning to, by adding new ships that allow a fleet to "compress" more effectively. Case in point: one mod (The Star Federation) adds an Omega capital for a one-off bounty, and this makes the return value of
getApproximateMaxFPPerFleet 5.4 times larger than what it is in vanilla (going from 576.58 to 3,126.49). This in turn led to a completely unrelated Omega fleet from my mod being about five times larger than it should have been under the circumstances it was generated, and about 2.5 times larger than what was ostensibly the maximum size specified in its fleet spawner.
Should hub missions have a more reliable sizing formula? (Why doesn't it let us just specify an arbitrary FP value directly, anyway?)
