Is it possible to allow a fighter wing capability to be usable in boarding actions in the campaign? Think a wing of small boarding craft.
It's possible, but not simple. It involves providing a different version of the fleet interaction dialog plugin.
maybe try to make the ModPlugin check if it can find the mods you want, and then if it dose load an alternative mission_list.cvs?
kinda like the exterin
Spoiler
{
try
{
Global.getSettings().getScriptClassLoader().loadClass("data.scripts.world.ExerelinGen");
}
catch (ClassNotFoundException ex)
{
new XXXX().generate(Global.getSector());
}
}
well its an idea i dont really have time atm to try it out
Yeah, that approach should work.
Is it possible in dialogs to add options without replacing the whole dialog? For example, say I want to make a mod that adds an option on top of the base choices when interacting with a specific station. I know I can do that by copying the base files and replacing the whole interaction dialog plugin. However, if all I wanted was to add an option with some logic, that seems wasteful and also non-compatible with any other mod that wants to modify the same entity. (A 'supplemental' pickPriority that instead of generating a whole new dialog receives as an argument the existing dialog of the highest priority non-supplemental thing. Getting its optionSelected argument called might be a bit of an issue, depending on how things are structured under the hood...)
It's not currently possible, but I completely get what you're asking for/where you're coming from. Basically, this would require structuring the core implementation of the interaction plugin so that it itself could have plugins. That's potentially doable, but also kind of commits station interactions to that specific structure, and that's not something I'm comfortable doing.
I may end up doing just that later on down the line for sanity reasons - say, when expanding the fleet interaction dialog - perhaps with actual dialog - gets unmanageable without some kind of overarching structure. This kind of thing always works best when there's a vanilla use case to drive it, not just because it also directly contributes to dev progress but because it makes it much easier to get the design right.