Semiconductor & Computer Engineering
m (bot: sort-key added to category) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{mirc title|/action Command}} |
| − | The action command is used to send an action message to the active window. Since it does not take a target parameter, that command is the kind of command that is mostly used manually, it cannot be used within events that are triggered by anything other than the user directly from a given channel. For example: it can be used within the on input or hotlink events but not within the on text. To be able to generate an action message from any event to any window, consider using the /describe command instead. | + | The '''/action''' command is now deprecated in favour of the identical '''/me''' command and is used to send an action message to the active window. Since it does not take a target parameter, that command is the kind of command that is mostly used manually, it cannot be used within events that are triggered by anything other than the user directly from a given channel. For example: it can be used within the on input or hotlink events but not within the on text. To be able to generate an action message from any event to any window, consider using the /describe command instead. |
| − | |||
An action message is simply a regular PRIVMSG that follows a client-dependent format - usually different to that of a normal message. The raw format for an action message is: | An action message is simply a regular PRIVMSG that follows a client-dependent format - usually different to that of a normal message. The raw format for an action message is: | ||
Latest revision as of 07:47, 9 July 2017
The /action command is now deprecated in favour of the identical /me command and is used to send an action message to the active window. Since it does not take a target parameter, that command is the kind of command that is mostly used manually, it cannot be used within events that are triggered by anything other than the user directly from a given channel. For example: it can be used within the on input or hotlink events but not within the on text. To be able to generate an action message from any event to any window, consider using the /describe command instead.
An action message is simply a regular PRIVMSG that follows a client-dependent format - usually different to that of a normal message. The raw format for an action message is:
//raw PRIVMSG $active $+(:, $chr(1), ACTION) [message] $+ $chr(1)
Where [message] is the actual message to be displayed.
Synopsis[edit]
/action <message>
Switches[edit]
None
Parameters[edit]
- <message> - The message to be sent to the channel.
Example[edit]
;Send an action message to the active window /action brings the cookie jar
Compatibility[edit]
Added: mIRC v2.1a
Added on: 28 Feb 1995
Note: Unless otherwise stated, this was the date of original functionality.
Further enhancements may have been made in later versions.
See also[edit]