philippelh/bitchx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial import of the ircii-pana-1.1-final source tree.

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/bitchx/code/tags/ircii-pana-1.1-final@1 13b04d17-f746-0410-82c6-800466cd88b0
This commit is contained in:
Kevin Easton
2008-02-25 09:25:32 +00:00
commit 28febcfea9
1429 changed files with 250653 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
bitchx-docs/1_General/1_General Normal file
View File

@@ -0,0 +1,12 @@
Section 1: General-Purpose Commands 
This section contains some of the most basic commands for EPIC. If you are
not at least familiar with these, you probably won't get very far on irc.
Included here are commands for joining and leaving channels, connecting to
and disconnecting from irc servers, changing your nickname, sending private
messages to other people, and countless others.
Please read this section (and the next one) carefully. Most of the problems
encountered by new users can be solved here.

12
bitchx-docs/1_General/4op Normal file
View File

@@ -0,0 +1,12 @@
Synopsis:
4op [nick|nick1 nick2 nick3 nick4]
Description:
This command will op nick 4 times or 4 nicks. Not generally useful,
as it's mostly a vanity command.
Examples:
To op a single nick 4 times
/4op nick

14
bitchx-docs/1_General/about Normal file
View File

@@ -0,0 +1,14 @@
Synopsis:
about
Description:
This command displays the about message that is built-in too the client.
Options:
none
Examples:
To display the about msg on your screen:
/about

21
bitchx-docs/1_General/addforward Normal file
View File

@@ -0,0 +1,21 @@
Synopsis:
addforward [<nick|#chan>]
Description:
This command will forward all msgs sent to the client onto either another
nick or another channel. Sometimes this is useful whilst netsexing or
while the client is on two differant networks and in a screened state.
Examples:
To forward to a nick:
/addforward nick
To forward to a channel:
/addforward #channel
See Also:
unforward(1) noforward(1)
Restrictions:
This could possibly get you in trouble in some cases. Use with caution.

21
bitchx-docs/1_General/addidle Normal file
View File

@@ -0,0 +1,21 @@
Synopsis:
addidle [#chan seconds]
Description:
This command will add idle checking to a channel. It will kick
MAX_IDLEKICKS nicks at a time after the number of seconds specified
for the idle time has elapsed. This can cause problems if mass kick
protection is active on the channel. Various things will make the client
think that another nick is not idle, publics, notices and ctcps for
example will reset the timer for the nick doing them. You will not
kick yourself, another op or a voiced client as long as the channel set
for KICK_OPS is off. Also if the nick is on your userlist then you will
not kick them
Examples:
To add idle checking to a channel:
/addidle #channel 600
See Also:
set MAX_IDLEKICKS set KICK_OPS cset KICK_OPS unidle(1)

11
bitchx-docs/1_General/addlamenick Normal file
View File

@@ -0,0 +1,11 @@
Synopsis:
addlamenick <nick>
Description:
ADDLAMENICK adds a nickname to your lamenick list. It will be matched
against the nick joining your channel and if you opped, they will be
banned by nick.
See Also:
unlamenick(1) lamenicklist(1)

17
bitchx-docs/1_General/addnoflood Normal file
View File

@@ -0,0 +1,17 @@
Synopsis:
addnoflood [<nick>]
Description:
This command will add a nick to your NO FLOOD list. This list will bypass
the client flood protection, making it good for chanserv's, nickserv's
and operserv's as well as friends, who you don't mind allowing flooding.
Examples:
To add a nick:
/addnoflood nick
To show no flood list:
/addnoflood
See Also:

25
bitchx-docs/1_General/addshit Normal file
View File

@@ -0,0 +1,25 @@
Synopsis:
addshit <nick|nick!user@hostname> <channel|*> <levels> [reason]
Description:
Adds <nick|nick!user@hostname> on <channel|*> with [shitlist level] and
optional [reason].
<channel> can have more than one via the use of of "," or * for all.
[shitlevels]:
1 - Deop user at all times
2 - Kick user when they join the channel
3 - Ban/Kick user when they join the channel
4 - Ban user at all times
5 - Perm ignore ALL from user
Examples:
/addshit panasync #bitchx 3 go away
would add panasync on the channel #bitchx only for a ban/kick on join.
/addshit panasync #bitchx,#mpeg3 5 go away
would add panasync on the channels #bitchx and #mpeg3.
See Also:
shitlist(1); unshit(1);

53
bitchx-docs/1_General/adduser Normal file
View File

@@ -0,0 +1,53 @@
Synopsis:
adduser [-ppp] <nick|nick!user@hostname> <channel|*> <levels> [password]
Description:
Adds <nick|nick!user@hostname> on <channel|*> with [userlevels] and
optional [password]. If a password is specified, it is encrypted in the
saved userlist.
<channel> can have more than one via the use of of ","
Use -ppp to add *domain.com hosts
[userlevels]: (available to the registered user)
BAN - Bans offender who bans a protected user
BOT - Creates a bot entry in userlist(/addbot replacement)
DCC - Allows a users dcc to auto-get regardless of whether
/set dcc_autoget is Off or On
DEOP - Deops offender who deops a protected user
FLOOD - AllowS Flood checking to be turned off on a user
INVITE - Allows a user to invite themself to a channel your in via
CTCP
I_OPS - Allows a user to be instantly opped/voiced upon joining a
channel they are protected in (NOT RECOMMENDED).
You still require OPS or VOICE with this modifier.
KICK - Kicks offender who bans/kicks protected user
KILL - <undefined as of yet>
OPS - Allows a user to be opped via CTCP/deleyed ops
PBAN - When a user is banned from a channel they are protected on,
they are automatically un-banned
PINVITE - When a user is kicked from a channel they are protected on,
they are automatically re-invited back
REOP - When a user is deopped from a channel they are protected on,
they are automatically re-opped
UNBAN - Allows a user to remotely unban his/herself via CTCP
VOICE - Auto-voice on join
FRIEND - Combination of: VOICE,OPS,UNBAN,INVITE
MASTER - Combination of: VOICE,OPS,BAN,UNBAN,INVITE,DCC,FLOOD
OWNER - Combination of: MASTER,KILL,DIE,BOT
More than one level is possible, you can combine them with a ",".
See UNUSER on how to remove <nick> from userlist
CTCP to understand valid CTCP commands which can be sent to gain
privileges
Examples:
/adduser panasync #bitchx friend,i_ops
would add panasync on the channel #bitchx only for instant ops on join
(if /cset aop on for that channel), and allow him too unban and invite
himself. Commands are given using /ctcp.
/adduser panasync #bitchx,#mpeg3 friend,i_ops password
would add panasync on the channels #bitchx and #mpeg3. He would need to
specify a password in order to become opped.

17
bitchx-docs/1_General/addword Normal file
View File

@@ -0,0 +1,17 @@
Synopsis:
addword [<#chan>|*] word(s)
Description:
Adds word(s) to your banned word list. Anyone saying this word(s) in the
channel will be kicked.
Examples:
/addword * too lame
/addword #channel sexx
/addword #channel this*is*lame
See Also:
showword(1) unwordkick(1)
Restrictions:
This could possibly get you in trouble in some cases. Use with caution.

16
bitchx-docs/1_General/ajoin Normal file
View File

@@ -0,0 +1,16 @@
Synopsis:
ajoin <channel> [key]
Description:
AJOIN will join the channel every time you connect to a server. These are
saved using SAVE command.
Examples:
/ajoin #bitchx
/ajoin #bitchx bitches
See Also:
unajoin(1); ajoinlist(1); JOIN_NEW_WINDOW(5);

14
bitchx-docs/1_General/ajoinlist Normal file
View File

@@ -0,0 +1,14 @@
Synopsis:
ajoinlist
Description:
AJOINLIST will display your current ajoin channels.
Examples:
/ajoinlist
See Also:
unajoin(1); ajoin(1); JOIN_NEW_WINDOW(5);

51
bitchx-docs/1_General/away Normal file
View File

@@ -0,0 +1,51 @@
Synopsis:
away [[<options>] <away message>]
Description:
This command marks you as being "away". It is used to tell people that
you currently aren't paying attention to your screen. You might use it
if you are taking a nap, in the shower, getting some food, or otherwise
just aren't there at the moment. When you mark yourself as away, your
status bar will show the value of STATUS_AWAY to reflect this; this is
"(Away)" by default.
Anyone who does a WHOIS on your nickname will see that you are away, as
well as your away message. Anyone doing a WHO that returns information
about you will also see that you're gone. By default, if someone sends
you a MSG while you are away, your client will beep. You can turn this
off by setting BEEP_WHEN_AWAY to OFF.
If you send a MSG to someone who is away, you will automatically be
notified of this. By default, you will only receive this notification
once. If you wish to see it every time (to tell when a person is no
longer marked away, for instance), change SHOW_AWAY_ONCE to OFF.
You can remove your away status by using AWAY with no arguments.
Options:
-all send the away message to all servers you are on
-one send away message to only the current server (default)
Examples:
To mark yourself away:
/away I'm not here right now, I'll be back soon
To mark yourself away on all servers:
/away -all I'm in the shower, back in 10 minutes
To remove your away status:
/away
See Also:
load(5) away; set(4) beep_when_away, show_away_once, status_away;
who(2); whois(2)
Restrictions:
AWAY status (and messages) is only through the network once,
when it is first set. The implication of this is that, if the AWAY was
set during a netsplit, when the netsplit heals, the reconnecting servers
will not be aware of the AWAY status. Thus, anyone on those servers
using WHO or WHOIS will not know you are away. In addition, servers
will impose a limit to the length of the AWAY message; this is usually
80 characters; test it on your server to be certain.

14
bitchx-docs/1_General/awaylog Normal file
View File

@@ -0,0 +1,14 @@
Synopsis:
awaylog [<level>]
Description:
AWAYLOG allows you to specify what type of msgs will be logged while
your away.
Examples:
/awaylog -msg
See Also:
set(4) lastlog, lastlog_level, log, logfile; window(4) lastlog_level,
log, logfile

16
bitchx-docs/1_General/awaymsg Normal file
View File

@@ -0,0 +1,16 @@
Synopsis:
awaymsg [<msg>]
Description:
AWAYMSG allows you to specify the message used when you auto set away.
Examples:
To set your away msg:
/awaymsg we are away now.
To remove your away msg:
/awaymsg
See Also:
away(1); back(1)

14
bitchx-docs/1_General/b Normal file
View File

@@ -0,0 +1,14 @@
Synopsis:
ban [<channel> <pattern> <nick>]
Description:
BAN will attempt to ban either a nick or a anyone matching the specified
pattern. If the nick is not found in the channel, the server will be
queryed for a match.
Examples:
/ban fudd
/ban #warez1 fizzle_b
/ban #bitchx *idt*
See Also:

27
bitchx-docs/1_General/back Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
back <back message>]
Description:
This command marks you as being "back". It is used to tell people that
you currently back paying attention to your screen. You might use it
after you have taken a nap, a shower, gotten some food. When you mark
yourself as back, your status bar will show remove the value of
STATUS_AWAY to reflect this; this is "(Away)" by default.
Examples:
To mark yourself away:
/back I'm here right now
See Also:
load(5) away; set(4) beep_when_away, show_away_once, status_away,
send_away_msg; who(2); whois(2)
Restrictions:
AWAY status (and messages) is only through the network once,
when it is first set. The implication of this is that, if the AWAY was
set during a netsplit, when the netsplit heals, the reconnecting servers
will not be aware of the AWAY status. Thus, anyone on those servers
using WHO or WHOIS will not know you are away. In addition, servers
will impose a limit to the length of the AWAY message; this is usually
80 characters; test it on your server to be certain.

14
bitchx-docs/1_General/ban Normal file
View File

@@ -0,0 +1,14 @@
Synopsis:
ban [<channel> <pattern> <nick>]
Description:
BAN will attempt to ban either a nick or a anyone matching the specified
pattern. If the nick is not found in the channel, the server will be
queryed for a match.
Examples:
/ban fudd
/ban #warez1 fizzle_b
/ban #bitchx *idt*
See Also:

12
bitchx-docs/1_General/banstat Normal file
View File

@@ -0,0 +1,12 @@
Synopsis:
banstat [<channel>] [<match>]
Description:
BANSTAT will display the bans on the current channel or the specified
channel. A pattern to match can also be specified.
Examples:
/banstat #bitchx
See Also:
on bans_header on bans_list on bans_footer

11
bitchx-docs/1_General/bantype Normal file
View File

@@ -0,0 +1,11 @@
Synopsis:
bantype [<N|B|H|D|S|I>]
Description:
BANTYPE will set the default type of ban to use when you various ban
commands and when banning someone automatically.
Examples:
/bantype s
See Also:

13
bitchx-docs/1_General/banwords Normal file
View File

@@ -0,0 +1,13 @@
Synopsis:
banwords <channel|*> word(s)
Description:
BANWORDS add a banned word or words to your banned word list for a
channel.
Examples:
/banwords #bitchx sexxy
See Also:
addword(1) unwordkick(1) wordlist(1) showwordkick(1)

34
bitchx-docs/1_General/bk Normal file
View File

@@ -0,0 +1,34 @@
Synopsis:
bk *|<channel> <nickname> [<reason for kick>]
Description:
This command "bans" and "kicks" the specified user off of the specified
channel. It is typically used to remove troublemakers, flooders, or
people otherwise making a nuisance of themselves on the channel.
The reason for the kick is randomly taken from BitchX.reasons if not
given.
Examples:
To kick foobar out of channel #blah:
/bk #blah foobar Go away!
To kick foobar out of your current channel:
/bk foobar I said go away!!
See Also:
ignore(1); load(5) autokick; mode(1); on(5) kick
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.
Other Notes:
It is important to note that channel operators are the single absolute
authority on their channels, and as such they may kick out anyone they
choose for any reason (or no reason at all). Keep in mind, however,
that doing so for such petty reasons won't make you very popular with
other users, and it isn't unheard of for users to abusively avenge the
kick. If someone is annoying you, using IGNORE (or SILENCE, if
available) is a better solution. KICK should be reserved for users who
are harassing your channel or its members in general.

34
bitchx-docs/1_General/bki Normal file
View File

@@ -0,0 +1,34 @@
Synopsis:
bki *|<channel> <nickname> [<reason for kick>]
Description:
This command "bans/kicks/ignores" the specified user off of the specified
channel. It is typically used to remove troublemakers, flooders, or
people otherwise making a nuisance of themselves on the channel.
The reason for the kick is randomly taken from BitchX.reasons if not
given.
Examples:
To kick foobar out of channel #blah:
/bki #blah foobar Go away!
To kick foobar out of your current channel:
/bki foobar I said go away!!
See Also:
ignore(1); load(5) autokick; mode(1); on(5) kick
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.
Other Notes:
It is important to note that channel operators are the single absolute
authority on their channels, and as such they may kick out anyone they
choose for any reason (or no reason at all). Keep in mind, however,
that doing so for such petty reasons won't make you very popular with
other users, and it isn't unheard of for users to abusively avenge the
kick. If someone is annoying you, using IGNORE (or SILENCE, if
available) is a better solution. KICK should be reserved for users who
are harassing your channel or its members in general.

20
bitchx-docs/1_General/bye Normal file
View File

@@ -0,0 +1,20 @@
Synopsis:
quit [<quit message>]
Description:
This ends your irc session. If a quit message is supplied, it will
be displayed to anyone else on any channel you were on before
quitting. If one isn't specified, the client's version string is
used.
Examples:
To quit from irc with a message:
/quit I'll be back soon!
Aliases:
BYE, EXIT and SIGNOFF are identical in operation to QUIT.
See Also:
bind(4) quit_irc; disconnect(1); on(5) channel_signoff, quit,
signoff

67
bitchx-docs/1_General/channel Normal file
View File

@@ -0,0 +1,67 @@
Synopsis:
join [-invite|<channel list> [<key>]]
Description:
JOIN lets you join a new channel. If you are on multiple channels,
the specified channel will become the current one. If you do not
specify a channel (or channels) to join, your client will display
your current channels, along with their respective modes and users,
and which server you are on the channel from.
You may join more than channel at a time with a single JOIN command
by separating the channels with commas. If a key (channel mode +k)
is set on a channel you wish to join, you must specify that key in
the JOIN command to be able to join the channel.
You can create a new channel simply by joining a channel that does
not exist. Channel names begin with a '#', a '&' (&channels are local
to your server), or a '+' (modeless channels, not available everywhere)
and following that may consist of any character except SPACE, BELL, NUL,
CR, LF, or comma (','). Channel names may be up to 200 characters in
length. Additionally, a channel may be restricted to only users from
certain hosts, by adding a hostmask to the end of the channel name,
separated with a ':' (this is not supported everywhere).
Options:
-invite makes you join the last channel to which you were INVITEd
Examples:
To join channel #blah (or create it if it does not exist):
/join #blah
To join channel #blah that has the key "foobar":
/join #blah foobar
To join more than one channel at once:
/join #foo,#bar,&blah
To join a channel that only German users may join:
/join #blah:*.de
To join channel #blah if you have been invited to it (either will
work, although the first is better, since channel names may contain
characters that your terminal can't display):
/join -invite
/join #blah
Aliases:
CHANNEL is identical in operation to JOIN.
See Also:
bind(4) switch_channels; invite(1); mode(1); on(5) join; set(4) novice;
window(4) channel
Restrictions:
The ability to join a channel can be restricted by the channel's modes.
If mode +k is set, you must specify the channel's key to join. If mode
+i is set, you must first be INVITEd. If mode +l is set, and the limit
has been reached, you cannot join. If a ban (mode +b) has been set
that matches your nick!user@host pattern, you cannot join. See MODE
for more information.
Other Notes:
The ircII client provides a NOVICE mode mechanism. When turned on, the
client will not allow you to join more than one channel at once. If
you are on a channel and try to join another, it will first make you
leave the first channel.

20
bitchx-docs/1_General/chat Normal file
View File

@@ -0,0 +1,20 @@
Synopsis:
chat <nick>
Description:
CHAT initiates a direct connection to another client, allowing
the users to chat without needing to pass messages through the irc
network. This is a very secure way of communicating on irc, not
to mention that it is generally faster than sending messages across
the irc network.
To send a message across the DCC CHAT connection, use MSG as you
normally would, but prefix the nickname with a "=". Additionally,
CTCP commands can be sent across a DCC CHAT connection (allowing you
to initiate a DCC SEND, for instance), if the remote client is also an
EPIC3 (or compatible) client. See the appropriate help files for more
information.
See Also:
ctcp(1); msg(1); on(5) dcc_chat, send_dcc_chat

15
bitchx-docs/1_General/ctcp/action Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

13
bitchx-docs/1_General/ctcp/bdcc Normal file
View File

@@ -0,0 +1,13 @@
Synopsis:
ctcp <nick>|<channel> cdcc <command>
commands are as follows.
<help|resend|resume|send|tresend|tsend|list|info|queue>
Description:
This is a part of the CDCC system builtin to BitchX. These are the
for transfering files using the dcc protocol.
Aliases:
See Also:

13
bitchx-docs/1_General/ctcp/cdcc Normal file
View File

@@ -0,0 +1,13 @@
Synopsis:
ctcp <nick>|<channel> cdcc <command>
commands are as follows.
<help|resend|resume|send|tresend|tsend|list|info|queue>
Description:
This is a part of the CDCC system builtin to BitchX. These are the
for transfering files using the dcc protocol.
Aliases:
See Also:

16
bitchx-docs/1_General/ctcp/clientinfo Normal file
View File

@@ -0,0 +1,16 @@
Synopsis:
ctcp [=]<nick>|<channel> clientinfo [<ctcp command>]
Description:
This lets you find out what CTCP commands another client knows how
to deal with. You can get a more detailed explanation of the CTCP
commands understood by specifying the desired command.
Examples:
To get more information on VERSION from Joebob:
/ctcp joebob clientinfo version
Other Notes:
Some CTCP commands, DCC, ERRMSG and SED in particular, are not meant
to be used manually. The results can be unpredictable.

50
bitchx-docs/1_General/ctcp/ctcp Normal file
View File

@@ -0,0 +1,50 @@
Synopsis:
ctcp [=]<nick>|<channel> <command> [<arguments>]
Description:
The CTCP command is a user-level interface to CTCP, the client-to-
client protocol. CTCP is used for interaction with other clients on
the network, instead of the server. It works by sending a specially
coded message to another client, which will respond to it if it
knows how.
The actual command sent depends on the particular client you are
dealing with, though most that support CTCP at all will support the
basic ones used by ircII. Used in conjunction with ON, just about
any CTCP command can be created and used. To find out what CTCP
commands a client understands, issue it a CTCP CLIENTINFO.
The normal behavior is to send the CTCP command across the network,
though ircII-EPIC also allows them to be sent across DCC CHAT
connections. To do this, prefix the nickname with a "=". If a "*"
is specified instead of a nick or channel, the command is sent to
the current channel. All CTCP commands may be sent to individual
clients or channels, with the same destination limitations as MSG.
Examples:
To request the version of another client:
/ctcp version nickname
To ping a client that you have a DCC CHAT connection to:
/ctcp =nickname ping
To make a client echo back the the arguments you send it:
/ctcp nickname echo send this back
See Also:
ctcp(1) clientinfo; on(5) ctcp, ctcp_reply; load(5) sound; set(4)
no_ctcp_flood, verbose_ctcp
Other Notes:
Aside from the CTCP commands documented here, ircII also supports a
command called SED. SED stands for simple encrypted data, and is used
internally by the client for its built-in encryption. It is not
intended for use by the user, as the results can be unpredictable.
See the ENCRYPT command for more information.
If you happen to be holding an encrypted conversation with another
person, and you send that person a CTCP, it will be encrypted as well.
This is useful primarily because it will encrypt DCC handshakes. This
does pose an incompatibility with older ircII clients, however, as
they won't know how to respond properly.

7
bitchx-docs/1_General/ctcp/echo Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
ctcp [=]<nick>|<message> echo [<any text>]
Description:
This just makes the remote client send back whatever text you send
to it. That's it.

15
bitchx-docs/1_General/ctcp/finger Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> finger
Description:
This will return the idle time of the client it is sent to, as well
as the user's real name (from their system's /etc/passwd file).
See Also:
load(5) finger
Other Notes:
This is not the same as the Unix command of the same name. Though it
returns similar information (idle time, real name), the two have no
relationship between one another.

15
bitchx-docs/1_General/ctcp/ident Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

15
bitchx-docs/1_General/ctcp/invite Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

15
bitchx-docs/1_General/ctcp/op Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

15
bitchx-docs/1_General/ctcp/ops Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

17
bitchx-docs/1_General/ctcp/ping Normal file
View File

@@ -0,0 +1,17 @@
Synopsis:
ctcp [=]<nick>|<channel> ping <current time>
Description:
This command is used to give you a general idea of how much "lag"
(delays due to network congestion) is between you and another client.
The current time is represented as an integer which is the number of
seconds since 1 January 1970. The current time in this format can
be obtained with the $time() function.
Aliases:
The PING command is identical to using CTCP PING with $time() as
the "time" argument.
See Also:
load(5) oldping; ping(1)

10
bitchx-docs/1_General/ctcp/time Normal file
View File

@@ -0,0 +1,10 @@
Synopsis:
ctcp [=]<nick>|<channel> time
Description:
This asks another client for its local time of day. This differs from
the TIME command, which queries the server instead of a client.
See Also:
time(2); time(6)

15
bitchx-docs/1_General/ctcp/unban Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

15
bitchx-docs/1_General/ctcp/uptime Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

10
bitchx-docs/1_General/ctcp/userinfo Normal file
View File

@@ -0,0 +1,10 @@
Synopsis:
ctcp [=]<nick>|<channel> userinfo
Description:
This asks another client to return whatever text it has stored in its
USER_INFORMATION variable, which can be just about anything.
See Also:
set(4) user_information

19
bitchx-docs/1_General/ctcp/utc Normal file
View File

@@ -0,0 +1,19 @@
Synopsis:
ctcp [=]<nick>|<channel> utc <time value>
Description:
This is a convenient means by which to send another client the current
time in your locale without requiring them to request it first. The
time value sent is in the same format as used with CTCP PING.
Examples:
To send another client the current time in your time zone (note that
EVAL is necessary to expand $time() to the actual value when used from
the input line):
/eval ctcp nickname utc $time()
Other Notes:
CTCP UTC is used primarily by robots or other automatons. Unlike
other CTCP commands, an automatic reply is not generated. Instead,
it appears to the recipient as a normal MSG.

15
bitchx-docs/1_General/ctcp/version Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<version> version
Description:
This command asks another client what the name and version of the
client program being used is.
See Also:
version(2)
Other Notes:
Some older ircII clients will return "SL0" in their VERSION reply.
This stands for "Script Level 0". It isn't seen very often anymore,
but if you do see it, that's what it means.

15
bitchx-docs/1_General/ctcp/whoami Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
ctcp [=]<nick>|<channel> action <action description>
Description:
This sends a message to the specified nickname or channel that
describes what you are doing. Instead of telling someone "I'm tired",
it lets you send a message saying "YourNick is tired".
Aliases:
CTCP ACTION is really just a low-level version of ME (for sending to
a channel) and DESCRIBE.
See Also:
describe(1); load(5) action, mudlike; me(1); on(4) action, send_action

13
bitchx-docs/1_General/ctcp/xdcc Normal file
View File

@@ -0,0 +1,13 @@
Synopsis:
ctcp <nick>|<channel> cdcc <command>
commands are as follows.
<help|resend|resume|send|tresend|tsend|list|info|queue>
Description:
This is a part of the CDCC system builtin to BitchX. These are the
for transfering files using the dcc protocol.
Aliases:
See Also:

9
bitchx-docs/1_General/dcc/activecount Normal file
View File

@@ -0,0 +1,9 @@
Synopsis:
dcc activecount
Description:
DCC ACTIVECOUNT displays the number of active dcc's and the number of
possible dcc sends allowed. The number allowed can be changed using /set
DCC_SEND_LIMIT

6
bitchx-docs/1_General/dcc/autoget Normal file
View File

@@ -0,0 +1,6 @@
Synopsis:
dcc autoget
Description:
DCC AUTOGET toggles on/off the automatic receive of dcc files.

7
bitchx-docs/1_General/dcc/autooverwrite Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
dcc autooverwrite
Description:
DCC AUTOOVERWRITE toggles on/off the dcc auto-overwrite of files that
exist and autoget is on.

7
bitchx-docs/1_General/dcc/autorename Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
dcc autorename
Description:
DCC AUTORENAME toggles on/off the dcc autorename of files that exist and
autoget is on.

6
bitchx-docs/1_General/dcc/autoresume Normal file
View File

@@ -0,0 +1,6 @@
BSynopsis:B
_dcc_ autoresume
BDescription:B
DCC AUTORESUME toggles on/off the dcc autoresume of files that exist and
autoget is on.

13
bitchx-docs/1_General/dcc/bot Normal file
View File

@@ -0,0 +1,13 @@
Synopsis:
dcc bot <nick>
Description:
DCC BOT initiates a direct connection to another client, allowing
the users to chat without needing to pass messages through the irc
network. This is a very secure way of communicating on irc, not
to mention that it is generally faster than sending messages across
the irc network. A BOT connection is differant from a CHAT connection.
See Also:
ctcp(1); msg(1); on(5) dcc_chat, send_dcc_chat

20
bitchx-docs/1_General/dcc/chat Normal file
View File

@@ -0,0 +1,20 @@
Synopsis:
dcc chat <nick>
Description:
DCC CHAT initiates a direct connection to another client, allowing
the users to chat without needing to pass messages through the irc
network. This is a very secure way of communicating on irc, not
to mention that it is generally faster than sending messages across
the irc network.
To send a message across the DCC CHAT connection, use MSG as you
normally would, but prefix the nickname with a "=". Additionally,
CTCP commands can be sent across a DCC CHAT connection (allowing you
to initiate a DCC SEND, for instance), if the remote client is also an
EPIC3 (or compatible) client. See the appropriate help files for more
information.
See Also:
ctcp(1); msg(1); on(5) dcc_chat, send_dcc_chat

35
bitchx-docs/1_General/dcc/close Normal file
View File

@@ -0,0 +1,35 @@
Synopsis:
dcc close <type> <nick> [<arguments>]
Description:
DCC CLOSE closes an unwanted DCC connection, or cancels a pending one.
The type, nickname, and parameters required are the same as those
shown in DCC LIST output. If no arguments are specified, the oldest
DCC record for the given type and nick is closed.
When DCC CLOSE is used on a pending incoming connection (one that has
not yet been established), it is treated as a rejected connection, and
a message to that effect is send back to the remote client. Note that
for an incoming SEND, the client actually records it as a GET, since
from a local perspective, the client will be getting something from
the remote client.
DCC CLOSE can also accept the flag '-all' or an asterisk, '*', as either
the type or the nickname. This will work as a wildcard, closing all DCC's
from that type or nickname.
Examples:
To close an existing DCC CHAT connection with joebob:
/dcc close chat joebob
To reject an incoming DCC SEND connection from joebob:
/dcc close get joebob
To close all DCC CHAT connections:
/dcc close chat *
or
/dcc close chat -all
See Also:
dcc(1) closeall, list, rename; on(5) dcc_lost

10
bitchx-docs/1_General/dcc/closeall Normal file
View File

@@ -0,0 +1,10 @@
Synopsis:
dcc closeall
Description:
This command closes every open DCC connection and clears your list of every
entry.
See Also:
dcc(1) close, list, rename; on(5) dcc_lost

28
bitchx-docs/1_General/dcc/dcc Normal file
View File

@@ -0,0 +1,28 @@
Synopsis:
dcc [<command> [<arguments>]]
Description:
DCC stands for direct client-to-client. The DCC command handles all
such connections. There are two primary uses for DCC; bypassing the
irc network for chatting, and file transfers. However, this is not
the limit of DCC's capabilities.
DCC connections are established with CTCP handshakes. All this really
means is that connection request, connection, and rejection messages
are sent in CTCP format. This is noteworthy, as other commands that
operate based on message type will lump DCC messages in with CTCPs
(including IGNORE and the client's internal logging mechanisms).
Aliases:
Using DCC with no arguments is the same as DCC LIST.
See Also:
ctcp(1); on(5) dcc_connect, dcc_lost, dcc_request
Restrictions:
It is worth noting that users behind firewalls may have some problems
using DCC. Depending on the nature of the firewall, such users will
probably be unable to initiate a DCC SEND. Others may find that they
cannot use DCC at all. This is not a bug in ircII-EPIC, it is due
simply to matters beyond the control of the client program.

19
bitchx-docs/1_General/dcc/exempt Normal file
View File

@@ -0,0 +1,19 @@
Synopsis:
dcc exempt [+nickname] [nickname1]
Description:
DCC EXEMPT bypasses /set dcc_autoget and allows the nick to send a
file even when autoget is off.
Example
To add a nick to your exempt list:
/dcc exempt +joe
To remove a nick from your exempt list:
/dcc exempt joe
To display your exempt list:
/dcc exempt

15
bitchx-docs/1_General/dcc/ftp Normal file
View File

@@ -0,0 +1,15 @@
Synopsis:
dcc ftp hostname user password [-p port] [-b blocksize]
Description:
DCC FTP initiates a ftp connection to a host.
To send a message across the DCC FTP connection, use MSG as you
normally would, but prefix the hostname with a "-". If you have a ncftp
bookmarks file in 2.x format, you can use shortcuts from that file for
the hostname. If no user and password is specifed defaults are supplied
for a anonymous connection.
See Also:
ctcp(1); ftp(1); msg(1); on(5) dcc_chat, send_dcc_chat

24
bitchx-docs/1_General/dcc/get Normal file
View File

@@ -0,0 +1,24 @@
Synopsis:
dcc get [=]<nick> [<file>]
Description:
DCC GET initiates a file transfer with a remote client that has offered
the client a DCC SEND. Naturally, a remote client must have already
send the client a DCC SEND request in order for the client to start a
DCC GET with it. If the DCC request comes over an existing DCC CHAT
connection, a '=' must be prepended to the nickname.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest SEND request
is processed first.
Examples:
To accept a SEND from joebob:
/dcc get joebob
To accept all files offered to you by DCCbot:
/dcc get DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_store_path

26
bitchx-docs/1_General/dcc/list Normal file
View File

@@ -0,0 +1,26 @@
Synopsis:
dcc list
Description:
This displays all current and pending DCC connections in a table format.
The data listed includes the type of DCC connection, the remote client
nickname, status (whether it has actually started or not), when the
connection began (if at all), how much data has been transferred over
the link, and any extra arguments present (such as the name of a file
being transferred between clients). Two differant types of display may
be chosen for displaying the information displayed.
Examples:
To show a list of current DCC connections:
/dcc list
Aliases:
DCC LIST operates the same as DCC with no arguments.
See Also:
dcc(1) close; set(4) dcc_bar_type; on(5) dcc_list
Other Notes:
For file transfers, LIST will show the filename being transferred.
Display of the full path can be toggled with DCC SHOWPATHS.

6
bitchx-docs/1_General/dcc/quietmode Normal file
View File

@@ -0,0 +1,6 @@
Synopsis:
dcc quietmode
Description:
DCC QUIETMODE toggles on/off display of dcc output.

27
bitchx-docs/1_General/dcc/raw Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc raw <fd> <host> <message>
Description:
DCC RAW is a raw socket interface for ircII-EPIC. It allows the client
to control arbitrary TCP connections with a remote host on any port
desired.
The actual connection is established with the $connect() function. It
makes the connection and returns a file descriptor that is used by DCC
RAW to control the connection. The file descriptor will always be a
number (generally a small one). Incoming data from the remote host may
be hooked with ON DCC_RAW.
Examples:
To send a message to blah.foo.com over an existing raw DCC connection:
/dcc raw 6 blah.foo.com This is a sample message
See Also:
connect(6); listen(6); on(5) dcc_raw
Other Notes:
The applications for DCC RAW are endless. Since it allows the client
connect to any arbitrary host on any arbitrary port, a little creative
use of the scripting language can turn ircII-EPIC into a client for
most any remote service.

27
bitchx-docs/1_General/dcc/reget Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc reget [=]<nick> [<file>]
Description:
DCC REGET initiates a file transfer with a remote client that has
offered the client a DCC RESEND. Naturally, a remote client must have
already send the client a DCC RESEND request in order for the client to
start a DCC REGET with it. If the DCC request comes over an existing
DCC CHAT connection, a '=' must be prepended to the nickname.
This command resumes the file if it exists. It is not compatible with
mIRC.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest RESEND request
is processed first.
Examples:
To accept a RESEND from joebob:
/dcc reget joebob
To accept all files offered to you by DCCbot:
/dcc reget DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_dldir

25
bitchx-docs/1_General/dcc/rename Normal file
View File

@@ -0,0 +1,25 @@
Synopsis:
dccrename [<nick>] <name> [<new name>]
dccrename -chat <nick> <new nick>
Description:
This renames an incoming file from a DCC GET connection, or optionally
a nick in a DCC CHAT. For files, this is useful if one with the same name
already exists, so that it doesn't get overwritten. If the new name isn't
specified, it is assumed the name given is the new name, and it is applied
to the oldest existing DCC GET connection.
Options:
-chat rename a nick in DCC CHAT instead of a file
Examples:
To rename file foo to bar from joebob:
/dcc rename joebob foo bar
To rename joebob to jimbob in a DCC CHAT:
/dcc rename -chat joebob jimbob
See Also:
dcc(1) get, list; set(4) dcc_store_path

27
bitchx-docs/1_General/dcc/resend Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc resend [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC RESEND offers files to a remote client over DCC. The remote
client must of course acknowledge with a DCC REGET in order to begin the
file transfer.
If a DCC CHAT with the remote client already exists, the RESEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc resend joebob somefile
See Also:
dcc(1) get; set(4) dcc_block_size

30
bitchx-docs/1_General/dcc/resume Normal file
View File

@@ -0,0 +1,30 @@
Synopsis:
dcc resume [=]<nick> <file>
Description:
In the event that a DCC file transfer is interrupted, DCC RESUME can be
used to continue it where the original transfer stopped. This is
generally most useful to users with very slow connections to the
Internet transferring large files.
Examples:
To restart a transfer with joebob:
/dcc resume joebob somebigfile
See Also:
dcc(1) close, get, send
Restrictions:
This command is only available if the client was compiled with the
BROKEN_MIRC_DCC_RESUME #define enabled (in the config.h). The client
compile options string (returned when $info(o) is evaluated) will have
an 'i' in it if this option is enabled.
Other Notes:
It is very important that the user realize that use of this feature is
a blatant violation of the irc protocol (described in rfc 1459), in that
it makes the client respond to a remote PRIVMSG with another PRIVMSG.
While this may not mean much to the average user, it is nonetheless not
"the right way" to do things, and irc operators have been known to KILL
clients that violate the protocol in this manner.

27
bitchx-docs/1_General/dcc/send Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc send [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC SEND offers files to a remote client over DCC. The remote client
must of course acknowledge with a DCC GET in order to begin the file
transfer.
If a DCC CHAT with the remote client already exists, the SEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc send joebob somefile
See Also:
dcc(1) get; set(4) dcc_sliding_window

7
bitchx-docs/1_General/dcc/showpaths Normal file
View File

@@ -0,0 +1,7 @@
Synopsis:
dcc showpaths
Description:
DCC SHOWPATHS toggles on/off the display of pathnames when /dcc LIST is
used.

8
bitchx-docs/1_General/dcc/stats Normal file
View File

@@ -0,0 +1,8 @@
Synopsis:
dcc stats
Description:
DCC STATS displays various information that has been collected during
the clients running time on all dcc sends and gets

26
bitchx-docs/1_General/dcc/tget Normal file
View File

@@ -0,0 +1,26 @@
Synopsis:
dcc tget [=]<nick> [<file>]
Description:
DCC TGET initiates a file transfer with a remote client that has
offered the client a DCC TSEND. Naturally, a remote client must have
already send the client a DCC TSEND request in order for the client to
start a DCC TGET with it. If the DCC request comes over an existing
DCC CHAT connection, a '=' must be prepended to the nickname.
This method is slightly faster than a normal dcc get.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest TSEND request
is processed first.
Examples:
To accept a TSEND from joebob:
/dcc tget joebob
To accept all files offered to you by DCCbot:
/dcc tget DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_dldir

29
bitchx-docs/1_General/dcc/treget Normal file
View File

@@ -0,0 +1,29 @@
Synopsis:
dcc treget [=]<nick> [<file>]
Description:
DCC TREGET initiates a file transfer with a remote client that has
offered the client a DCC TRESEND. Naturally, a remote client must have
already send the client a DCC TRESEND request in order for the client to
start a DCC TREGET with it. If the DCC request comes over an existing
DCC CHAT connection, a '=' must be prepended to the nickname.
This command resumes the file if it exists. It is not compatible with
mIRC.
This method is slightly faster than a normal dcc get.
The client need not specify the name of the file to get. If multiple
files are offered by the same remote client, the oldest TRESEND request
is processed first.
Examples:
To accept a TRESEND from joebob:
/dcc treget joebob
To accept all files offered to you by DCCbot:
/dcc treget DCCbot *
See Also:
dcc(1) rename, resume, send; set(4) dcc_dldir

27
bitchx-docs/1_General/dcc/tresend Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc send [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC SEND offers files to a remote client over DCC. The remote client
must of course acknowledge with a DCC GET in order to begin the file
transfer.
If a DCC CHAT with the remote client already exists, the SEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc send joebob somefile
See Also:
dcc(1) get; set(4) dcc_block_size

27
bitchx-docs/1_General/dcc/tsend Normal file
View File

@@ -0,0 +1,27 @@
Synopsis:
dcc tsend [=]<nick> <file> [<file> ...] [-port <port>]
Description:
DCC TSEND offers files to a remote client over DCC. The remote client
must of course acknowledge with a DCC TGET in order to begin the file
transfer.
If a DCC CHAT with the remote client already exists, the TSEND request
can be sent over that connection by prefixing the nickname with a '='.
This speeds up the handshake considerably. Of course, the remote
client must be able to deal with CTCP commands sent over DCC.
A specific local port may be specified for the transfer. This is useful
to users behind a firewall that only permits inbound connections on
specific port numbers.
Options:
-port use s specific local port
Examples:
To send a file to joebob:
/dcc tsend joebob somefile
See Also:
dcc(1) get; set(4) dcc_block_size

35
bitchx-docs/1_General/describe Normal file
View File

@@ -0,0 +1,35 @@
Synopsis:
describe <nickname|channel> <action description>
Description:
DESCRIBE lets you perform an action. It lets you describe what you're
doing as though someone is watching you, rather than you telling them.
You may send an action to either an individual or to an entire channel.
Examples:
If your nickname is foobar, and you want to send an action to your
friend whose nickname is booya:
/describe booya is eating pizza
To send an action to channel #blah:
/describe #blah is eating pizza
Anyone receiving an action from you will see something like this:
* foobar is eating pizza
Aliases:
DESCRIBE is identical to CTCP ACTION. When sending an action to a
channel, it functions identically to the ME command.
See Also:
ctcp(1) action; load(5) action, mudlike; me(1); on(5) action,
send_action
Restrictions:
This command makes use of CTCP (client-to-client protocol), which is not
part of the IRC protocol. Most modern IRC clients understand CTCP, but
not all do, while others might not support the same CTCP commands that
ircII-EPIC supports. If you receive an error of some sort, then the
client on the receiving end is unable to properly handle your CTCP
message.

19
bitchx-docs/1_General/disconnect Normal file
View File

@@ -0,0 +1,19 @@
Synopsis:
disconnect [<server number> [<reason>]]
Description:
This command disconnects you from your server, but does not actually
make the client quit. If you are connected to multiple servers in
multiple windows, the client will only close the connection to the
current server.
Examples:
To disconnect from your current server:
/disconnect
To disconnect from server 2 in your server list:
/disconnect 2 I'll be back later!
See Also:
reconnect(1); server(1)

51
bitchx-docs/1_General/gone Normal file
View File

@@ -0,0 +1,51 @@
Synopsis:
gone [[<options>] <away message>]
Description:
This command marks you as being "away". It is used to tell people that
you currently aren't paying attention to your screen. You might use it
if you are taking a nap, in the shower, getting some food, or otherwise
just aren't there at the moment. When you mark yourself as away, your
status bar will show the value of STATUS_AWAY to reflect this; this is
"(Away)" by default. GONE marks you away silently.
Anyone who does a WHOIS on your nickname will see that you are away, as
well as your away message. Anyone doing a WHO that returns information
about you will also see that you're gone. By default, if someone sends
you a MSG while you are away, your client will beep. You can turn this
off by setting BEEP_WHEN_AWAY to OFF.
If you send a MSG to someone who is away, you will automatically be
notified of this. By default, you will only receive this notification
once. If you wish to see it every time (to tell when a person is no
longer marked away, for instance), change SHOW_AWAY_ONCE to OFF.
You can remove your away status by using AWAY with no arguments.
Options:
-all send the away message to all servers you are on
-one send away message to only the current server (default)
Examples:
To mark yourself away:
/gone I'm not here right now, I'll be back soon
To mark yourself away on all servers:
/gone -all I'm in the shower, back in 10 minutes
To remove your away status:
/gone
See Also:
load(5) away; set(4) beep_when_away, show_away_once, status_away,
send_away_msg; who(2); whois(2)
Restrictions:
AWAY status (and messages) is only through the network once,
when it is first set. The implication of this is that, if the AWAY was
set during a netsplit, when the netsplit heals, the reconnecting servers
will not be aware of the AWAY status. Thus, anyone on those servers
using WHO or WHOIS will not know you are away. In addition, servers
will impose a limit to the length of the AWAY message; this is usually
80 characters; test it on your server to be certain.

40
bitchx-docs/1_General/help Normal file
View File

@@ -0,0 +1,40 @@
Synopsis:
help [<topic> [<subtopic> ...]]
Description:
As its name implies, HELP is the command for getting help with some
feature of the client. Currently, the EPIC help system divides the
various help documents up into logical groups, each group is given a
unique section number.
Help files are uniformly structured. All files include, at the very
least, a synopsis and description (such as this file). Some files
also include a description of switches accepted by the command, a
list of aliases to the command, bug warnings, or other miscellaneous
information.
Some also include a list of related help topics. These references are
usually followed by a number in parentheses. This number is the help
section that the command is listed under. Help file names are not
sensitive to case (e.g. "HELP" is the same as "help"), and they may be
abbreviated unambiguously (e.g. "hel" is the same as "help", but "wh"
is ambiguous because it matches "who", "whois", "whowas", etc.).
Options:
-wait this will stop script processing until the user is finished
in the help system
Examples:
To get help on the WHOIS command (in section 3):
/help 3 whois
To list all of the help files in section 3 (server queries):
/help 3 ?
To list all help sections:
/help
See Also:
Introduction(7); New_User(7); on(5) help; set(4) help_pager, help_path,
help_prompt, help_window

84
bitchx-docs/1_General/ignore Normal file
View File

@@ -0,0 +1,84 @@
Synopsis:
ignore [<nick | user@host>] [[-|+|^]<message type(s)>]
ignore [<nick!user@host>] [[-|+|^]<message type(s)>]
ignore [<channel>] [[-|+|^]<message type(s)>]
Description:
The IGNORE command has two primary uses; filtering out messages that
are unwanted, and highlighting messages of particular importance. The
default method is to filter messages out.
Messages can be filtered based on any nick!user@host pattern, as well
as just by nick (a "!*@*" will be appended to complete the pattern) or
just by user@host (a "*!" will be prepended). Messages can be filtered
at the channel level, too.
Messages can also be filtered based on context, so you could ignore all
INVITEs from a person and still receive all other messages from that
person. Alter- nately, you could ignore all INVITEs from everyone except
a specified person.
IGNORE will apply a filter based on the best possible match. Thus, if
you are ignoring *!*@*.net and *!*foobar@*.slurpee.net, and someone
with an nick!user@host mask of BigFoob!foobar@grape.slurpee.net sends
you a message, IGNORE will use *!*foobar@*.slurpee.net to determine how
to filter the message. This will prove useful, as shown in the example
below.
Using IGNORE with no arguments displays the list of patterns you are
ignoring or highlighting, as well as the type of messages for each
pattern.
Options:
ctcps filter in/out all CTCPs received
invites filter in/out all INVITEs received
msgs filter in/out all MSGs received (but not CTCPs)
notes filter in/out all NOTEs received
notices filter in/out all NOTICEs received
public filter in/out public channel conversation
wallops filter in/out operator WALLOPS
crap anything else not listed above
all everything listed above
none remove pattern from list of filtered patterns
Examples:
To ignore everything from foobar:
/ignore foobar all
To ignore everything except public conversation from foobar:
/ignore foobar all -publics
To highlight all private messages from foobar (it is displayed
highlighted with whatever you have set HIGHLIGHT_CHAR to):
/ignore foobar +msgs
To ignore all NOTICEs except those from foobar's site:
/ignore * notices
/ignore *!*@*.slurpee.net ^notices
To remove *!*foobar@*.slurpee.net from your ignore list:
/ignore *!*foobar@*.slurpee.net none
To highlight people joining and leaving, mode changes, etc. for a channel:
/ignore #channel +crap
See Also:
set(4) highlight_char, send_ignore_msg; silence(1); igmask(6);
rigmask(6); igtype(6); rigtype(6)
Restrictions:
IGNORE is a client command. All it does is hide messages sent to you by
the person you want to ignore. However, your server is actually still
sending the messages to you, so while it works fine to ignore someone
who is annoying you, it is not very effective when dealing with abusive
users who insist on flooding you or the channel you're on. On some
servers, however, there is a mechanism to ignore a person at the server
level, using a command called SILENCE. SILENCE is limited to the
Undernet, and servers derived from or compatible with it.
Other Notes:
When removing a person from your ignorance list, you must specify the
pattern to remove exactly as you originally entered it or as it appears
in your ignorance list (case insensitive). IGNORE does no pattern
matching in this respect.

19
bitchx-docs/1_General/invite Normal file
View File

@@ -0,0 +1,19 @@
Synopsis:
invite <nickname> <channel>
Description:
This command lets you invite people to a one of your current channels.
This is generally used on channels that are +i (meaning people can only
join if someone INVITEs them; see MODE for more information on channel
modes), but this is not a restriction.
Examples:
To invite foobar to channel #blah:
/invite foobar #blah
To join the last channel you were INVITEd to:
/join -invite
See Also:
join(1); mode(1); on(5) invite

67
bitchx-docs/1_General/j Normal file
View File

@@ -0,0 +1,67 @@
Synopsis:
j [-invite|<channel list> [<key>]]
Description:
J lets you join a new channel. If you are on multiple channels,
the specified channel will become the current one. If you do not
specify a channel (or channels) to join, your client will display
your current channels, along with their respective modes and users,
and which server you are on the channel from.
You may join more than channel at a time with a single J command
by separating the channels with commas. If a key (channel mode +k)
is set on a channel you wish to join, you must specify that key in
the JOIN command to be able to join the channel.
You can create a new channel simply by joining a channel that does
not exist. Channel names begin with a '#', a '&' (&channels are local
to your server), or a '+' (modeless channels, not available everywhere)
and following that may consist of any character except SPACE, BELL, NUL,
CR, LF, or comma (','). Channel names may be up to 200 characters in
length. Additionally, a channel may be restricted to only users from
certain hosts, by adding a hostmask to the end of the channel name,
separated with a ':' (this is not supported everywhere).
Options:
-invite makes you join the last channel to which you were INVITEd
Examples:
To join channel #blah (or create it if it does not exist):
/j #blah
To join channel #blah that has the key "foobar":
/j #blah foobar
To join more than one channel at once:
/j #foo,#bar,&blah
To join a channel that only German users may join:
/j #blah:*.de
To join channel #blah if you have been invited to it (either will
work, although the first is better, since channel names may contain
characters that your terminal can't display):
/j -invite
/j #blah
Aliases:
J is identical in operation to JOIN.
See Also:
bind(4) switch_channels; invite(1); mode(1); on(5) join; set(4) novice;
window(4) channel
Restrictions:
The ability to join a channel can be restricted by the channel's modes.
If mode +k is set, you must specify the channel's key to join. If mode
+i is set, you must first be INVITEd. If mode +l is set, and the limit
has been reached, you cannot join. If a ban (mode +b) has been set
that matches your nick!user@host pattern, you cannot join. See MODE
for more information.
Other Notes:
The ircII client provides a NOVICE mode mechanism. When turned on, the
client will not allow you to join more than one channel at once. If
you are on a channel and try to join another, it will first make you
leave the first channel.

67
bitchx-docs/1_General/join Normal file
View File

@@ -0,0 +1,67 @@
Synopsis:
join [-invite|<channel list> [<key>]]
Description:
JOIN lets you join a new channel. If you are on multiple channels,
the specified channel will become the current one. If you do not
specify a channel (or channels) to join, your client will display
your current channels, along with their respective modes and users,
and which server you are on the channel from.
You may join more than channel at a time with a single JOIN command
by separating the channels with commas. If a key (channel mode +k)
is set on a channel you wish to join, you must specify that key in
the JOIN command to be able to join the channel.
You can create a new channel simply by joining a channel that does
not exist. Channel names begin with a '#', a '&' (&channels are local
to your server), or a '+' (modeless channels, not available everywhere)
and following that may consist of any character except SPACE, BELL, NUL,
CR, LF, or comma (','). Channel names may be up to 200 characters in
length. Additionally, a channel may be restricted to only users from
certain hosts, by adding a hostmask to the end of the channel name,
separated with a ':' (this is not supported everywhere).
Options:
-invite makes you join the last channel to which you were INVITEd
Examples:
To join channel #blah (or create it if it does not exist):
/join #blah
To join channel #blah that has the key "foobar":
/join #blah foobar
To join more than one channel at once:
/join #foo,#bar,&blah
To join a channel that only German users may join:
/join #blah:*.de
To join channel #blah if you have been invited to it (either will
work, although the first is better, since channel names may contain
characters that your terminal can't display):
/join -invite
/join #blah
Aliases:
CHANNEL is identical in operation to JOIN.
See Also:
bind(4) switch_channels; invite(1); mode(1); on(5) join; set(4) novice;
window(4) channel
Restrictions:
The ability to join a channel can be restricted by the channel's modes.
If mode +k is set, you must specify the channel's key to join. If mode
+i is set, you must first be INVITEd. If mode +l is set, and the limit
has been reached, you cannot join. If a ban (mode +b) has been set
that matches your nick!user@host pattern, you cannot join. See MODE
for more information.
Other Notes:
The ircII client provides a NOVICE mode mechanism. When turned on, the
client will not allow you to join more than one channel at once. If
you are on a channel and try to join another, it will first make you
leave the first channel.

33
bitchx-docs/1_General/k Normal file
View File

@@ -0,0 +1,33 @@
Synopsis:
k [<channel>] <nickname> [<reason for kick>]
Description:
This command "kicks" the specified user off of the specified channel.
It is typically used to remove troublemakers, flooders, or people
otherwise making a nuisance of themselves on the channel. The reason
for the kick is recommended, but not required by the IRC servers.
Examples:
To kick foobar out of channel #blah:
/k #blah foobar Go away!
To kick foobar out of your current channel:
/k foobar I said go away!!
See Also:
ignore(1); load(5) autokick; mode(1); on(5) kick
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.
Other Notes:
It is important to note that channel operators are the single absolute
authority on their channels, and as such they may kick out anyone they
choose for any reason (or no reason at all). Keep in mind, however,
that doing so for such petty reasons won't make you very popular with
other users, and it isn't unheard of for users to abusively avenge the
kick. If someone is annoying you, using IGNORE (or SILENCE, if
available) is a better solution. KICK should be reserved for users who
are harassing your channel or its members in general.

34
bitchx-docs/1_General/kb Normal file
View File

@@ -0,0 +1,34 @@
Synopsis:
kb *|<channel> <nickname> [<reason for kick>]
Description:
This command "kicks" and "bans" the specified user off of the specified
channel. It is typically used to remove troublemakers, flooders, or
people otherwise making a nuisance of themselves on the channel.
The reason for the kick is randomly taken from BitchX.reasons if not
given.
Examples:
To kick foobar out of channel #blah:
/kb #blah foobar Go away!
To kick foobar out of your current channel:
/kb foobar I said go away!!
See Also:
ignore(1); load(5) autokick; mode(1); on(5) kick
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.
Other Notes:
It is important to note that channel operators are the single absolute
authority on their channels, and as such they may kick out anyone they
choose for any reason (or no reason at all). Keep in mind, however,
that doing so for such petty reasons won't make you very popular with
other users, and it isn't unheard of for users to abusively avenge the
kick. If someone is annoying you, using IGNORE (or SILENCE, if
available) is a better solution. KICK should be reserved for users who
are harassing your channel or its members in general.

33
bitchx-docs/1_General/kbi Normal file
View File

@@ -0,0 +1,33 @@
Synopsis:
kbi [<channel>] <nickname> [<reason for kick>]
Description:
This command "kicks/bans/ignores" the specified user off of the specified
channel. It is typically used to remove troublemakers, flooders, or people
otherwise making a nuisance of themselves on the channel. The reason
for the kick is recommended, but not required by the IRC servers.
Examples:
To kick foobar out of channel #blah:
/kbi #blah foobar Go away!
To kick foobar out of your current channel:
/kbi foobar I said go away!!
See Also:
ignore(1); load(5) autokick; mode(1); on(5) kick
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.
Other Notes:
It is important to note that channel operators are the single absolute
authority on their channels, and as such they may kick out anyone they
choose for any reason (or no reason at all). Keep in mind, however,
that doing so for such petty reasons won't make you very popular with
other users, and it isn't unheard of for users to abusively avenge the
kick. If someone is annoying you, using IGNORE (or SILENCE, if
available) is a better solution. KICK should be reserved for users who
are harassing your channel or its members in general.

33
bitchx-docs/1_General/kick Normal file
View File

@@ -0,0 +1,33 @@
Synopsis:
kick *|<channel> <nickname> [<reason for kick>]
Description:
This command "kicks" the specified user off of the specified channel.
It is typically used to remove troublemakers, flooders, or people
otherwise making a nuisance of themselves on the channel. The reason
for the kick is recommended, but not required by the IRC servers.
Examples:
To kick foobar out of channel #blah:
/kick #blah foobar Go away!
To kick foobar out of your current channel:
/kick * foobar I said go away!!
See Also:
ignore(1); load(5) autokick; mode(1); on(5) kick
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.
Other Notes:
It is important to note that channel operators are the single absolute
authority on their channels, and as such they may kick out anyone they
choose for any reason (or no reason at all). Keep in mind, however,
that doing so for such petty reasons won't make you very popular with
other users, and it isn't unheard of for users to abusively avenge the
kick. If someone is annoying you, using IGNORE (or SILENCE, if
available) is a better solution. KICK should be reserved for users who
are harassing your channel or its members in general.

22
bitchx-docs/1_General/kickidle Normal file
View File

@@ -0,0 +1,22 @@
Synopsis:
kickidle [<channel>]
Description:
This command "kicks" idle users off the current or specified channel.
It will not kick unless /addidle is turned on for the channel. It will
not kick ops.
Examples:
To kickidle on channel #blah:
/kickidle #blah
To kick foobar out of your current channel:
/kickidle
See Also:
addidle(1); unidle(1); showidle(1);
Restrictions:
KICK is limited to channel operators (users with channel mode +o; see
MODE for more information) on the specified channel.

24
bitchx-docs/1_General/l Normal file
View File

@@ -0,0 +1,24 @@
Synopsis:
l [<channel>|*] [:<part message>]
Description:
L makes you leave a channel. That's it. If you happen to be on
multiple channels, you may leave more than one at the same time.
Examples:
To leave channel #foobar:
/l #foobar :I'm going to #fubar, it's cooler!
To leave your current channel:
/l
To leave channels #foo and #bar at the same time:
/l #foo,#bar
See Also:
join(1); partall(1); on(5) leave; set(4) novice
Restrictions:
If you specify "*" as the channel to leave, you may not specify any
other channels to leave at the same time.

9
bitchx-docs/1_General/lamenicklist Normal file
View File

@@ -0,0 +1,9 @@
Synopsis:
lamenicklist
Description:
LAMENICKLIST displays your lamenick list.
See Also:
addlamenick(1) unlamenick(1)

60
bitchx-docs/1_General/lastlog Normal file
View File

@@ -0,0 +1,60 @@
Synopsis:
lastlog [-] [-<flag>] [--<flag>] [<pattern>] [<number of entries [<start>]]
Description:
LASTLOG allows you to view messages that were on your screen at one
time but have since scrolled off. This is convenient is you aren't
on a terminal capable of maintaining its own scrollback buffer, or
if you accidentally used CLEAR before reading a message.
LASTLOG only returns data saved in your client's lastlog buffer.
This is limited by both your LASTLOG setting, which specifies how
many lines to save, and the LASTLOG_LEVEL setting, which says what
types of messages to save. It can return a specified number of
lines, any lines which match a given pattern, or any combination.
Additionally, the output can be limited to a specific type, and
multiword patterns are allowed (by surrounding the whole thing in
double quotes), as are wildcards.
If the first argument is a single hyphen (-), the output will not be
surrounded by "Lastlog:" and "End of Lastlog" messages.
Options:
-action CTCP ACTIONs
-all all qualifying levels
-crap anything not covered above
-ctcp CTCPs (except ACTIONs and DCC stuff)
-dcc DCC connection and status messages
-literal search for a literal string
-max <num> only returns <num> matches
-msg private messages
-note NOTEs
-notice NOTICEs
-opnote operator notifications
-public public channel conversation
-reverse display the log backwards; from the END to the BEGINNING
-snote server notices
-wall WALLs (deprecated since WALL is no longer supported)
-wallop WALLOPs
-userlog1 - 4 anything XECHOed under USERLOG1 - USERLOG4
A double hyphen in front of a flag disables the output of that level.
Examples:
To list all private messages from JoeBob:
/lastlog -msg joebob
To list all public messages from JoeBob in the last 100 lines
/lastlog -public joebob 100
To list all occurrences of the phrase "ircII-EPIC is cool" from 100
to 600 lines ago:
/lastlog "ircII-EPIC is cool" 100 500
To list everything *except* messages:
/lastlog -all --msgs
See Also:
set(4) lastlog, lastlog_level, log, logfile; window(4) lastlog_level,
log, logfile

26
bitchx-docs/1_General/leave Normal file
View File

@@ -0,0 +1,26 @@
Synopsis:
leave <channel>|* [:<part message>]
Description:
LEAVE makes you leave a channel. That's it. If you happen to be on
multiple channels, you may leave more than one at the same time.
You may also specify a "*", which is interpreted as your current
channel. As with QUIT, you may specify a "leaving message."
Examples:
To leave channel #foobar:
/leave #foobar :I'm going to #fubar, it's cooler!
To leave your current channel:
/leave *
To leave channels #foo and #bar at the same time:
/leave #foo,#bar
See Also:
join(1); on(5) leave; set(4) novice
Restrictions:
If you specify "*" as the channel to leave, you may not specify any
other channels to leave at the same time.

70
bitchx-docs/1_General/m Normal file
View File

@@ -0,0 +1,70 @@
Synopsis:
m [=]<nickname> <text to send>
m <channel> <text to send>
m %<process id|process name> <text to send>
m -<hostname> <text to send>
Description:
This command has 3 primary functions; to send a private message to an
individual, to send a message to a channel, or to send a message to a
running EXEC process (usually a command of some sort). You can specify
multiple recipients for the message by delimiting them with commas (but
no spaces), and you may even mix-and-match the types of recipients.
Additionally, there are 3 special cases for recipients. If you specify
a single comma, ",", the message will go to the last person who sent you a
M. If a single period, ".", the message will go to the last person you
sent a M to. If you specify an asterisk, "*", the message will go to
your current channel.
Finally, you can make ircII-EPIC beep whenever you receive a private
message by setting BEEP_ON_MSG to "msgs". This is turned off by
default.
Examples:
To send a private message to your friend Buddha:
/m buddha hi there!
To send a message to your current channel:
/m #channel how is everyone today?
To send a message to a running EXECed process with id 2:
/m %2 exit
To send a message to your friends buddha, booya (with whom you have a
DCC CHAT running), and channel #foobar:
/m buddha,=booya,#foobar see you later!
To send a message to an EXECed process named "mail":
/m %mail x
Aliases:
When sending a message to your current channel, MSG has the same effect
as the SAY command.
See Also:
dcc(1) chat; exec(5); load(5) nicks; notice(1); on(5) msg, public_msg,
send_msg; query(1); say(1); send(5); set(4) beep_on_msg
Restrictions:
The IRC protocol explicitly prohibits any client from sending any
automated response to a MSG other than a NOTICE, and ircII-EPIC
enforces this policy.
The special cases for private MSG recipients, ",", ".", and "*", may
not be specified with any other recipients (i.e. in a comma-delimited
list), they must be used alone. Attempting to do so will cause the
client to not interpret them and assume they are literal nicknames,
which will return a "No such nick/channel" error message.
You may not send a message to any channel that is +n unless you are
currently on it (and if it is +m, you must have +v or +o status). See
MODE for more information.
Recent +CS servers (mostly used on EFnet) now restrict the number of
people you may simultaneously send a MSG to. The maximum is 20 people,
though local operators will be warned if there are more than 10, in an
attempt to curb irc "spams". The /th servers are knows to behave in a
similar manner. Hybrid6 servers have completely removed this capability.

32
bitchx-docs/1_General/me Normal file
View File

@@ -0,0 +1,32 @@
Synopsis:
me <action description>
Description:
ME lets you perform an action on your current channel. It lets you
describe what you're doing as though someone is watching you, rather
than you telling them.
Examples:
To perform an action:
/me doesn't want to go to work today
Anyone on the channel you sent the action to will see something like
this:
* foobar doesn't want to go to work today
Aliases:
ME functions identically to using DESCRIBE to send an action to your
current channel, as well as to CTCP ACTION.
See Also:
ctcp(1) action; load(5) action, mudlike; describe(1); on(5) action,
send_action
Restrictions:
This command makes use of CTCP (client-to-client protocol), which is not
part of the IRC protocol. Most modern IRC clients understand CTCP, but
not all do, while others might not support the same CTCP commands that
ircII-EPIC supports. If you receive an error of some sort, then the
client on the receiving end is unable to properly handle your CTCP
message.

168
bitchx-docs/1_General/mode Normal file
View File

@@ -0,0 +1,168 @@
Synopsis:
mode <your nickname|channel> [<+|-><mode> [<mode parameter(s)>]]
Description:
Both channels and users have modes associated with them. For channels,
they determine who is a channel operator, the number of people who may
join the channel, who may not enter the channel, and myriad other
things. For users, they determine whether the user will is an IRC
operator, whether the user will receive special server notices, etc.
Modes are enabled when prepended with a "+", and disabled when with a
"-". Modes may be clustered as well. When clustering modes, all mode
changes are specified first, then their parameters (see the examples
below).
Options:
Standard User Modes:
i When enabled, you are "invisible" to NAMES and WHO queries from
anyone not on a channel common to you. Additionally, you are
also hidden from WHOIS unless your exact nickname is specified.
o When enabled, this gives you IRC operator status (however, see
restrictions below).
s When enabled, you will receive special server notices (such as
nickname collisions, fake modes, etc.).
w When enabled, you will receive IRC operator WALLOPS, as well as
notices of any remote CONNECTs or SQUITs.
Standard Channel Modes:
b When enabled, this prevents the specified nick!user@host mask
from entering the channel. If only the @host portion is
specified, "*!*" is prepended; if only user@host is specified,
"*!" is prepended; if the mask does not contain a "@", it is
assumed to be a nickname, and a !*@* is appended. When used
with no arguments, the channels list of "bans" is displayed.
i When enabled, users may only join the channel if INVITEd.
k When enabled, users may only join the channel if they specify
the proper "key" (which is specified when +k is set).
l When enabled, only the specified number of users may enter the
channel.
m When enabled, only users with +o or +v may speak on the channel.
n When enabled, public messages from outside the channel are not
allowed.
o When enabled, grants the specified nickname channel operator
status.
p When enabled, the channel is made private. The channel name
will not show up in WHO, WHOIS, NAMES, or LIST replies (though
users who are not +i will still be shown in NAMES, the channel
name is simply masked as "Private").
s When enabled, makes the channel secret. This is the same as +p,
except the channel will not show up in any WHO/WHOIS/etc.
queries from a person not on the channel. Anyone who is on a
+s channel is effectively invisible, as per user mode +i.
t When enabled, only channel operators may set a topic.
v When enabled, grants the specified nickname voice status.
Examples:
To receive operator WALLOPS and server notices (both examples are
equivalent):
/mode your_nick +sw
/mode your_nick +s+w
To set a channel limit (the number is arbitrary):
/mode #channel +l 35
To make someone a channel operator:
/mode #channel +o theirnick
To set a ban, a key, and to remove chanop status from someone:
/mode #channel +bk-o *!*some@*.ban.com Secret_Key foobar
See Also:
chanmode(6); deop(4); invite(1); key(6); kick(1); on(5) mode,
mode_stripped; oper(4); set(4) mode_stripper; usermode(6); wallops(4)
Restrictions:
Only channel operators may set modes for a channel (though anyone may
view them), and only you may set or view your personal user modes.
Additionally, the user mode +o may NOT be set with MODE, you must use
the OPER command. However, it may be removed with -o (see DEOP as
well).
Also note that some server variants do not allow for redundant mode
changes, such as "+oo foobar foobar". This shouldn't cause too many
problems though, since you can easily reverse a mode if you wish to set
it again, such as "-o+o foobar foobar", which is allowed.
Finally, note that mode changes are limited to a maximum of 4 total
parameters. Thus you could give +o to 3 people and set +l, but you
could not do those and set +k as well, since that would involve 5
parameters.
Other Notes:
On Undernet servers, the maximum number of parameters for MODE is 6.
Additionally, some server versions have extra modes that may be used.
Keep in mind that these do not apply everywhere, so you should check
what software version your server is using to be sure (see VERSION).
Undernet servers (ircu2.9.x):
User Modes:
d When enabled, your client does not receive any public messages
from any channel you are on. (mnemonic: deaf mode)
k No-kick mode. Any client with this mode may not be kicked from
any channel it applies to. Limited to services.
DALnet servers (ircu2.9.x+DAL, DAL4.x)
User Modes:
g Allows operators to see all OPER attempts, and failed server
connects. Allows all users to see nickname collisions.
h Shows operators the arguments to any protocol HELP command
issued. Server numeric 310 is returned in WHOIS to denote
+h users.
IRC 2.9 servers (irc2.9.x):
User Modes:
r When enabled, the client cannot be a channel operator (even if
it is the first to join), nor can it change nicknames. This
mode is automatic if the connecting client has a matching i:
line. This mode cannot be reversed once enabled.
(s) Version 2.9 servers do not have a +s user mode.
Channel Modes:
a When enabled, this makes the channel anonymous. Nicknames are
hidden (and thus nick changes are not shown), and no other
channel modes are permitted. Note that this can seriously
confuse the client...
EFnet +CS servers (irc2.8.x+CSr27 and beyond):
User Modes:
b When enabled, shows connects from potential bots, and attempts
with invalid usernames.
c When enabled, shows all clients connecting and disconnecting
from your server. Limited to irc operators.
d When enabled, shows connects where the username given and the
client's ident response differ.
f When enabled, shows all "Fake MODE" and "Nickname Collision"
notices.
k When enabled, shows all global and local operator kills.
l When enabled, shows connect attempts from clients that exceed
their connect class (Y:line) limit.
(r) Replaced by +bdl after CSr25.
s When enabled, it shows any miscellaneous server notices that
are not shown with modes bcdfklu (even if they are not
enabled).
u When enabled, shows all unauthorized connect attempts, as well
as connect attempts when the server has reached its maximum
connection limit.
EFnet /th servers (irc2.8/th):
User Modes:
c When enabled, shows all clients connecting and disconnecting
from your server. Limited to IRC operators.
d Debug mode, displays miscellaneous messages. Limited to irc
operators.
k When enabled, shows all server kills
n Shows all local nickname changes. Limited to irc operators.
r When enabled, shows all rejected connections.
s When enabled, it shows any miscellaneous server notices that
are not shown with modes ckr, including operator kills
y Spy mode, informs operators of all LINKS, STATS, and TRACE
commands issued, and of any failed MSG commands.
AnotherNet servers
User Modes:
c Show all [dis]connections, possible clones, and invalid logins
f Show all DCC handshakes (mnemonic: file transfers)
h Makes operator completely invisible to all normal users;
mainly meant for channel services (mnemonic: hidden)

68
bitchx-docs/1_General/msg Normal file
View File

@@ -0,0 +1,68 @@
Synopsis:
msg [=]<nickname> <text to send>
msg <channel> <text to send>
msg %<process id|process name> <text to send>
Description:
This command has 3 primary functions; to send a private message to an
individual, to send a message to a channel, or to send a message to a
running EXEC process (usually a command of some sort). You can specify
multiple recipients for the message by delimiting them with commas (but
no spaces), and you may even mix-and-match the types of recipients.
Additionally, there are 3 special cases for recipients. If you specify
a single comma, ",", the message will go to the last person who sent you a
MSG. If a single period, ".", the message will go to the last person you
sent a MSG to. If you specify an asterisk, "*", the message will go to
your current channel.
Finally, you can make ircII-EPIC beep whenever you receive a private
message by setting BEEP_ON_MSG to "msgs". This is turned off by
default.
Examples:
To send a private message to your friend Buddha:
/msg buddha hi there!
To send a message to your current channel:
/msg #channel how is everyone today?
To send a message to a running EXECed process with id 2:
/msg %2 exit
To send a message to your friends buddha, booya (with whom you have a
DCC CHAT running), and channel #foobar:
/msg buddha,=booya,#foobar see you later!
To send a message to an EXECed process named "mail":
/msg %mail x
Aliases:
When sending a message to your current channel, MSG has the same effect
as the SAY command.
See Also:
dcc(1) chat; exec(5); load(5) nicks; notice(1); on(5) msg, public_msg,
send_msg; query(1); say(1); send(5); set(4) beep_on_msg
Restrictions:
The IRC protocol explicitly prohibits any client from sending any
automated response to a MSG other than a NOTICE, and ircII-EPIC
enforces this policy.
The special cases for private MSG recipients, ",", ".", and "*", may
not be specified with any other recipients (i.e. in a comma-delimited
list), they must be used alone. Attempting to do so will cause the
client to not interpret them and assume they are literal nicknames,
which will return a "No such nick/channel" error message.
You may not send a message to any channel that is +n unless you are
currently on it (and if it is +m, you must have +v or +o status). See
MODE for more information.
Recent +CS servers (mostly used on EFnet) now restrict the number of
people you may simultaneously send a MSG to. The maximum is 20 people,
though local operators will be warned if there are more than 10, in an
attempt to curb irc "spams". The /th servers are knows to behave in a
similar manner.

35
bitchx-docs/1_General/nick Normal file
View File

@@ -0,0 +1,35 @@
Synopsis:
nick [<new nickname>]
Description:
The NICK command allows you to change your current nickname to something
else. If you choose a nickname that is already in use, you will receive
an error message to that effect, and your nickname will not be changed.
Nicknames are not case-sensitive.
If you do not specify a new nickname, your current one is displayed.
Examples:
To change your nick to foobar:
/nick foobar
To display your current nickname:
/nick
See Also:
on(5) channel_nick, nickname; set(4) auto_new_nick
Restrictions:
Nicknames on IRC are restricted to 9 characters in total length (except
on DALnet, where the limit is 30). All nicknames must begin with a
letter, and then may be followed by any letter, number or any of the
following characters: - _ \ | [ ] { } ` ^
Other Notes:
The special allowance for 30-character nicknames requires the client
to be compiled with the #define "ALLOW_LONG_NICKNAMES" enabled. This
is done by default, but if for some reason the person compiling the
client has disabled it, any attempts to use a nickname longer than 9
characters will be truncated to 9 characters. This can be circumvented
by using the raw server NICK command: /quote nick <new nick>

9
bitchx-docs/1_General/nochat Normal file
View File

@@ -0,0 +1,9 @@
Synopsis:
nochat <nick>
Description:
NOCHAT removes the request for direct connection to another client.
See Also:
ctcp(1); msg(1); on(5) dcc_chat, send_dcc_chat

20
bitchx-docs/1_General/noforward Normal file
View File

@@ -0,0 +1,20 @@
Synopsis:
unforward
Description:
This command will remove the forward of msgs sent to another nick or
another channel.
Examples:
To unforward to a nick:
/unforward nick
To unforward to a channel:
/unforward #channel
See Also:
addforward(1) noforward(1)
Restrictions:
This could possibly get you in trouble in some cases. Use with caution.

21
bitchx-docs/1_General/notice Normal file
View File

@@ -0,0 +1,21 @@
Synopsis:
notice [=]<nickname> <text to send>
notice <channel> <text to send>
notice %<process id|process name> <text to send>
Description:
NOTICE is functionally equivalent to MSG. Like MSG, it may send to
a person or a channel, and may send to more than one target. The command
was primarily intended as a message type that guaranteed no automated
responses. See MSG for more information.
See Also:
msg(1); on(5) notice, public_notice, send_notice
Restrictions:
The IRC protocol explicitly prohibits any client from automatically
responding to NOTICE with a MSG, CTCP, another NOTICE, or anything
else, and ircII-EPIC will do everything in its power to prevent you
from doing it :)

41
bitchx-docs/1_General/notify Normal file
View File

@@ -0,0 +1,41 @@
Synopsis:
notify [[-]<nickname> [[-]<nickname> ...]]
notify <+|->
Description:
The NOTIFY command lets you specify a list of nicknames to watch for,
and will notify you any time a specified nickname signs on or signs off
IRC. A "signoff" message will be generated if the person changes his
or her nickname, so keep this in mind.
Options:
- When used alone, this will clear your notify list. When used with
a nickname, it will remove that nick from the list.
+ This will display any nicks on your notify list who are signed on.
Examples:
To add your friends scuba and diver to your notify list:
/notify scuba diver
To remove your ex-friend buddha from your notify list:
/notify -buddha
To clear your notify list:
/notify -
To show your friends that are current logged on irc:
/notify +
See Also:
ison(2); notify(6); set(4) notify_handler
Restrictions:
Everyone asks, so here's a formal answer before you ask. No, you cannot
specify a nick!user@host mask to notify, nor can you specify wildcards.
NOTE allows for this functionality, but not all servers enable it.
Bugs:
If you redefine the numeric 303 hook, be careful! NOTIFY absolutely
depends on this numeric, and redefining the default behavior will
probably trash your NOTIFY output.

25
bitchx-docs/1_General/nslookup Normal file
View File

@@ -0,0 +1,25 @@
Synopsis:
nslookup [-cmd { ... }] nick1 [[nick2] [nick3] ...]
Description:
This command will attempt to lookup a hostname, ip or using the internal
userhost queue, a nick on irc. As well you can lookup multiple
hosts|ips|nicks. A alias or cmd may be specified which is then performed
on each. If a failure occurs, then the failing name is returned, whereas
on success, the name and the associated ip's are returned. There is also
a hook which can be used only upon those nslookups without a -cmd.
Examples:
To nslookup a nick:
/nslookup nick
To nslookup multiple nicks:
/nslookup nick1 nick2 nick3
To nslookup a nick and perform a command:
/nslookup -cmd { echo $G $* } nick1
See Also:
dns userip ON NSLOOKUP

Some files were not shown because too many files have changed in this diff Show More