Why not? In the system I propose, they don't appear out of nowhere, they take over AI planes that are already there. The server can remark the time the mission started for anyone that doesn't want an airstart. That's all it is, an airstart for latecomers, but WITH the group.
SOW could have AI 10X better than il-2, and you know what, the AI would still suck compared to real pilots. You have a couple hours one night to fly a coop scheduled into your family time. You start the mission with 7 guys. Not ideal, but better than offline. A few minutes in, another coop lets out, and 16 guys become available, why no design a system that would allow—allow, not compel—mission designers and server hosts to have coop style play with players coming in over time.
If they new player chose to fly bombers or escorts they'd know they'd be getting into an airstart situation. If that was offensive to their sense of immersion, they'd either not have logged in to a mission in progress in the first place, or they could join the "scramble" squadron and TO later in the mission when the bombers show up on radar.
Choices for mission builders are a universal good.
There is no possible downside to considering "out of the box" systems for mission builders, mission builder MUST be lateral thinkers to make things work with the limited tools they are usually given. More options is ALWAYS better.
tater
|