Originally posted by karajorma
However if you've set the support ship to I can see that the SEXP might need some alterations. I've never played about with that setting but I assume that whether you get a centaur or scarab in that case depends on whether a vasudan or a terran makes the first call for support.
In that case the SEXP does need some amending becase as it is you can have terran ships launching vasudan support and there is no way to have both a terran and a vasudan capship in the mission and have each of them launch the correct kind of support ship.
That's the situation I'm more concerned with. For example, with default FS2 data (that is, FS2 tables, not Port, and no set-support-ship sexp), if you're playing say "Surrender, Bellassarius" (sp?), if you or your Terran wingman call for support first, then a Hygeia will jump in and service both Terran and Vasudan fighters that ask for rearm/repair, until said support ship is either destroyed or departs. If a Vasudan pilot is the next pilot to call for support, then a Nephthys will arrive and also service both Terran and Vasudan fighters until it is destroyed or departs. Now, lets take the same basic mission idea, and place it in FS1 era, using the Port. For the sake of argument, its the HoL attacking, in place of the NTF. Now, unless a set-support-ship sexp is used, the Hygeia and Nephthys will continue to arrive, which are incorrect for the period. So I want to have the Centaur called in if a support ship is not in the game field, and a Terran calls for support, and I want a Scarab to be called in if a Vasudan calls for support under the same conditions. The set-support-ship sexp cannot do this right now. You can specify the Centaur OR the Scarab, but not both. In fact, the only way to get this effect right now, is to gut the FS2 support ships from the tables and run without the sexp. Without resorting to this, the solution is either to include a species line in the sexp and allow for this sexp to be used as many times in mission as required for the number of friendly species, or make the sexp scaleable, like the send-message-list sexp, which can be extended for as many messages as are required for a mission, except for species-specific support ship entries. A third option would be to bypass sexps all together, and have a section in the mission specs so you can select which species have which support ships, how many, where they come from, etc.
I hope this clears up the question of where I see a failing in the current sexp, and how I think it should be handled.
Later!