]>
Commit | Line | Data |
---|---|---|
ee41c3c6 G |
1 | ROLEPLAY consists of a number of similar commands |
2 | all of which send messages to channel under 'fake' | |
3 | nicknames. The user of the command can be identified | |
4 | by looking at the ident of the 'fake' user - it will | |
5 | always be the nickname of the person using the command, | |
a26bd774 G |
6 | and the host will always be npc.fakeuser.invalid. These |
7 | commands require the target channel to be set +E, and | |
8 | obey the same restrictions as regular PRIVMSG. | |
ee41c3c6 | 9 | |
a26bd774 G |
10 | Roleplay commands from normal users have the nick |
11 | underlined, to clearly show that the message is a | |
ee41c3c6 G |
12 | roleplay message rather than a normal one (with one |
13 | exception). Network operators are not subject to this | |
a26bd774 | 14 | restriction. |
ee41c3c6 G |
15 | |
16 | NPC <nick> <channel> :message | |
17 | Sends a standard roleplay message to #channel with the | |
18 | nick specified. | |
19 | ||
20 | NPCA <nick> <channel> :message | |
21 | Sends an ACTION to #channel with the nick and message | |
22 | specified. | |
23 | ||
24 | SCENE <channel> :message | |
25 | The same as NPC, except the message always originates | |
26 | from the nickname =Scene=, which will not be underlined | |
27 | like the other commands. |