Hey, Builder, I'm posting my response to your PM here, because I think if others read my responses the way you read them, I think I need to publicly clarify.
My apologies if I seemed intentionally vague or obnoxious. I honestly thought my responses were answering your questions.
I think I underestimated how much you knew about jobs.txt. That's my fault.
This supply script is a single set of instructions. These instructions can be run on any ship. The thing is, my military supply script here doesn't actually create the ships, the job engine does. Once the job engine creates the ship, the military supply script is then run on it. It's the job engine that runs my script on this ship. So there's nothing I can do to make Yaki, Xenon, Goner, or Klingon supply ships; that's not what this script does. All it does is tells the Xenon, Yaki, Goner or Klingon ship to supply its own race's missile boats; it cannot create those ships.
The one script runs on any missile supplier, regardless of race. There is not an Argon supply script, a Boron supply script, or a Vulcan supply script. It's one script. This script functions differently depending on what race owns the ship.
So now you probably understand that in order to do what you've requested, one is required to edit the jobs.txt. That is something I can do, but won't be of use to anyone. Jobs is not a modular thing; it's all or nothing. From what I gather, most of you are using the xtra jobs pack. So he (she?) is going to have to edit that, and just include a reference to my script.
For future reference, if you think I'm being a dick, call me out publicly. The record will probably show that I'm not here to pick fights with anyone. And while there's more than a handful of WAAaay over-sensitive forum users in this particular scripts and modding forum, I don't count myself among them; if you call me a douche pocket, I'll probably see the light, buy you a beer, and explain myself a little clearer. If someone is bitter at something we say, it's probably our own fault.
