Semiconductor & Computer Engineering
(→Example) |
(→See also) |
||
| Line 34: | Line 34: | ||
* [[/ame command - mIRC|/ame]] | * [[/ame command - mIRC|/ame]] | ||
* [[/amsg command - mIRC|/amsg]] | * [[/amsg command - mIRC|/amsg]] | ||
| + | * [[/action command - mIRC|/action]] | ||
* [[/describe command - mIRC|/describe]] | * [[/describe command - mIRC|/describe]] | ||
* [[/msg command - mIRC|/msg]] | * [[/msg command - mIRC|/msg]] | ||
Revision as of 14:55, 14 March 2014
The /me command is used to send an action message to the active window. Because this command does not take a target parameter, 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
/me <message>
Switches
None
Parameters
- <message> - The message to be sent to the channel
Example
;Send an action message to the active window /me brings the cookie jar
Compatibility
Added: mIRC v2.1a
Added On: 28/02/95
Note: Individual switches were not taken into consideration.