Add the ability to create and remove client slots via script.

[Loophole]

Adding the ability to create and remove client slots via script would make it much simpler and less problematic to create dynamic campaign-style missions, where airbases and FARPs might change hands over time.  Instead of having to pre-set every possible client slot at every possible base, then muck about with mechanisms to selectively block slots, script could simply create and remove slots as required by the mission.

It would also simplify missions that need to cater to an unknown and variable number of players, with unknown preferences for specific airframes.  Some straight-forward scripting could give a Spectator a menu from which they could select airframe and starting point; script could then generate a slot on-demand, with whatever loadout and flightplan it deemed appropriate.

[cfrag]

More to the point, I would welcome if we had a callback in the mission context (not server) that a script could subscribe to in the form

function offerSlotToCallback(slot, player, unit)

where the script can return <true> (slot is offered), <false> (slot is not offered and does not even show up), or <nil> (where the next callback in the queue is presented with the question). 

This would not only allow solo missions to allow access to aircrafts based on mission progress, it would also allow to filter planes by type etc.

Quick shout-out to @Loophole who I'm sure is already aware of that: you can do this in MP, provided you install the correct scripts (mostly SSB).

Edited November 16, 2021 by cfrag

[Poulet67]

I second this request, however be advised this has been a wished for request probably since multi-player was ever a thing.

[Shrike88]

Just add this to the list of everything else that has collected dust for years.   Its 2022 and still cannot multiselect with click-drag.  That has been the most Basic of windows and OS functions since I can remember.