I think they can, but not sure...
Say I have a script I want another script to load, can my script trigger off its get user input to answer or work the menus if I set it right?

There are a couple of ways to make 2 scripts communicate, none of them great.

Off the top of my head...
1. Create text triggers in both scripts, and use the SubSpace radio to send/receive input/output between them.
2. Use a file on your harddrive. Have script one create a question file, and have script two create an answer file. Each script checks for the existence of the file every second, and deletes it when finished with it.
3. Use setSectorParameter/getSectorParameter or saveVar/loadVar to pass data locally, using a similar method as outlined above.
4. Finally, you can have TWX Proxy connect to another instance of TWX Proxy.

+EP+

Ok I have 2 questions:

1st Why would you want to even do that? Just have the script trigger within itself and pass information through variables under different labels.

2nd How do you get two (or more) copies of TWX to load at the same time on the same machine? TWX seems to internally use the machines game port and once it is in use it locks out all other attempts to further utilize it. As far as I can figure out it only uses port-23. I have looked before and was unable to locate any config files to alter or change TWX so as to direct access to another port.

Go to setup|program|Listen For Connections on Port

With 2.03, regardless of what you do, if port 23 is in use, it will give you an error on startup. However, it will work just fine so long as you really do have it on another port. Personally, I keep mine in the high port range so there are no conflicts with other things.

Ohh, it gets passed on by the Windows config. Laff, I never even thought of that. [V] Thanks Harley!

quote:Originally posted by RexxCrow


1st Why would you want to even do that? Just have the script trigger within itself and pass information through variables under different labels.....



A controller script comes to mind when you need two scripts to communicate. The controller script fires another script and then the "child" communicates back through SS channels as EP indicated as an option. When the correct SS message comes through, the controller takes over and we finish what we are doing. If the wrong message (error) comes across or the controller delays out, then the controller has to fix whatever problem occured (within reason).

SS works well when there are actions to be made on the fly but can spam your corpies and could be susceptible to spoofing.

I use saveVar and loadVar for things that are basically static.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

ok guys thanks, I experiment some with it today after work.
As far as Port 23, I've had 3 TWX going at once, port 23, port 24, and port 26
Port 25 seems to used by something else, so it won't work.

Port 25 is generally an outgoing email port