Nod. Ck's doesn't I don't think.

But that's a perfect example of what I mean. Aliens are a common enough problem that most
ppl have worked that out. But there are other problems that aren't so common.

What if you're in a game where people are mowing 2 sectors in a row, then twarping off? If you
had the source you could modify it to only shoot on the first, hoping for a pdrop into their 2nd.
Or if your ping is really good you could focus on just the 2nd one, hoping to hit them on the
twarp out. You have options, and which one you go with will depend on the situation.

There's a hundred little problems you can only solve by rolling your own code.

Wow.....thanks Sing, I think I had that exact issue with someone. Thanks for the idea....

Yes yes, I completely agree... but it sounds like you're trying to convince me to code twx, and I don't need any convincing - You and Vid both seemed to conclude I wasn't intending to code twx at all, but just use zoc. That's not at all what I intend, and have already done a lot of twx coding.

I'm just saying that it's quicker to use someone else's script when I haven't got around to coding my own. I don't have a huge library of my own scripts built up yet, and it takes time to code them. There is so much coding to do that each time I sit down I hardly know where to start. Until I have my own twx scripts polished, which I am in the process of doing but will take a long time, I will use the best of what's available.

Anwyays.... I really appreciate the advice... and I do understand some of what you are getting at. Obviously it's far preferable to have my own scripts.

Nah. Perhaps we all get a little overzealous a bit on this, it just seemed a very round-a-bout way of doing something simple. There's a little cruftwarrior in all of us I think.

:controller_script
settexttrigger wow :wow "Deployed Fighters Report Sector"
pause
:wow
Processin 1 "START MY FOTON SCRIPT NOW"
halt

:Controlled_Script
settexttrigger wow :wow "START MY FOTON SCRIPT NOW"
pause
:wow
load dny_photon.ts


this is the only way (that I have found) to pass a trigger execution of from one script to another without using Comm.