From WikiChip
Editing mirc/commands/signal
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 16: | Line 16: | ||
<syntaxhighlight lang="mirc">/signal mysignal Signal information!</syntaxhighlight> | <syntaxhighlight lang="mirc">/signal mysignal Signal information!</syntaxhighlight> | ||
− | Once you've executed this command, it will send a '''signal''' named ''mysignal'' to all scripts in your mIRC remotes. Any script files that have signal event listening for | + | Once you've executed this command, it will send a '''signal''' named ''mysignal'' to all scripts in your mIRC remotes. Any script files that have signal event listeners listening for the event will trigger, and perform whatever tasks they have been set to perform. |
+ | |||
+ | How do the other scripts listen for a signal event? That's a great question, which brings us to our next section regarding these listeners. | ||
<syntaxhighlight lang="mirc">ON *:SIGNAL:mysignal:echo -s rcvd: $signal : $1-</syntaxhighlight> | <syntaxhighlight lang="mirc">ON *:SIGNAL:mysignal:echo -s rcvd: $signal : $1-</syntaxhighlight> |