In 6.16, the help file states: Note: This identifier cannot be used in a script event. One way around this is to use a /timer to initiate an input request after the script ends.
However, I am able to put $? into a on-connect event, and it works.
Yeah it is usable (unless Im misunderstanding your intent). A perfect example of this is:
/test { if ($?="type your text here" == $null) { echo -s NULL } else { echo $! } }
No timer is needed and it DOES take the input from the $? and evaluates it in the $! I've given this to people to use for ops talkers (the kinds that DONT not send the message if it's blank) and it works for them fine
The help file states that "This identifier cannot be used in a script event." Both connect and text are script events. Yet it can be used in "on connect" event.
if you read the help carefully it states "after the script ends"... also if u check the help provided for the /timer command u' ll notice that timer 1 0 command executes the command "after the calling script ends"... so i quess that' s what u were looking for...