New AI type : Flagship and Cargo

[arkahys]

flagship
Instead of set flagship by fleet window, set it by AI module.

• In AI window : Add a list to choose and display subordinated fleet(s) (or flagships, enabling hierarchy)
  
• in fleet window : add a list of flagships (as subfolder if enabling hierarchy).
  The actual fleet list becoming squadrons list.
  
• Order to squadrons and flagship could be differents :
  • remove formation orders and "recall to carrier" from squadrons order.

What's change :

• You can always give order to squadrons if flagship is lost.
• If you loose your flagship (commandant) squadron can't fly in formation.
• You need an AI in carrier to supervise drones between them.
  
• If hierarchy enabled, you can have more than one carrier by fleet, order the carrier (first row) or the carriers (2nd and more row) easily.

the penalty to have to set flagship manually allow formation and others restriction. But it could be overpass by setting subordinated in fleet window. I find this restriction interresting.

Cargo
I think could be pretty if an AI "cargo" type is added with following new AI window parameters :

• Set loading ship and set unloading ship who can be either a pickup point or a rail (un)load.
  "Carrier callback" order make :
  • Fully loaded cargo going to unloading ship
  • Fully empty cargo going to loading ship, if :
    • If set loading ship by pickup point, at least one rail load is free on the entity
    • If set by rail load, the rail load is free.
  • Take off :
    • If current carrier entity is set by pickup point, wait to be (manually) undocked to travel.
    • If current carrier entity is set by rail (un)load, undock and go.
• Add option Auto manage :
  • If the cargo is fully (un)loaded, set by :
    • Pickup point : if at least one rail unload is free on the targeted entity, the cargo "carrier callback"
    • Rail (un)load : if the rail is free on targeted entity, the cargo "carrier callback"
• Add option Force All/Load/Unload/Never,
  • all : for not loose the time travel between the two points.
  • Load/unload : cargo wait near (un)loading point, freeing rail. For the case of more than 1 cargo with 2 ship, no one will undock first because targeted rail is busy.
  • never : safety option to not have cargo undocked and waiting
• I explain "Rail load free", When cargo start order, it reserve to destination :
  • Pickup point : 1 rail load (just have to keep a total account, not reserve a specifique rail (un)load)
  • Rail (un)load : reserve this rail.

changes :

• Cargo fleets don't need to have a carrier as flagship.
• They can have more than one unloading or(exclusive) loading entity.