Semiconductor & Computer Engineering
(fixed format error) |
(fixed format error) |
||
| Line 34: | Line 34: | ||
* [[List of commands - mIRC|List of commands]] | * [[List of commands - mIRC|List of commands]] | ||
* [[List of identifiers - mIRC|List of identifiers]] | * [[List of identifiers - mIRC|List of identifiers]] | ||
| − | * [[ | + | * [[$me identifier - mIRC|$me]] |
| − | * [[ | + | * [[$nick identifier - mIRC|$nick]] |
* [[/amsg command - mIRC|/amsg]] | * [[/amsg command - mIRC|/amsg]] | ||
* [[/describe command - mIRC|/describe]] | * [[/describe command - mIRC|/describe]] | ||
Revision as of 01:44, 1 December 2013
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.
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
/action <message>
Switches
Parameters
- <message> - The message to be sent to the channel
Example
;Send an action message to the active window /action brings the cookie jar
Compatibility
Added: mIRC v2.1a
Added On: 28/02/1995
Note: Individual switches were not taken into consideration.