[Question] Carrier Module Fighter Craft

Yes, you are correct.

Thats awsome, means my idea can bare fruit

Whats the idea!?

To add a starbase module that grants the starbase the ability to launch defence platforms instead.

ATM though its not looking good. As I can not see how or where to make a new Stat Type effect. StatTypeDisplayDefs.xml just "seems" to be the place, but you can not define what your Stat Type does or does not do. I am guessing it is just a link file for some dll to reference.

I assume that you're trying to make use of fighters for the defense platforms and do not want to use AssaultFightersCap, InterceptorFightersCap, or GuardianFightersCap because you don't want to lose the standard Assault Fighters, Interceptors, or Guardian Drones? If so, I have good news for you: there's an unused (at least, in the base game; some mods may make use of it) fighter type - Escort Fighters, which can be granted to a starbase module or ship component using an EffectType of EscortFightersCap. You'll need to create a blueprint for the Escort Fighters and define at least one ship class for them, as well as making the InitialEscortFighter lines in the *ShipStyleSetDefs reference the appropriate class rather than the *AssaultFighter as they do now, but you don't need to create a new stat type (which is not currently supported, as far as I am aware).

Further investigation has bared a bit of info, there are schema files for StatTypes and ModifierEffectTypes but no xml files linked to these schema. I guess modding these is locked away for now, or forever.

While looking over ModifierEffectTypes.xsd I did come across a away to Grant ships, sveral ways tbh, but this option would limit the granted "ships" to a one time deal, which is not realy what I want.

All this has lead me to the option of just replacing an existing fighter type to do what I wish. Which again is not ideal.
 

At present, it's more or less the case that if something cannot be done with the things defined in the schema files that come with the game, you cannot do it. That being said, there are things defined in the schema files that are currently unused - for example, a fourth (and more importantly, functional but unused) type of fighter.

As I wrote above, most likely while you were typing this, create an EscortFighterBlueprint, define at least one class which references the EscortFighterBlueprint, and have the InitialEscortFighter lines in *ShipSetStyleDefs reference your new Escort Fighter class(es). There is nothing in the unmodded game which makes use of Escort Fighters; even if there were, it'd be redundant because at present the InitialEscortFighter for every faction is the same as the faction's InitialAssaultFighter, so even if there is an instance where Escort Fighters are actually used in the unmodded game (and I'm almost positive that nothing uses them anymore) you won't actually be losing any diversity. Once you've defined your Escort Fighters, you can add them to a ship component or starbase module using EscortFightersCap.

If so, I have good news for you: there's an unused (at least, in the base game; some mods may make use of it) fighter type - Escort Fighters, which can be granted to a starbase module or ship component using an EffectType of EscortFightersCap. You'll need to create a blueprint for the Escort Fighters and define at least one ship class for them, as well as making the InitialEscortFighter lines in the *ShipStyleSetDerfs reference the appropriate class rather than the *AssaultFighter as they do now, but you don't need to create a new stat type (which is not currently supported, as far as I am aware).

I was just looking at that. That is what I am going to "hopefully" replace. But I see a reference to it in ComponentClassDefs.xml, does this not mean its buildable in game? Or is it just a fake entry?

 Edit

Okay we are posting at the same time LOL! I get what u say, thanks!

Look in ShipComponentDefs, StarbaseModuleDefs, and anywhere else that might possibly make use of EscortFightersCap. Nothing uses it anymore. Moreover, all of the base game factions have the same fighter class for their InitialAssaultFighter and InitialEscortFighter, which means that even if there is something that does use escort fighters, you can just switch that to use assault fighters and not lose anything at all.

So, they are used still By AssaultCarrierBlueprint, but as you stated already they just use the same ship as Assault Fighters, so I can edit xml's and point the blueprints/components to fit my needs, just requries a bit more work than originaly thought, something I can live with

Seems to work, game boots up and loads a new game. Module shows up in the Tech Tree. Not built one  on a starbase yet to see the results, still got a few bits and pieces i want to do before i can get into a proper test game. I did make a screen shot though:-

Screenshot

Only issue I can see so far is, it is not picking up my custom Icon and displays the generic Icon still.

Edit.

Ah ha i urm Kind forgot to chnage the Icon text lol.