ACCESS

Usage: ACCESS [<nick>] [<#channel>]Usage: ACCESS <#channel> [<level>] <ADD|DEL|LIST|WIPE|COUNT|ENABLE|DISABLE> [<nick>]
ACCESS is used to control all channel access related functionalities.
ACCESS - Lists all channels you have access in.
ACCESS <nick> - Lists all channels the specified nick has access in. (Requires you to identify to the nick or be network operator.)
ACCESS <nick> <channel> - Tells you what access a given nick has to a given channel. (You need to have access in the channel or be an operator.)
If you specify a channel as first argument, it allows you to manage the channel's access lists. Valid levels are UOP, VOP, AOP, SOP, and MGR. The level can be omitted if you use the parameter ACCESS COUNT, which gives the number of entries in each access level list.
See the subcommands for details, as shown in the examples.Examples:
/access
/access #movies
/access #movies Jay
/helpserv access add
/helpserv access list
/helpserv access aop
You need channel access for most subcommands of this command, you will not be able to modify access lists that rank higher or equal to your own access level. The commands ACCESS LIST and ACCESS COUNT are available to all users who have access to the channel.
Note: This command replaces the service commands /CS UOP|VOP|AOP|SOP|MGR, /CS WHY, /CS ACC and /CS COUNT, as well as /NS LIST, and /NS LISTCHANS.

ACTION

Usage: ACTION <text>
This will preface any text with your nickname and in most cases use a different color for the message than a normal text color.
It is used to distinguish actions from speech. For instance, if your nick was 'John' and you typed "/action is going to watch TV" it would show up emphasized as "John is going to watch TV".Examples:
/action is hungry
Note: This command is an alias of the command ME, which usually is used because it is shorter and more convenient.
This is also a client-side command, so your client may not support it

ADMIN

Usage: ADMIN [<server name>]
Retrieves administrative information about the chat server you are currently using. Often provides an email address for the server administrator.
If the server name is omitted, then this command will provide information about the server to which you are connected and also show server administrators currently connected to it.Examples:
/admin
/admin irc.webmaster.com
/admin glass.*
This is a useful command for users who run into any problems on the chat network. The information listed with the admin command should provide at least one method for contacting someone who can help.

AKICK

Usage: AKICK <#channel> <ADD|DEL|LIST|WIPE> [<mask>] [<reason>]
This command is used to manipulate a channel's AKICK list. AKICKs are enforced by the server the moment a user matching an AKICK list entry joins the channel. The user will be kicked and the mask will be banned.Examples:
/helpserv akick add
/helpserv akick list
AKICKs are the best way to ban certain nick masks or known users, because ban lists tend to get wiped now and then, an AKICK sticks and is enforced on sight. However, you don't want to make the mask too general, as it may affect many users that were not at all involved.
Note: this command replaces the service command /CS AKICK.

AKILL

Usage: AKILL <nick|user@host> <reason> [<time>]
This will place a kline on all servers that are connected to your server, thus preventing someone from logging into the entire network. You can use the nick for a user who is currently on the chat network and the network will akill that user's address. You must include a reason for the command to work.
Note: If a server is split off when the akill is placed, it will not be present on that system. To get a list of akills on your server do a /STATS k and look for the lines that are prefixed with A: instead of K:. See rakill and unakill to remove an akill. Akills must end with either text, or the time parameter. If no time parameter is given, the akill will be placed indefinitely.Examples:
/akill Rachel flooding 30
/akill alumnus@nc-67-77-218-198.dyn.sprint-hsd.net spamming
An akill is a way of banning someone from the chat network. It is a last resort when warnings and kills did not keep the person from misbehaving. An akill works basically the same way that a channel ban works, except that it prevents someone from logging into the network rather than from just joining a channel.
See also: RAKILL

ATTACH

Usage: ATTACH <#channel> <description>Usage: ATTACH <password> <email address>
If the first parameter is a channel name, then this command attaches a new channel to your nick, thereby registering it. The channel must be unregistered and you must be op (see CMODE +o) in it. The description parameter is any string following the channel name and should contain a general idea of what the channel is about.
Note: The channel is attached to your nick directly, this means it does NOT need another password. If you specify a password, it will be added to the description and people will be able to read it in the channel info.
If the first argument is not a channel, then ATTACH tries to register the nick you are currently using. For that, you also need to specify an email address in order to verify the registration.
The nickname must not be registered, yet.Examples:
/attach #trivia a fun place to test your trivia knowledge
/attach #math a channel to discuss mathematics
/attach Fz5nr sandra@somedomain.com
If you plan to talk to a group of people regularly, you should register a channel in which to do it. Only in registered channels you can maintain access lists and place AKICKs for disturbing users. AOPs, SOPs, MGRs and the founder of a channel get operator status in it the moment they join.
In general, registration ensures that nobody else can change settings of your channel or steal it while you are not in the channel.
Note: This command replaces the servic command /CS REGISTER, and does NOT require you to specify a password.
It also replaces the service command /NS REGISTER, allowing you to register nicknames and channels with the same command.

AVATAR

Usage: AVATAR <avatar>
This is an alias for UPROP AVATAR and lets you change the avatar more easily.Examples:
/avatar cat
/avatar

AWAY

Usage: AWAY [<message>]
The system will automatically send this message to anyone trying to message you. The message will also show in your information if someone issues the command WHOIS on you. It is often used to tell people that you are away from your computer. If you no longer wish to be seen as away, then simply type /AWAY with no message and the away message will no longer be displayed.Examples:
/away I'm walking my dog, be back later.
/away
You can also use it if you are staying active but do not want to reply to private messages. For example, some people will set their away message to something like "Please talk to me in the channel, I am busy and not replying to private messages.".
Additionally, private messages can be blocked entirely, see CMODE +m.

BUDDY

Usage: BUDDY <#channel> <ADD|DEL|LIST|WIPE> [<nick>]
This command lets you manage the BUDDY list. The server will inform you when each of your buddies joins or leaves the chat network.Examples:
/helpserv buddy add
/helpserv buddy list
You can add the nicks of people you frequently chat with as buddies. But you might not want to make your buddy list too long, or you may be seeing too many messages about people logging on and off.
Before you can add a user to your buddy list, an authorization request will be sent to the user, which he can accept or decline. See also AUTH.
Note: buddy lists are similar to WATCH lists, however, they are associated with your registered nick and will remain intact even if you disconnect and reconnect to the network.

CFLASH

Usage: CFLASH <#channel> <message>
This will send a newsflash to all of the users in the specified channel who have UMODE +n set.Examples:
/cflash #Chat Welcome nikb to our SOP team.
This is mostly useful if you are running an event or meeting in a channel and want to add newsflashes about particular information that relates.

CHANSERV

Usage: CHANSERV <commands>
An alias for /msg chanserv so that you can send ChanServ commands with less typing.Examples:
/chanserv info #ConferenceRoom
See also CS as another alias.
Most ChanServ commands are deprecated and there exist direct server commands now to provide most of ChanServ's functionalities. See ACCESS, ACCESS, ATTACH, PROP CHANNEL, AKICK to name a few.

CHATOPS

Usage: CHATOPS <message>
Sends a server notice to all network operators that have UMODE +b set.Examples:
/chatops Where are we meeting?
Exactly how these are used can be determined by network policies, but while GLOBOPS are generally reserved for very important communications, CHATOPS generally have looser standards. More social chatter is acceptable and less vital questions can be asked there.
Only opers see these messages, so there is less need to worry about the content of the messages. Watching chatops should be voluntary, so that busy opers can stop watching them. Anything truly vital should be sent via GLOBOPS.

CK

Usage: CK <#channel>
This will kick all unregistered users from a channel. It will also set CMODEs +J and +R to only allow Java users and registered users back into the channel.Examples:
/ck #Egypt
Note: this is just an alias of the command CK.

CLEAR

Usage:
This will clear out your channel or private message window and history buffer so that any text will be erased.Examples:
/clear
Note: this is a client-side command and doesn't communicate with the server at all.

CLEARAKILLS

Usage:
This will remove all the global klines or akills from your server. This command does not affect any other servers.Examples:
/clearakills
It tends to be a good idea to remove akills after a while. The person it was set to ban may have either reformed or stopped trying to log in. Any other users who may have matched the ban coincidentally will not be able to log in and chat until the akill is removed.

CLONEKICK

Usage: CLONEKICK <#channel>
This will kick all unregistered users from a channel. It will also set CMODEs +J and +R to only allow Java users and registered users back into the channel.Examples:
/clonekick #Egypt
Note: the command CK is an alias for CLONEKICK.

CLOSE

Usage:
This command will close all unknown connections to your server. You can list those connections with "STATS U".Examples:
/close
You normally won't need to close these connections, but if your server is accumulating a large number of unknown connections, then you may want to clear them all off so that other users can join.
Note: some clients implement an own CLOSE command, which has nothing to do with the server command. If that is the case you need to tell the client to send the command to the server, often done with something like "/raw CLOSE".

CHANNEL MODE A

Usage: MODE <channel> +|-A A - Auditorium
Auditorium is designed to handle big events without flooding everyone with unimportant information based on the size of the channel, it works with +m and often with +M. It will hide the names of most of the people who cannot speak; it will show up to 20 of them. Anyone who can speak will be visible in the names list, and then a maximum of 20 users who cannot will be shown.
It will only show users who cannot speak if there are fewer than 20 people who can speak, and then it will show users who cannot speak until there are 20 visible people. When the channel is set -A the users will start to appear as they speak unless there is a small number of users, in which case they will massjoin.Privilege: server operatorExamples:
/mode #movies +A

CHANNEL MODE b

Usage: MODE <channel> +|-b [<nickname|nick!user@host>]b - Ban
Will ban the specified user from joining the channel. When used by itself with no hostmask it will list the bans that are in a channel. Valid hostmasks include nickname!user@host. When a user is banned his ability to speak in the channel is removed. You can use this in events to limit a persons ability to cause problems.Privilege: channel operatorExamples:
/mode #movies +b
/mode #movies +b bot*!*@*.offenderhost.com

CHANNEL MODE c

Usage: MODE <channel> +|-c c - Block colors
This mode will prevent colors from being sent to the channel. Messages that contain color codes will still go through, but the colors will be removed.Privilege: channel operatorExamples:
/mode #movies +c

CHANNEL MODE d

Usage: MODE <channel> +|-d d - Block nick changes
This mode will only allow 1 nickname change per user, from Guestxxxx to a nickname. It does not affect network operators. This will keep a channel from getting cluttered with nick changes. It is particularly useful in larger channels. You will probably want to set channels +d if you are having a moderated event.Privilege: channel operatorExamples:
/mode #movies +d

CHANNEL MODE e

Usage: MODE <channel> +|-e e - Block CTCPs
This will prevent CTCPs to the channel but will not prevent actions or CTCPs between individual users of the channel.Privilege: channel operatorExamples:
/mode #movies +e

CHANNEL MODE i

Usage: MODE <channel> +|-i i - Invite only
Users must be specifically invited to join using the INVITE command or may invite themselves if they have access to the channel.Privilege: channel operatorExamples:
/mode #movies +i

CHANNEL MODE j

Usage: MODE <channel> +|-j j - Java exception
This mode allows you to have only java clients and selected legacy IRC clients enter the specified channel. For this mode to take effect you must set a key. For IRC clients to enter the channel they must supply the key, or be invited into the channel.Privilege: channel operatorExamples:
/mode #movies +j
See also: CMODE +k

CHANNEL MODE J

Usage: MODE <channel> +|-J J - Java exception
This mode defines an exception for CMODE +R, which only permits registered users to join. With +J set as well, Java users can join even if they don't have a registered nickname.Privilege: channel operatorExamples:
/mode #movies +J
See also: CMODE +R

CHANNEL MODE k

Usage: MODE <channel> +|-k [<key>]k - Key
Sets the channel so only users who specify the channel's key (password) as the second parameter of the join command can enter the channel. If the key to the channel #CoolChat were bagel then to join one would use the command /JOIN #CoolChat bagel. Unlike passwords, keys are not case sensitive.Privilege: channel operatorExamples:
/mode #movies +k secret173
See also: CMODE +j

CHANNEL MODE l

Usage: MODE <channel> +|-l [<limit>]l - Limit
Limits the number of users that can be in the channel simultaneously. The limit can be set to something lower than the current user count, it only prevents new users from entering when the channel is full or overfull.Privilege: channel operatorExamples:
/mode #movies +l 20

CHANNEL MODE L

Usage: MODE <channel> +|-L L - Language filtering
When language filtering is enabled on the server one option is to give each channel the choice to enable this or not. Will prevent words on the filter list from reaching the channel either by the filter or censor rule as set by the administrative policy of the server.Privilege: channel operatorExamples:
/mode #movies +L

CHANNEL MODE m

Usage: MODE <channel> +|-m m - Moderation
Causes a channel to be moderated so only the operators and those users who are +v (voiced) can talk. UOPs cannot talk in moderated channels unless they are temporarily voiced or opped. Moderation is a good way to carefully control a channel.
If anyone starts causing problems you only need to remove their +v (ops should not be causing problems because they should be trusted, but if they do, then removing their status will fix things, although you might need to remove their entry from whichever op list they are on).
The downside to constant moderation is that there must be an op present at all time to voice new people or else they can't talk, and the channel may become temporarily unuseable. It also is tedious to voice every new user so that they can speak.
Although this can be accomplished by a bot. Moderation is usually reserved for channels that only wish to allow certain people to speak (events, lectures, etc.) or that wish to give different people the floor for a time (debates, storytelling, etc.).Privilege: channel operatorExamples:
/mode #movies +m

CHANNEL MODE M

Usage: MODE <channel> +|-M [<channel>]M - Moderation target
This mode is used in a forward moderated chat. If the channel is set to +m all the messages sent to the channel that cannot be viewed by other users will be sent to a +N channel that is specfied when the mode is set. +M and CMODE +N work together. The channel must be +m (moderated) for the messages to go to the receiving channel.Privilege: network operatorExamples:
/mode #event +M #questions
See also: CMODE +m and CMODE +N

CHANNEL MODE n

Usage: MODE <channel> +|-n n - No external messages
Only people in the channel can speak to the channel. Without +n any user can send a message to the channel and it will be seen in the channel.Privilege: channel operatorExamples:
/mode #movies +n

CHANNEL MODE N

Usage: MODE <channel> +|-N [<channel>]N - Moderation receiver
This command is set to a channel that is receiving moderated messages from a +mM channel, it is a good way of scanning questions when you have a special event. To use both +M and +N modes you must be an network operator and you must be a channel op in both channels. The channel must be +m (moderated) for the messages to go to the receiving channel.Privilege: network operatorExamples:
/mode #questions +N #event
See also: CMODE +m and CMODE +M

CHANNEL MODE o

Usage: MODE <channel> +|-o [<nick>]o - Channel operator
Gives the user whose nickname immediately follows the +o operator status in the channel. Channel operators are able to set the configuration of a channel with the exception of a very small quantity of server operator modes.Privilege: channel operatorExamples:
/mode #movies +o moonman

CHANNEL MODE O

Usage: MODE <channel> +|-O [<channel>]O - Overflow
If you set a user limit in the channel and have mode +O on, it will redirect the users in the second channel. To use this mode you must set the channel +l (limit), when the limit is reached the next user to join will be sent to the specified overflow channel.Privilege: channel operatorExamples:
/mode #movies +O
See also: CMODE +l

CHANNEL MODE p

Usage: MODE <channel> +|-p p - Private
Hides the channel in the channel LIST and WHOIS information, this is a good setting for channels that do not wish to have random people wandering in. It does not prevent anyone from joining, but it keeps the channel from being easily noticed.Privilege: channel operatorExamples:
/mode #movies +p
Note: This mode is equivalent to CMODE +s.

CHANNEL MODE r

CHANNEL MODE R

Usage: MODE <channel> +|-R R - Registered users only
When this mode is set the server will check to make sure that a user that is joining the channel has a registered nickname.Privilege: channel operatorExamples:
/mode #movies +R
See also: CMODE +J

CHANNEL MODE s

Usage: MODE <channel> +|-s s - Secret
Hides the channel in the channel LIST and WHOIS information, this is a good setting for channels that do not wish to have random people wandering in. It does not prevent anyone from joining, but it keeps the channel from being easily noticed.Privilege: channel operatorExamples:
/mode #movies +s
Note: This mode is equivalent to CMODE +p.

CHANNEL MODE t

Usage: MODE <channel> +|-t t - Topic
Sets the channel so that only channel operators can change the topic. Most channels will want to be +t so that only trusted people will be setting the topic. A topic represents the channel; it is one of the first things people will see about a channel when deciding whether to join or stay.Privilege: channel operatorExamples:
/mode #movies +t

CHANNEL MODE u

Usage: MODE <channel> +|-u u - Channel user
Sets a user to +u. He/she will be identified with a - in front of the nickname. While adding someone to the UOP list gives them certain abilities, moding them +u does not. However, it can be used as an indicator.
What it would indicate would be up to each channel to decide, a help channel might use it to show a guest helper, a chat channel might use it to show that the person was friends with one of the regulars, but not themselves around and trusted enough to have earned voice or ops.Privilege: channel operatorExamples:
/mode #movies +u Tessix

CHANNEL MODE U

Usage: MODE <channel> +|-U U - Channel knocks
When this mode is set and user tries to join the channel but fails due to a ban or other channel mode, it will send a knock to the channel operators telling them that a user is trying to join. This will allow the channel operators to INVITE that user into the channel.Privilege: channel operatorExamples:
/mode #movies +U

CHANNEL MODE v

CONNECT

Usage: CONNECT <connecting-server> <port> <destination-server>
Connects a server to another server. The servers at both ends of the connection being established must have defined each other properly in order for this command to succeed. The first server you type in is the split server, the second server is usually the hub server.Examples:
/connect server1.mynetwork.com 6667 server2.mynetwork.com
You can use this command to connect any split server with any server on the part of the network you are still connected to. However, unless the servers are configured to connect and one of them is a hub, it will not work.
You should be familiar with where the servers on your network usually connect before you try to connect two servers. Bad routing will create a slower network that is more likely to split.

CS

Usage: CS <commands>
An alias for /msg chanserv so that you can send ChanServ commands with less typing.Examples:
/cs info #ConferenceRoom
See also CHANSERV as another alias.
Most ChanServ commands are deprecated and there exist direct server commands now to provide most of ChanServ's functionalities. See ACCESS, ACCESS, ATTACH, PROP CHANNEL, AKICK to name a few.

DEOP

Usage: DEOP <#channel> [<nick>]
This will deop a user or yourself in a channel, but the mode change is done by the server, you need to have AOP or higher access to the channel to use this command. If no nick is given, it works on yourself.
It's particularly useful if you are not opped but need to deop someone else or yourself quickly.Examples:
/deop #mychannel Zorgor
deop #mychannel
See also CMODE +o and DEVOICE.
This replaces the service command /CS DEOP.

DETACH

Usage: DETACH <#channel|nick>
This lets you drop nicknames or channels you have registered with ATTACH before. Note, that this will clear all access lists of a channel, as it becomes unregistered.Examples:
/detach Flower18
/detach #hangout
This replaces the service commands /NS DROP and /CS DROP.

DEVOICE

Usage: DEVOICE <#channel> [<nick>]
This will devoice a user or yourself in a channel, but the mode change is done by the server, you need to have AOP or higher access to the channel to use this command on other nicks and VOP access to use it on yourself.
It's particularly useful if you are not opped but need to devoice someone else or yourself quickly.Examples:
/devoice #mychannel Zorgor
devoice #mychannel
See also CMODE +o and DEVOICE.
This replaces the service command /CS DEVOICE.

DIE

Usage:
This command will stop ConferenceRoom. Unless you are running ConferenceRoom as a service, it will not start up again. If you use this command by mistake, you can always go to the Web Configuration panel and start ConferenceRoom from the Home tab. If you do not have configuration access, you probably should be very careful using this command.Examples:
/die
DIE is a good way to close ConferenceRoom, because the program will make sure to close down neatly and save its current configuration. If you simply kill or stop ConferenceRoom from the operating system, you might lose your most recent changes.

EMBED

Usage:
This will embed a floating applet back into the browser.Examples:
/embed
This only works in the Java client.

FIELD

Usage: FIELD <#channel|nick> [<GET|SET>] <field> [<value>]
This command works simultaneously with the AdminServ FIELD command. Any FIELD added using AdminServ FIELD would then be SET with command. SET can either be used by a network operator or by a user, depending on the level of the FIELD you added.
The GET command just returns the field for the specified #channel or nick, if you specify '*' as field, then all fields are listed.Examples:
/field John get *
/field John set name John Doe
/field John get name
Note: The commands SET and GET are merely convenient shortcuts for this command.

FJOIN

Usage: FJOIN <nick> <#channel>
This will force the user specified by nickname into the given channel.Examples:
/fjoin Nicole #kitchen
This can be a way to send someone who needs help to the proper channel, especially if they are having trouble joining channels. However, it can be disorienting to find yourself in a channel you didn't intentionally join. It is often a good idea to inform the user of what you are going to do.

FLOAT

Usage:
This will launch your java applet onto your desktop.Examples:
/float
This can be handy when you want to position the chat client without the extra bulk of the browser.

FOLDER

Usage: FOLDER <list|select|stat|create|del|delete|undel|move>
This command allows accessing the folders for memos you have received.Examples:
/folder list
Note: this command replaces many MemoServ functionalities, see also MEMO and READ to send and read memos.

FREEZE

Usage: FREEZE <#channel|nick> <reason>
The FREEZE command is used to (mostly temporarily) take away most access rights to a channel or nick. If used on a channel, it will disable all access lists of the channel. Users can still join, but the channel will behave as if it wasn't registered.
If used on a nick name, then the user with that nick name can't use any of his access in channels or use ATTACH on the nick.Examples:
/freeze #Hell
/freeze Francisca
Freezing a nick should be a temporary punishment in most cases, it's useful if an abusive user caused trouble in many channels he has access in. Or if a whole channel has been violating network policies.
Note: The properties FROZEN, FREEZEBY and FREEZETIME will be added for the channel or nick when this command is issued.

FTRANSFER

Usage: FTRANSFER <#channel> <nick>
Used to transfer channel ownership to another nick. Unlike TRANSFER, this command forces the transfer and doesn't require the user to finish the process after receiving a memo.Examples:
/ftransfer #BakerStreet221B MrsHudson

FURL

Usage: FURL <nick> <URL> [<frame>]
This command will force a user's browser to open and view an URL. This will only work on java users.Examples:
/furl John http://www.webmaster.com/update.htm
/furl John http://www.webmaster.com/update.htm frame2
This can also be disorienting, and it is best to warn users of what you are doing. However, it can be useful for a presentation or to send users to a help site.

GET

Usage: GET <nickname> <field>
This command allows you to get specific field information. Fields store information that is associated with a nickname and allow for a variety of storage and display options.Examples:
/get bill avatar
See also: FIELD

GFLASH

Usage: GFLASH <message>
This command will send a System Maintenance NewsFlash Message on the entire network. The users will not know the nickname of the sender of this NewsFlash message. You must be a Services Administrator to use this command. All users will see this message regardless of their modes.Examples:
/gflash We are restarting several servers, the downtime will be short.
See also MFLASH for a local version of this command.

GLOBOPS

Usage: GLOBOPS <message>
Sends a message to all opers that have UMODE +g set. This command is usually used for network-wide communication between opers for details that concern the entire network.Examples:
/globops The event is going to start in ten minutes.
GLOBOPS should be reserved for important communications that most opers will need to see. If globops get too cluttered, then it will make it difficult for opers to do other things and read globops. Less important communciations can be sent through CHATOPS, which some opers may choose not to read.

GNOTICE

Usage: GNOTICE <message>
Any notice that is sent from the server to operators are sent in the form of global notices. Operators can elect to not view Global Notices by unsetting UMODE +G.Examples:
/gnotice We updated the policies for operators, please read the new version.

HelpServ Topics

Will give you help information on a specific command.
Please note: If you request help that is not in this list your help request will go to all the operators that have UMODE +h set.

HELPSERV

Usage: HELPSERV <command>
This will give the HelpServ help file for a command if a server command is sent, if HelpServ has no information then the message is sent to everyone who has set UMODE +h, so that they can help the user.Examples:
/helpserv join
/helpserv Where can I go for help?
The commands HELP, HELPSERV, HS are synonymous.

HIDETICKER

Usage:
This command will prevent the scrolling message at the bottom of the Java client from scrolling. The scrolling message is called the ticker.Examples:
/hideticker
This command may be disabled by the person running the server. But if it works, then it will stop the ticker at whatever point you send the command. The SHOWTICKER command will reverse this and start the ticker scrolling again.

HS

Usage: HS <command>
This will give the HelpServ help file for a command if a server command is sent, if HelpServ has no information then the message is sent to everyone who has set UMODE +h, so that they can help the user.Examples:
/hs join
/hs Where can I go for help?
The commands HELP, HELPSERV, HS are synonymous.

IDENTIFY

Usage: IDENTIFY [<nick>] <password>
You can use this command to identify for your current nickname by sending just your password or for any specified nickname by sending that nick and its password.Examples:
/identify 3iT4WwB2mI
/identify Akinwale Bc93w8UrSH
You can also specify the password directly when changing your nick, see NICK.

INFO

Usage: INFO [<server|#channel|nick>]
Displays information about a server, channel or nick. If no parameter is specified, the information returned is about the server you are on.
For servers, this information includes up-time, address, version, and how to connect to them.
While for channels, it'll display data like the founder of the channel, the time of its registration, the topic, etc..
If a nickname is specified, then the info will include time of registration, last time the nick was online, and possibly email address and similar fields, if the user chose to publically display them.Examples:
/info
/info #metal
/info Fibonacci
/info arena.webchat.org
If you need any help with ConferenceRoom and are not sure what version you are running, use the info command. You can also use it if you have forgotten what web address to use to connect.

INVITE

Usage: INVITE <nick> #<#channel>Usage: INVITE #<#channel>
This command is used to invite people to join a channel. The server will send a message to the user, inviting them to join and allowing them to enter through CMODE +i and other restrictive channel modes. This is the only way to let someone into a channel that is +i, if they do not have at least UOP access in it.
If only a channel is given as parameter, then you invite yourself into that channel. This requires access to the channel (see ACCESS for details) and is mostly useful when a channel mode or ban list entry prevents you from joining normally.Examples:
/invite residue #support
/invite #island
In general, if you have an invite only channel, this is how you will let people join. You generally only want to invite people you know, because random invites are usually considered rude or even synonymous to spamming.
Note: the syntax with only one channel parameter to invite yourself replaces the service command /CS INVITE.

ISON

Usage: ISON <nick> [<nicks>]
Will check to see if one or more of the nicknames are currently logged into the chat network. It will report back all of the specified nicks that are online.Examples:
/ison Surel
/ison malakian scott-s kAyleigh
This is fast way to check if a nick is in use. You could use the WHOIS command, but then you would also get multiple lines of information you might not care about, and could only check for one nick at a time.

JOIN

Usage: JOIN <#channel>
The join command lets you enter a channel. This is the first thing you want to do when you connect to a server. You always have to place a # in front of the channel name. Normally the # symbol is considered to be a part of the channel's name. The maximum channel name width is 60 characters.Examples:
/join #music
Channels are the virtual environments in which people chat. When you are in a channel, you see all of the text sent to it, as does everyone else present. While you can have private conversations with individuals who are in the same channel as you are, or even with people who are elsewhere if you know their nicknames, most chat takes place in channels.
You can be in multiple channels at the same time, but it can become confusing. Some networks may restrict the number of channels you can be in simultaneously. It is generally best to be in a very small number of channels that are moderately active. Java users can also look at the NEWJOIN command.

KICK

Usage: KICK <#channel> <nick|mask> [<reason>]
Used to force users to leave a channel. The reason parameter is not required, but if specified will be sent to the client as part of the kick. Only users who are opped (CMODE +o) in the channel can kick others out.
You can use a wildcard mask instead of a nick name and thus kick many matching users at once, this can be useful to either empty a channel entirely or kick all users with a certain ident or host.Examples:
/kick #webmaster Phillip Don't flood this channel.
/kick #panama bot* We don't like bots.
/kick #panama *!*@*.cloning-host.com Cloning.
The channel's ops may kick anyone for any reason, but this command should be reserved for people who are causing problems in the channel. In general, channels that kick frivolously become less popular. It is good to put an explanation of the kick in the command, because it helps the person being kicked learn how to behave acceptably in the future.
Note: If used as "/KICK <#channel> *", this command replaces the service comand /CS MKICK.

KILL

Usage: KILL <nick> [<reason>]
Used to forcibly disconnect someone from the server. This is usually used when someone is rude or is being disruptive. Global operators can kill users who are on any server on the network.Examples:
/kill Jamie spamming

KLINE

Usage: KLINE <user@host> <reason> [<time>]
Klines prohibit users from logging on to the server. This is used normally to restrict access from those that have been disruptive. To unkline someone you must either do it through the control panel or use the UNKLINE command. You can use wildcards while creating a ban, though you want to be careful not to make the kline more prohibitive than needed.
The second example is a site ban and will prohibit anyone from that domain from using the server. Care should always be used when placing klines. Klines work in a similar way as channel bans, except that they ban people from the server instead of from a channel.Examples:
/kline Rachel flooding 30
/kline alumnus@nc-67-77-218-198.dyn.sprint-hsd.net spamming
See also AKILL.

LFLASH

Usage: LFLASH <message>
This command will send a local NewsFlash Message on your server. The users will not know the nickname of the sender. See NFLASH for sending network-wide newsflashes. Only users with UMODE +n set will see newsflashes.Examples:
/lflash Greetings, special announcement...
See also NFLASH and CFLASH.

LINKS

Usage:
This command will show all the servers currently linked together on the network.Examples:
/links
If there is lag between two servers, you can use the links command to determine the path between them. Then you can test each link to see which is causing the lag. This is useful if you intend to reroute servers, SQUIT a leaf off of a hub and connect it to a different hub. Or disconnect two hubs and reconnect one to another hub.
Normal users can also use the links command to find server names to connect to or to connect to servers closer to the servers their friends are on.

LIST

Usage: LIST [<#channel mask>]
Shows all the public channels on the server. You can set a mask to limit the number of channels that are returned, in the example below we ask for any channels that start with the word support. Private or secret channels will not show up on the list.Examples:
/list #support*
The channel list may be very large, depending on the network. You can use the command LUSERS to see how many channels are on the network. The list command will take some time to display.

LOAD

Usage:
This command is for Java users only. It allows the user to load various available management/control panels. All the Panels are case sensitive.Available Panels:
IgnoreList - User Ignore panel
NickServPanel - Services Nickname management panelMemoServPanel - Services Memo services panel
ChanServPanel - Services Room management panel
OpPanel - Room control panel
ImagePanel - Images/picture panel
WhoCard - Whois information panel
AvatarPanel - Avatars: image/icon representing a user
BuddyList - Watch/notify management list panelExamples:
/load NickServPanel
/load OpPanel
/load BuddyList
The panels give you an easier way to send commands. They are simple graphical user interfaces to make chatting easy. You do not have to remember the exact commands, you can just push the button on the panel that pops up. If any information is needed, it will generally prompt you for it. You can close a panel when you are done with it and reload it later.

LOCOPS

Usage: LOCOPS <message>
Sends a notice to all network operators who are on the same server and have UMODE +g set.Examples:
/locops Where are we meeting?
Locops are very useful for server-specific communications. For example, the opers for a particular server should have some idea of which servers connect best with their server. If the server needs to be routed, it is best to discuss it with the opers of that server. Some servers may allow locops to be used for chat or less important communications, much as CHATOPS are.
This can help the opers of a server get to know each other better, which can be useful since they may need to work together at times. Opers should watch locops while on duty, so they should not be allowed to get too cluttered with chat, preventing opers from being able to concentrate on the things they are working on.

LUSERS

Usage: LUSERS [*] [<server>]
Displays information about the number of users currently logged on to your server and the network. If you don't specify a server name, it will provide information of the server you are logged into. If you use it with a * it will get the lusers information from the target server.
If you designate a target server with no asterisk, then it will return the number of users that your server shows at the current time.Examples:
/lusers
/lusers * arena.webchat.org
/lusers arena.webchat.org

MARK

Usage: MARK <nick> <reason>
The MARK command is used to mark a nick name with a reason why it was marked, this is useful if a user has been abusive and an operator wants to make a note of the offense. Other operators encountering the nick name may then check the properties of the nick and will see the previous problem(s) with that user.Examples:
/mark Thomas Seen flooding and cloning.
See also PROP NICK MARKED.

ME

Usage: ME <text>
This will preface any text with your nickname and in most cases use a different color for the message than a normal text color.
It is used to distinguish actions from speech. For instance, if your nick was 'John' and you typed "/action is going to watch TV" it would show up emphasized as "John is going to watch TV".Examples:
/me is hungry
Note: This command is an alias of the command ACTION, which usually is used less.
This is also a client-side command, so your client may not support it

MEMO

Usage: MEMO <nick|#channel> [MTARGET UOP|VOP|AOP|SOP|MGR [UOP|VOP|AOP|SOP|MGR]] [MTOPIC <topic> MBODY] <message>
If a nickname is specified, then this will send a memo to the given nick. The nickname must be registered and you must be using a registered nickname. The receiving user will be told that a new memo was sent the next time he logs on, and can then use READ to read it.
You can also specify a topic of the memo, this is done by adding MTOPIC <topic> MBODY before the memo. Note, that the MBODY keyword is needed to mark the end of the topic and the beginning of the memo.
With a channel parameter, the memo is sent to all users on the access lists of the channel. You can narrow the target group down further by specifying the MTARGET keyword, followed by a list of access lists. However, if you use MTARGET, then MTOPIC and MBODY are also required.Examples:
/memo George mtopic The new plans mbody Hey, try to catch me online, we need to discuss the new plans.
/memo #staff Happy new year, everybody.
/memo #staff mtarget sop mgr mtopic Topic-lock mbody The topic is not locked and can only be changed by users with SOP and MGR access.
Note: this command replaces the "/memoserv send" command. See also FOLDER and READ to access memos.

MEMOSERV

Usage: MEMOSERV <commands>
An alias for /msg memoserv so that you can send MemoServ commands with less typing.Examples:
/memoserv help
See also MS as another alias.
Many functionalities of MemoServ can be accessed through server commands now, see FOLDER, MEMO, and READ.

MFLASH

Usage: MFLASH <message>
This command will send a local System Maintenance NewsFlash Message on the local server. The users will not know the nickname of the sender of this NewsFlash message. You must be a Services Administrator to use this command. All users will see this message regardless of their modes.Examples:
/mflash This server is going down for an upgrade in 5 minutes.
Use this whenever you need to send a notice to all local users about maintenance issues. It will appear differently than a normal notice, so that normal users cannot fake network notices. See also GFLASH.

MKILL

Usage: MKILL <IP address|hostmask|#channel> <reason>
This command will mass kill users from the same IP address, hostmask or channel. It is normally used when a large quantity of users from the same address or channel need to be removed from the server.Examples:
/mkill pp23.ntsvr4-2.tor.idirect.com cloning
/mkill #bots botnet channel
This is especially useful if the users are changing their nicks because it allows you to kill by address. It is a good idea to check exactly who will be killed by this command before you send it by using the WHO command.

MOTD

Usage: MOTD [<server name>]
Display the current Message of the day for the server that you designate, if you leave the server field blank it will return with the current server you are logged into. Generally this field has administrative information and the rules for that server.Examples:
/motd
/motd arena.webchat.org
/motd arena.*
You should be familiar with the contents of the message of the day for the server you are using. Despite its name, a motd may not change often, but it may change to reflect network changes. Often a motd will include a list of help channels, and that may change as new channels are added.

MOVE

Usage: MOVE <nick> <#channel>
This command will move a user to another channel. It is very similar to the FJOIN command. If the user is in exactly one channel at the time of the move then he will be forced out of that channel and join the specified channel. However, if he is in more than one channels, MOVE is equivalent to FJOIN.Examples:
/move BlackSheep #letstalk
This is primarily useful to force users to go to help channels when they need it. If the user is also unintentionally doing something harmful, it will isolate the user until he/she can be educated.

MS

Usage: MS <commands>
This is an alias for /msg memoserv so that you can send MemoServ commands with less typing.Examples:
/ms list
Many functionalities of MemoServ can be accessed through server commands now, see FOLDER, MEMO, and READ.

MSG

Usage: MSG <nick|#channel> <message>
This command will allow you to send a private message to a specific user or send a message to an entire channel.Examples:
/msg Roseanna All I wanna do when I wake up in the morning is see you eyes.
/msg #home Good morning, everybody.
Note: this is a client-side command, so your client might not implement it. See PRIVMSG for the server equivalent.

NAMES

Usage: NAMES <#channel>
Show all of the nicknames that are in the specified channel. If you are a server operator and no channel is specified then it shows the nicks of all the users on the network. If you are not in a channel and try to get the names list, users who have UMODE +i set will not show up, but if you are in the channel then you can get a complete list.Examples:
/names #webchat
Some clients do not show the users in a channel, and so you can use this command to list them after joining the channel. Listing all of the users on the network is rarely useful to do, and is limited to opers to prevent normal users from sending annoying messages to people they do not know.

NEWJOIN

Usage: NEWJOIN <#channel>
This command is for Java users only, it will allow the Java user to join additional channels, without leaving any channels they are in.Examples:
/newjoin #webchat
Note: this is a client command.

NFLASH

Usage: NFLASH <message>
This command will send a global NewsFlash Message on the network. The users will not know the nickname of the sender. The users need to have UMODE +n set to see newsflash messages.Examples:
/nflash Greetings, special announcement.
/nflash <a href=http://www.webchat.org> Visit our Network URL
This is a useful way to send messages that will be noticed. However, since it only shows to people who are +n, if the message is very important you may wish to send it another way. See MFLASH.

NICK

Usage: NICK <new nick> [<password>]
This command will change your nickname to a new one that you select. This will update all the channels that you are on. The example below would change your nickname to lucky. Nicknames are limited to 30 characters.
You can specify the password for your nick directly or use the IDENTIFY command before you use NICK.Examples:
/nick Harry
/nick Harry ei0fvvHe7a
Your nickname is the first thing that other people will notice about you. It is your name and your identity on the chat network. You should try to pick one that you are happy with. You may have to try a few before finding one that someone else hasn't registered yet.
You can change your nick to reflect your mood or to show that you are away (e.g. /nick Lucky-away), this is often done in combination with the AWAY command.

NICKSERV

Usage: NICKSERV <command>
This is an alias for /msg nickserv so that commands can be sent with less typing.Examples:
/nickserv info Jennifer
See also NS as another alias for /ms nickserv.
Many NickServ commands can now be accessed with direct server commands, such as INFO, IDENTIFY, ACCESS and others.

NOTICE

Usage: NOTICE <nick|#channel> <message>
Sends a message into a channel or to a specific user. Usually reserved for important messages.Examples:
/notice #webmaster Check out our new web page.
/notice Phil What time is the meeting?
Notices are much like messages (see PRIVMSG), but notices may be easier to notice for some users. Also no bot (program that looks like a person on the chat network but only replies automatically to set commands) should ever reply to a notice. Bots reply to messages and send notices, this prevents the possibility of an infinite loop between two bots.

NS

Usage: NS <command>
This is an alias for /msg nickserv so that commands can be sent with less typing.Examples:
/ns info Jennifer
See also NICKSERV as another alias for /ms nickserv.
Many NickServ commands can now be accessed with direct server commands, such as INFO, IDENTIFY, ACCESS and others.

OP

Usage: OP <#channel> [<nick>]
This will op yourself or a user in a channel, but the mode change is done by the server, you need to have AOP or higher access to the channel to use this command. If no nick is specified, it will op yourself.
It's particularly useful if you are not opped but need to quickly op someone else or yourself.Examples:
/op #mychannel Zorgor
op #mychannel
See also CMODE +o and VOICE.
This replaces the service command /CS OP.

OPER

Usage: OPER [<nick> <password>]
This command will grant you status as a network operator for the server you are on. This gives you access to all the operator commands on that server.
If no parameter is given, then it will list the operators on the server you are on. This may be useful if you have an important problem or need assistance with abusive users.Examples:
/oper
/oper mike 9U7gh3
Despite having an oper definition configured into the server, you will not appear to be an oper or have access to any of the oper commands until you actually oper up. This command puts you on-duty and marks you as an oper. To de-oper you can use /UMODE -o.
In order to oper you must have an oper definition, your mask must match, you must put in the nick that is specified in your oper definiiton, and you must put in the correct case sensitive password. These are required to make sure that only the correct users can oper.

PART

Usage: PART <#channel> [<message>]
The part command has you leave a channel. The other people in the channel will see the message if you send one. The example below would make you leave the channel #webmaster.Examples:
/part #movies
/part #movies see you today
Note: the server configuration may surpress the display of the part message. This is because part messages, just like QUIT messages, can easily be abused to spam or annoy other users.

PASS

Usage: PASS <password>
The PASS command has a similar functionality as the IDENTIFY command, you can use PASS with your nick password and it will be used when you change your nick to it.Examples:
/pass UluqcoiRhC
This is a good way to identify for the nick you are using. It requires less typing than the normal method so it is easier and you are less likely to make a typo. It is important to send passwords securely so that you do not accidentally send your password to another user.

PLOG

Usage: PLOG <ON|OFF|STATUS>] [<password>]
The PLOG command starts or stops personal logging. In order to start it, you must set it to ON and specify a password. Specifying OFF on its own will stop logging, and STATUS will report the current state of logging, this is equivalent to not specifying any parameters.Examples:
/plog
/plog on f71aLg
/plog off
After disabling or disconnecting from the server, the log will be sent in an email to the address associated with your nickname. The log will be encrypted with the password you specify. You can also access it online, instructions on how to do that will be shown when you turn personal logging on.
The idea of server-side logging is to make it possible to prove the validity of a log, because the server signs the log digitally, making it possible to check whether the log was altered.

PRIVMSG

Usage: PRIVMSG <nick|#channel> <message>
This command will allow you to send a private message to a specific user or send a message to an entire channel.Examples:
/privmsg Roseanna All I wanna do when I wake up in the morning is see you eyes.
/privmsg #home Good morning, everybody.

PROP

Usage: PROP <nick|#channel> [<*|property>] [<value>]
This command allows inspecting and changing or all properties for channels and nicknames. If no value is specified, the server only prints the value of the property. You can use '*' as property parameter to see all properties of the channel or nickname.
See PROP NICK and PROP CHANNEL for more information.Examples:
/prop mark language en
/prop #lobby joinmute 5
/hs prop nick
/hs prop channel

Channels contain a variety of properties, some read-only, others read-write. Some duplication of functionality is present, in that PROP commands can be used to change certain attributes that were previously only changeable by commands.

CHANNEL PROPERTY: AUDIT

Usage: PROP <#channel> AUDIT [<ON|OFF>]
The AUDIT property can be set by managers and the founder of a channel, it allows you to monitor all relevant changes to channel settings.
If set to ON, every property change in the channel will cause the server to send a memo to all managers and the founder, which includes details about the op who changed the property and when. Default is OFF.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia audit
/prop #Philadelphia audit on
/prop #Philadelphia audit off

CHANNEL PROPERTY: AUTOVOICE

Usage: PROP <#channel> AUTOVOICE [<ON|OFF>]
If the AUTOVOICE property is set to ON, then every user joining the channel will be voiced by the server. Default is OFF.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia autovoice
/prop #Philadelphia autovoice on
See also: CMODE +v

CHANNEL PROPERTY: CHECKAGE

Usage: PROP <#channel> CHECKAGE [<ON|OFF>]
If CHECKAGE is set to ON, then all users need a non-zero age set in their AGE property in order to join. Default is OFF.
Note, that this does not require or check a certain age, it only checks whether the property is set.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia checkage
/prop #Philadelphia checkage on
/prop #Philadelphia checkage off
See also: PROP NICK AGE, PROP CHANNEL RATING

CHANNEL PROPERTY: CLOSETIME

Usage: PROP <#channel> CLOSETIME
If a channel was closed, the CLOSETIME property contains the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when it was closed.Privilege: operatorAttribute: readExamples:
/prop #Philadelphia closetime
See also: PROP CMODE CLOSED and PROP CMODE CLOSEBY

CHANNEL PROPERTY: CREATION

Usage: PROP <#channel> CREATION
The CREATION property is the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when the channel was created.Privilege: userAttribute: readExamples:
/prop #Philadelphia creation

CHANNEL PROPERTY: DESC

Usage: PROP <#channel> DESC [<description>]
The DESC property carries a short description of the channel, it will be set to the description given when you ATTACH a channel to your nickname, but can be changed later on by simply setting it to something else.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia desc
/prop #Philadelphia desc my favourite channel!
See also: ATTACH

CHANNEL PROPERTY: FREEZEBY

Usage: PROP <#channel> FREEZEBY
The FREEZEBY property holds the name of the operator who froze the channel.Privilege: operatorAttribute: readExamples:
/prop #Philadelphia freezeby
Note: this property is only set if the channel is frozen, see PROP CHANNEL FROZEN.

CHANNEL PROPERTY: FREEZETIME

Usage: PROP <#channel> FREEZETIME
The FREEZETIME property tells you when the channel was frozen.Privilege: operatorAttribute: readExamples:
/prop #Philadelphia freezetime
Note: this property is only set if the channel is frozen, see PROP CHANNEL FROZEN.

CHANNEL PROPERTY: FROZEN

Usage: PROP <#channel> FROZEN
The FROZEN property is set if a channel was frozen and states the reason for the freezing.Privilege: operatorAttribute: readExamples:
/prop #Philadelphia frozen
See also PROP CHANNEL FREEZEBY and PROP CHANNEL FREEZETIME.

CHANNEL PROPERTY: KEY

Usage: PROP <#channel> KEY [<key>]
The KEY property contains the key that is set for the channel, if CMODE +k is set.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia key
/prop #Philadelphia key jnLtT5OeGa
/prop #Philadelphia key :
Note: in order to unset the key with PROP, you need to specify a ':' as parameter, to set the key to an empty string.

CHANNEL PROPERTY: LASTJOIN

Usage: PROP <#channel> LASTJOIN
The LASTJOIN property is the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of the last time someone joined the channel.Privilege: userAttribute: readExamples:
/prop #Philadelphia lastjoin

CHANNEL PROPERTY: MARKTIME

Usage: PROP <#channel> MARKTIME
If a channel was marked, the MARKTIME property contains the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when it was marked.Privilege: operatorAttribute: readExamples:
/prop #Philadelphia marktime
See also: PROP CMODE MARKED and PROP CMODE MARKBY

CHANNEL PROPERTY: MEMOLEVEL

Usage: PROP <#channel> MEMOLEVEL [<UOP|VOP|AOP|SOP|MGR>]
The MEMOLEVEL property allows to specify what level of access is needed in a channel in order to send memos to all users on a certain access list of it.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia memolevel
/prop #Philadelphia memolevel aop
See also: MEMO

CHANNEL PROPERTY: MODELOCK

Usage: PROP <#channel> MODELOCK [<modes>]
The MODELOCK property lets you specify a set of modes that are always enforced by the server. This includes set and unset modes, for instance, if you set +t-i as MODELOCK, then the mode 't' will be set if someone tries to unset it and the mode 'i' will be unset if someone tries to set it.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia modelock
/prop #Philadelphia modelock +tR-z
/prop #Philadelphia modelock -t
/prop #Philadelphia modelock +i
See also: CMODE

CHANNEL PROPERTY: OPGUARD

Usage: PROP <#channel> OPGUARD [<ON|OFF>]
The OPGUARD property specifies whether a user has to be added to an access list in order to be made operator in the channel. If OPGUARD is set to ON, then you can't set CMODE +o for a user who isn't at least AOP of the channel.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia opguard
/prop #Philadelphia opguard on
See also: CMODE +o and ACCESS

CHANNEL PROPERTY: OVERFLOW

CHANNEL PROPERTY: POLICY

Usage: PROP <#channel> POLICY [<CLOSED|OPEN>]
In a channel with an OPEN policy, every user can add himself to the UOP access list. In CLOSED channels (the default), this is not possible.
This behaviour is intended for channels that offer a type of mailing list, it may send channel memos with updates and information, and all UOPs will receive those memos.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia policy
/prop #Philadelphia policy normal
/prop #Philadelphia policy open
Note: An OPEN policy does not lower security in a channel, because AKICKs placed in OPEN channels can not be overridden by self-invitation from self-added UOPs.

CHANNEL PROPERTY: PEAKUSERS

Usage: PROP <#channel> PEAKUSERS
The PEAKUSERS property contains the highest number of users seen in the channel.Privilege: userAttribute: readExamples:
/prop #Philadelphia peakusers

CHANNEL PROPERTY: REJOINTRACK

Usage: PROP <#channel> REJOINTRACK [<seconds>]
The REJOINTRACK property lets you set the number of seconds a user must wait before he/she can rejoin the channel after parting it. The maximal value is 60 seconds.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia rejointrack
/prop #Philadelphia rejointrack 3

CHANNEL PROPERTY: RESTRICT

Usage: PROP <#channel> RESTRICT [<ON|OFF>]
If RESTRICT is set to ON, then only users with channel access can join the channel, everybody else will get kicked and banned by the server on sight. Default is OFF.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia restrict
/prop #Philadelphia restrict on
/prop #Philadelphia restrict off

CHANNEL PROPERTY: SUBJECT

Usage: PROP <#channel> SUBJECT [<keywords>]
The SUBJECT property contains keywords that have something to do with the channel, you can set these to describe your channel. It also enables users to use /LIST -S= to list all channels containing the specified keyword.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia subject
/prop #Philadelphia subject hollywood cusack film

CHANNEL PROPERTY: TOPICBY

Usage: PROP <#channel> TOPICBY
The TOPICBY property contains the nickname of the user who set the topic of the channel.Privilege: userAttribute: readExamples:
/prop #Philadelphia topicby
See also: PROP CHANNEL TOPIC and PROP CHANNEL TOPICTIME

CHANNEL PROPERTY: TOPICLOCK

Usage: PROP <#channel> TOPICLOCK [<OFF|UOP|VOP|AOP|SOP|MGR>]
The TOPICLOCK property makes it possible to allow topic changes only for users with high enough access in the channel. For instance, if set to AOP, then only users with AOP, SOP or MGR access to the channel can change the topic.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia topiclock
/prop #Philadelphia topiclock aop
See also: TOPIC

CHANNEL PROPERTY: USERMSGSPERSEC

Usage: PROP <#channel> USERMSGSPERSEC [<limit>]
The USERMSGSPERSEC property lets you set a maximum number of messages a user can send per second.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia usermsgspersec

CHANNEL PROPERTY: USERS

Usage: PROP <#channel> USERS
The USERS property contains the number of users currently in the channel.Privilege: userAttribute: readExamples:
/prop #Philadelphia users

CHANNEL PROPERTY: USERSPERIP

Usage: PROP <#channel> USERSPERIP [<limit>]
The USERSPERIP property lets you set a maximum number of users that may share an IP in a channel. A value of 2-3 is usually a good setting. However, in the case of an event that attracts users from a certain netcafe or a similar shared connection, you probably want to raise or disable this value.Privilege: userAttribute: read-writeExamples:
/prop #Philadelphia usersperip
/prop #Philadelphia usersperip 3

Nicknames contain a variety of properties, some read-only, others read-write. Some duplication of functionality is present, in that PROP commands can be used to change certain attributes that were previously only changeable by commands.
Possible nick properties are:

See also UPROP for a more convenient way to change your own properties.

NICK PROPERTY: AGE

Usage: PROP <nick> AGE [<age>]
As you would expect, this property lets you specify your age in years, you can choose to make this piece of information available to anyone with PROP NICK SHOWAGE, otherwise it won't show to anyone else.
The age specified here will be taken into account in channels that have a certain rating set, some channels may even require you to specify an age with this property, see PROP CHANNEL AGECHECK for that option.Privilege: userAttribute: read-writeExamples:
/uprop age
/uprop age 31
/uprop age 19
See also: PROP NICK SHOWAGE, PROP NICK CONTENT, PROP CHANNEL RATING, PROP CHANNEL AGECHECK

NICK PROPERTY: AIM

Usage: PROP <nick> AIM [<AIM-account>]
The AIM property allows you to specify your AIM account, if you want other users to be able to contact you on AIM.Privilege: userAttribute: read-writeExamples:
/uprop aim
/uprop aim Ewok2107

NICK PROPERTY: AUTOPLOG

Usage: PROP <nick> AUTOPLOG [<ON|OFF>]
The AUTOPLOG property lets you specify whether or not to enable personal logging each time you connect and use your registered nickname. If enabled, it will make sure that logging starts the moment you identify to your nick. Default is OFF.Privilege: userAttribute: read-writeExamples:
/uprop autoplog
/uprop autoplog on
See also: PLOG

NICK PROPERTY: AUTHBUDDY

Usage: PROP <nick> AUTHBUDDY [<AUTHORIZE|DECLINE>]
With the AUTHBUDDY property you can control what happens when someone tries to add you to a buddy list. DECLINE immediately declines all requests, while AUTHORIZE sends you an authorization request which you can accept or decline.Privilege: userAttribute: read-writeExamples:
/uprop authbuddy
/uprop authbuddy allow
/uprop authbuddy authorize
See also: AUTH

NICK PROPERTY: AUTHCHAN

Usage: PROP <nick> AUTHCHAN [<ALLOW|AUTHORIZE|DECLINE>]
With the AUTHCHAN property you can control what happens when someone tries to add you to a channel access list. ALLOW and DECLINE immediately allow or decline the request respectively, while AUTHORIZE sends you an authorization request which you can accept or decline.Privilege: userAttribute: read-writeExamples:
/uprop authchan
/uprop authchan allow
/uprop authchan authorize
See also: AUTH

NICK PROPERTY: AVATAR

Usage: PROP <nick> AVATAR [<avatar>]
The AVATAR property lets you set an avatar. How this property will be interepreted is client-dependent. The java client shows a small icon next to the user.Privilege: userAttribute: read-writeExamples:
/uprop avatar cat

NICK PROPERTY: AWAY

Usage: PROP <nick> AWAY
The AWAY property is set if the user is away. The value is the away message for the user. You can set it with the AWAY command.Privilege: userAttribute: readExamples:
/uprop away

NICK PROPERTY: AWAYTIME

Usage: PROP <nick> AWAYTIME
The AWAYTIME property is set if the user is away. The value is the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when the user used the AWAY command.Privilege: userAttribute: readExamples:
/uprop awaytime

NICK PROPERTY: CAPAB

Usage: PROP <nick> CAPAB
The CAPAB property can carry certain capability information, which is set by the server.Privilege: userAttribute: readExamples:
/uprop capab

NICK PROPERTY: CONNECTTIME

Usage: PROP <nick> CONNECTTIME
The CONNECTTIME property is the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when the client connected to the server.Privilege: userAttribute: readExamples:
/uprop connecttime

NICK PROPERTY: CONTENT

Usage: PROP <nick> CONTENT [<ANY|G|PG|MA>] [<V|S|L>]
The CONTENT property allows you to set a restriction on the channels you can join. The rating is similar to US TV guide ratings, valid values are G, PG, and MA for General Audience, Parental Guidance, and Mature Audience respectively.
Additionally, it may contain a second parameter with the flags V, S, and L to indicate Violence, Sexual content, and crude Language, that may be commonly found in the channel.
For instance, if you specify PG SL, then you won't be able to join channels with a PG rating or higher. You also wouldn't be able to join channels that have the S or L flag set.
You can specify ANY to allow all channel ratings.Privilege: userAttribute: read-writeExamples:
/uprop content
/uprop content ANY
/uprop content ANY SV
/uprop content PG
See also: PROP CHANNEL RATING

NICK PROPERTY: ENCRYPTION

NICK PROPERTY: FREEZEBY

Usage: PROP <nick> FREEZEBY
The FREEZEBY property holds the name of the operator who froze the nickname.Privilege: operatorAttribute: readExamples:
/uprop freezeby
Note: this property is only set if the nick is frozen, see PROP NICK FROZEN.

NICK PROPERTY: FREEZETIME

Usage: PROP <nick> FREEZETIME
The FREEZETIME property tells you when the nickname was frozen.Privilege: operatorAttribute: readExamples:
/uprop freezetime
Note: this property is only set if the nick is frozen, see PROP NICK FROZEN.

NICK PROPERTY: FROZEN

Usage: PROP <nick> FROZEN
The FROZEN property is set if a nickname was frozen and states the reason for the freezing.Privilege: operatorAttribute: readExamples:
/uprop frozen
See also PROP NICK FREEZEBY and PROP NICK FREEZETIME.

NICK PROPERTY: FTRANSFER

Usage: PROP <nick> FTRANSFER [<ON|OFF>]
If you set the FTRANSFER property to OFF, then all channel founder transfers (using TRANSFER) to you are blocked automatically. Default is ON.Privilege: userAttribute: read-writeExamples:
/uprop ftransfer
/uprop ftransfer on
/uprop ftransfer off
See also: TRANSFER
Note: Network operators can still override this with the command FTRANSFER.

NICK PROPERTY: GUID

Usage: PROP <nick> GUID
The GUID property is a Globally Unique Identifier for the user, the GUID will remain the same even if you change your nickname.Privilege: userAttribute: readExamples:
/uprop guid

NICK PROPERTY: ICQ

Usage: PROP <nick> ICQ [<ICQ-account>]
The ICQ property allows you to specify your ICQ account, if you want other users to be able to contact you on ICQ.Privilege: userAttribute: read-writeExamples:
/uprop icq
/uprop icq 2107

NICK PROPERTY: LANGUAGE

Usage: PROP <nick> LANGUAGE [<language code>]
The LANGUAGE property lets you set a preferred language. The parameter must be a valid ISO 639 language code, it will be displayed in your WHOIS info, together with the corresponding language name.Privilege: userAttribute: read-writeExamples:
/uprop language
/uprop language de

NICK PROPERTY: LUID

Usage: PROP <nick> LUID
The LUID property is a Local User Identifier for the nick, the LUID depends on the nickname you are using, for users with unregistered or unverified nickname, this property is set to 0. Multiple nicknames can be grouped under one LUID.Privilege: userAttribute: readExamples:
/uprop luid

NICK PROPERTY: MAILBLOCK

Usage: PROP <nick> MAILBLOCK [<ON|OFF>]
This property controls whether you want automated services messages to be sent to the email address associated with your nickname/LUID. If you disable this option, you will NOT be able to get help with your nickname password. Default is OFF.Privilege: userAttribute: read-writeExamples:
/uprop mailblock
/uprop mailblock on

NICK PROPERTY: MARKED

Usage: PROP <nick> MARKED
The MARKED property is set if a nickname was marked and states the reason for the marking.Privilege: operatorAttribute: readExamples:
/uprop marked
See also PROP NICK MARKEDBY and PROP NICK MARKEDTIME.

NICK PROPERTY: MARKEDBY

Usage: PROP <nick> MARKEDBY
The MARKEDBY property holds the name of the operator who marked the nickname.Privilege: operatorAttribute: readExamples:
/uprop markedby
Note: this property is only set if the nick is marked, see PROP NICK MARKED.

NICK PROPERTY: MARKEDTIME

Usage: PROP <nick> MARKEDTIME
The MARKEDTIME property tells you when the nickname was marked.Privilege: operatorAttribute: readExamples:
/uprop markedtime
Note: this property is only set if the nick is marked, see PROP NICK MARKED.

NICK PROPERTY: MFORWARD

Usage: PROP <nick> MFORWARD [<EMAIL|OFF>]
This property enables memo forwarding to the email address attached to your nickname/LUID. If you set MFORWARD OFF it will stop forwarding memos for the nick you are using. You cannot turn MFORWARD on if you have PROP NICK NOMEMO set on. Default is OFF.Privilege: userAttribute: read-writeExamples:
/uprop mforward
/uprop mforward off

NICK PROPERTY: MRECEIPTS

Usage: PROP <nick> MRECEIPTS [<ON|OFF>]
This property will send you a notification memo when a user has read a memo you have sent to them. The default is OFF.Privilege: userAttribute: read-writeExamples:
/uprop mreceipts
/uprop mreceipts on
If you need to know when someone has gotten the information you sent, then turn MRECEIPTS on. Also, this way if you do not get a memo, you will know that the one you sent was never read. It is best left off, to avoid pointless memos, unless you have a reason to desire the information.

NICK PROPERTY: MSN

Usage: PROP <nick> MSN [<MSN-account>]
The MSN property allows you to specify your MSN account, if you want other users to be able to contact you on MSN.Privilege: userAttribute: read-writeExamples:
/uprop msn
/uprop msn Ewok2107@hotmail.com

NICK PROPERTY: NAME

Usage: PROP <nick> NAME [<>]
The NAME property allows you to set your name.Privilege: userAttribute: read-writeExamples:
/uprop name
/uprop name John Doe

NICK PROPERTY: NICKTIME

Usage: PROP <nick> NICKTIME
The NICKTIME property is the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when the nick was changed last.Privilege: userAttribute: readExamples:
/uprop nicktime

NICK PROPERTY: NOMEMO

Usage: PROP <nick> NOMEMO [<ON|OFF>]
This property prevents people from being able to memo you, if set to ON. You cannot turn NOMEMO on if you have PROP NICK MFORWARD set on.Privilege: userAttribute: read-writeExamples:
/uprop nomemo
/uprop nomemo on

NICK PROPERTY: NOOP

Usage: PROP <nick> NOOP [<ON|OFF>]
With the NOOP property you can control whether you get opped when you join channels you have access in.Privilege: userAttribute: read-writeExamples:
/uprop noop
/uprop noop on
/uprop noop off

NICK PROPERTY: OPT

Usage: PROP <nick> OPT [<IN|OUT>]
The OPT property allows you to toggle the "opt" flag, which controls whether you wish your email address to be used for mailings. Individual networks have different policies about opting in or out. Default is IN.Privilege: userAttribute: read-writeExamples:
/uprop opt
/uprop opt out

NICK PROPERTY: PASSWORD

Usage: PROP <nick> PASSWORD <new password>
The PASSWORD property allows you to set a new password for your nickname/LUID.Privilege: userAttribute: writeExamples:
/uprop password
/uprop password Fz71ch2
Note, that this property is write-only, you can't retrieve the password.

NICK PROPERTY: PMREPTRACK

Usage: PROP <nick> PMREPTRACK [<repetition limit>]
The PMREPTRACK property attempts to block too many repetitions of messages sent to you privately. If one or many users send you a message very often (or messages that all are very similar), then the server will stop sending them to you, once the number reaches the limit set in PMREPTRACK.Privilege: userAttribute: read-writeExamples:
/uprop pmreptrack
/uprop pmreptrack 3

NICK PROPERTY: REALNAME

Usage: PROP <nick> REALNAME [<userinfo>]
The REALNAME property allows you to set the real name or userinfo that is visible when someone performs a WHOIS on you.Privilege: userAttribute: read-writeExamples:
/uprop realname
/uprop realname John Doe

NICK PROPERTY: REGISTERED

Usage: PROP <nick> REGISTERED
The REGISTERED property is the UNIX time (number of seconds in Jan 1, 1970 00:00:00, GMT) of when the nickname was registered.Privilege: userAttribute: readExamples:
/uprop registered

NICK PROPERTY: SHOWAGE

Usage: PROP <nick> SHOWAGE [<ON|OFF>]
SHOWAGE specifies whether other users can see your AGE property, if you set one. The default is OFF.Privilege: userAttribute: read-writeExamples:
/uprop showage
/uprop showage on
/uprop showage off
See also: PROP NICK AGE

NICK PROPERTY: URL

Usage: PROP <nick> URL [<an URL>]
The URL property allows you to add an URL that is shown to other users if they request INFO about your nick.Privilege: userAttribute: read-writeExamples:
/uprop url
/uprop url http://www.myveryownwebsite.com

NICK PROPERTY: YAHOO

Usage: PROP <nick> YAHOO [<Yahoo-account>]
The YAHOO property allows you to specify your Yahoo account, if you want other users to be able to contact you on Yahoo.Privilege: userAttribute: read-writeExamples:
/uprop yahoo
/uprop yahoo Ewok2107@yahoo.com

QLINE

Usage: QLINE <nick|mask> <reason>
This adds a temporary qline to the server. Qlines restrict the use of a nickname to network operators. If you notice that a certain nickname is connected to your server and that nickname is inappropriate, you can use this command to change the nickname of that user to Guestxxxx and prevent further use.
Note: that nickname will not be available for use until it is removed from the qline list. To view your qline list simply type /STATS q on your server, the qlines are prefixed by q:.Examples:
/qline IRC-Oper impersonation
/qline *serv* services impersonation
Qlines are used to prevent nicks that seem in bad taste or nicks that give the illusion of being part of the network administration. This is why opers can use qlined nicks. Be careful when setting qlines with variables, such as *sh*t* which would ban possibly acceptable nicks like Lipshitz.

QUIT

Usage: QUIT [<message>]
Causes the server to terminate your current session. You are free to log back on after issuing this command.Examples:
/quit I'll be back in awhile.
Note: the server configuration may surpress the display of the quit message. This is because quit messages, just like PART messages, can easily be abused to spam or annoy other users.

RAKILL

Usage: RAKILL <user@host>
Removes a specific global kline from the entire network. As with the AKILL command, any server that is split when you issue this command will not remove the entry.Examples:
/rakill alumnus@nc-67-77-218-198.dyn.sprint-hsd.net
/rakill *@*.digex.net
If you set the global akill and now think it should be removed, you generally should remove it from the entire network. It's not a good idea to leave akills on other servers, because then they may not be noticed for a while and an akill may stay around simply because no one was responsible for removing it.

READ

Usage: READ [<folder>] <memo number>
This command is used to read memos you receive, you can specify a folder by either name (for instance INBOX, SYSTEM) or number. If no folder is specified, the currently selected folder is used.
You can read more than one memo by passing a list of numbers, for instance 1,3,5 to read the 1st, 3rd and 5th memo, or passing a range, such as 1:5 to read the first 5 memos.Examples:
/read 1
/read 1,7
/read 2:5
/read system 1
See also MEMO and FOLDER.
Note: this command replaces the "/memoserv read" command.

REHASH

Usage: REHASH [<server>]
Used to to clear temporary settings such as klines and qlines.Examples:
/rehash
/rehash chat2.*
A good command to use at the end of an event, or on a community chat server.

RESTART

Usage: RESTART [<server>]
This command will restart ConferenceRoom. It will reset the /LUSERS information, it will not reset the database or the configuration settings in your Confchannel.conf file. All users will be forced off the server while it quits.Examples:
/restart
A good command to use at the end of an event, or on a community chat server.

ROLL

Usage: ROLL <sides> [<dice>]
This command will simulate rolling a die with the specified number of sides. If you wish to roll multiple dice with the same number of sides, then include the number of dice you wish to roll after the number of sides. The example below would roll two six-sided dice.Examples:
/roll 6 2
This command is primarily here to make it easier to use the chat network for fun purposes. You can always flip a coin or roll a die while chatting to help you make difficult decisions or play various games.

SAJOIN

Usage: SAJOIN <#channel|all>
This command will allow you to join channels that are locked, keyed or have bans set against you. You will also not be able to be kicked out from any channel you entered with SAJOIN. When you use the command 'all' at the end of this command you will be joined to all channels on the server (max 100).Examples:
/sajoin #test
/sajoin all
If the people running a channel are causing problems and they try to ban you when you are discussing this with them, then you can force your way in so that you can explain what you are doing. You can also use this along with SAMODE to op yourself in the channel and remove anyone who is misbehaving. This command can be used simply to make you unkickable.

SAKICK

Usage: SAKICK <#channel> <nick|mask>
This command acts the same as KICK, but it allows operators to kick users from channels without being opped.Examples:
/sakick #test AnnoyingSquirrel Don't do that.
/sakick #botchannel *
See also KICK.

SAMODE

Usage: SAMODE <#channel> +|-<modes> [<value>]
This gives the operators the ability to set modes in a channel without being a channel operator. The modes syntax is the same as with MODE.Examples:
/samode #test +o Steve
/samode #test -i
This is a good method for taking control of any channel that is having problems. It even works if your server is currently split from services. You can fix any modes, remove or add any ops, and ban any users from the channel.

SAPROP

Usage: SAPROP <#channel|nick> <property> <value>
This gives the operators the ability to set properties in a channel without being a channel operator and read all properties of nicknames. The syntax is the same as with PROP.Examples:
/saprop #FunChat desc a fun channel for all ages
/saprop Stephen
See PROP for details.

SERVER

Usage: SERVER <server> [<port>]
This command is for connecting to a server with an IRC client. It will disconnect you from the server you are using and try to connect you to the server you specify.Examples:
/server irc.webchat.org 6667
With most clients if no port is listed it defaults to 6667, the standard IRC port. If the server you were using goes down or if you are experiencing significant lag (delays between you typing things and people seeing them) then you might want to switch servers. The server command will cause the client to try to connect to whatever server you specify.
Note: this is a client-side command, some clients may not support it or have slightly different syntax.

SERVICES

Usage: SERVICES <command>
This is an alias for /msg nickserv.Examples:
/services info Jennifer
See also NS as another alias for /ms nickserv.
Many NickServ commands can now be accessed with direct server commands, such as INFO, IDENTIFY, ACCESS and others.

SERVSTART

Usage:
This command will restart your services while you are online.Examples:
/servstart
This is the easiest way to bring services back if they are removed for any reason. See SERVSTOP to shut services down.

SERVSTOP

Usage:
This command will stop your services.Examples:
/servstop

SET

Usage: SET <nickname> <field> <data>
This command allows you to set specific field information. Fields store information that is associated with a nickname and allow for a variety of storage and display options.Examples:
/set bill avatar cat
See also: FIELD

SETPASS

Usage: SETPASS <old password> <new password>
This command lets you change your password. An email will be sent to your email account asking you for verification.Examples:
/setpass MyPass 4lmtkTIXB2

SHOWTICKER

Usage:
This command will show the Java client the ticker, which is the scrolling message at the bottom of the page. Note that this command will only work if it is enabled in the parameter file, which is managed by the server administrator.Examples:
/showticker
This command reverses the HIDETICKER command so that you can once again see the ticker.

SHUN

Usage: SHUN [<nick>|<#channel> <nick>] [<reason>]
Allows you to specify nicks that will not be able to talk in channels or send private messages or notices on that specific server. You can also shun a user from speaking in a particular channel; this will not affect private messages at all. To remove the shun, just issue the UNSHUN command with the specific nick you wish to unshun.
To view the shun list type /SHUN. Opers cannot be shunned. However if a shunned user opers, the shun still remains and is effective until it is removed.Examples:
/shun Fred be quiet.
/shun #polynomial Fred be quiet.
This can be a rather harsh thing to do to someone because unless you inform them, they will have no way of knowing that they are shunned and their private messages are not being received. It can be used in channels if a particular user is causing problems there, but generally behaving elsewhere.

SILENCE

Usage: SILENCE [-|+]<nick|nick!user@host>
The silence command allows you to ignore a specific user. For example, if a user is flooding or harassing you, the user can be silenced. When you silence a user, all messages, notices or ctcp events initiated by that user will no longer reach you. Others see this user's messages normally.
You can specify a nickname or a mask, any user that matches that mask will not be able to send private messages or notices to you. To remove a silence, issue the same command with a minus sign "-" in front of the hostmask or nick
If you specify a nickname, then it will add the *!user@host mask that matches the nickname you specified, if you only want to silence a particular nick, you need to do /SILENCE nickname!*@*Examples:
/silence
/silence rowdy
/silence -rowdy
/silence Flooder!trill@pm02.digex.net
This is a good command to stop people from annoying you. You will see anything they say in channels you have in common, so you won't miss anything important. Yet you won't see any private messages. Silencing people is a very good tactic that is not used as often as it should be.
There may be many immature people who get on your nerves, simply not dealing with them is best. Then you can enjoy chatting in peace with the people who do interest you.
Note: many clients provide a client-side command with similar functionality, it's usually called /IGNORE. The difference is, that SILENCE will prevent the messages to even be sent to you, while with /IGNORE, the client still receives them but doesn't display them.

SOUND

Usage: SOUND <name>
Will play the specified sound file to the channel.Examples:
/sound door
When you know the list of names that are available on the chat site you can play them with this command.
Note: this is a client command and limited to the Java client.

SQUIT

Usage: SQUIT <server> <reason>
Causes the specified server to be disconnected from the network. Use the CONNECT command to connect the server back to the network.Examples:
/squit irc.webmaster.com I want to connect you to another hub.
This is done to reroute a server. A server cannot connect to another server on the same network. So you have to SQUIT a server before you can reconnect it. You might wish to GLOBOPS before rerouting, in case someone has a good reason not to reroute. It is also nice to WALLOPS before squiting, so that users who wish to be kept informed will expect the split.

STATS 4

Usage: STATS 4Resolver Information: - Shows the active resolvers that have been specifically defined. It also shows the penalty count for wach name server. The higher the penalty count the less we use that specific name server.Examples:
/stats 4
/stats 4 arena.*

STATS 5

Usage: STATS 5 [<server>]Version history: - This is primarily useful if you need technical support on beta code as it shows us the internal version of each module inside of ConferenceRoom.Examples:
/stats 5
/stats 5 arena.*

STATS c

STATS D

Usage: STATS DDomain reporting: - Gives you a list of the configured servers and the last time a domain report was sent.Examples:
/stats D

STATS h

Usage: STATS h [<server>]Hubs: - This will show you which hubs you are configured to connect to.Examples:
/stats h
/stats h arena.*

STATS i

Usage: STATS i [<server>]Allowed Hosts: - Shows all of the user@host masks that are allowed to connect to the server. It will also show the ping time that the mask contains.Examples:
/stats i
/stats i arena.*

STATS j

Usage: STATS j [<server>]Client type count: - This will give you a client type breakdown for both local and global clients.Examples:
/stats j
/stats j arena.*

STATS K

Usage: STATS K [<server>]Additional security information: - This will list some Zline, Proxy and URL filtering settings, as well as some connection statistics of the server.Examples:
/stats K
/stats K arena.*

STATS l

STATS m

Usage: STATS m [<server>]Commands: - It will give a list of commands and how many times each has been used. This may be useful to make sure that certain commands aren't being overused or misused. For example, if your network requires opers to send an email explaining every shun and the total shun count has gone up more than the emails received, then you can look for the discrepancy.Examples:
/stats m
/stats m arena.*

STATS o

Usage: STATS o [<server>]Operators: - Shows the operator configurations for the target server. You will get a list of masks and nicks that are allowed to oper. To the left of each entry will be a letter that shows their status, such as h for helper or O for oper.Examples:
/stats o
/stats o arena.*

STATS P

Usage: STATS P [<server>]Proxy status: - Gives you a list of the hosts that have been caught by the proxy filter along with the number of attempts that each host has made.Examples:
/stats P
/stats P arena.*

STATS q

Usage: STATS q [<server>]Usage: STATS Q [<server>]Qlines: - Shows all of the nicknames that cannot be used by non-opers and why they are prohibited. See QLINE to add such nicks.Send queue: - Shows queue information. This will usually not be very useful but can contain information needed for debugging.Examples:
/stats q
/stats q arena.*

STATS u

Usage: STATS u [<server>]Usage: STATS U [<server>]Uptime: u - Shows how long the server has been running.Unknown connections: U - See the IP addresses of the unknown connections to your server. Connections can be open for a variety of reasons. Most common is that the client is waiting for DNS resolving to happen. You can close these connections with the CLOSE command.Examples:
/stats u
/stats u arena.*
/stats U
/stats U arena.*

STATS w

Usage: STATS w [<server>]User statistics: - Shows the average number of network operators and users on that server and on the network for various recent time intervals. This is a good way to keep track of how your network is doing and look for problems. You can check your oper to user ratio and make sure that it is sufficient for the times your chat network is open.Examples:
/stats w
/stats w arena.*

STATS Z

Usage: STATS Z [<server>]

Internal Information:
This is not very useful to the user, but it is important debugging information. If you email support@webmaster.com for technical support you should give the stats Z and Stats 5 of the server or of services.* if the problem is a services problem.

Example:
/stats Z webmaster.*
/stats Z

THAW

Usage: THAW <nick>
The THAW command is used to undo a previously issued FREEZE.Examples:
/thaw Francisca
Freezing a nick should be a temporary punishment in most cases, this command reverses the freezing and restores all rights to the nick.

TIME

Usage: TIME [<server>]
Display the current local time and date of the server to which you are connected or specified in the command.Examples:
/time
/time webmaster.*
This is useful either to see what time it is if you do not have the time easily accessible or to see what time zone a server is in. You can also issue a time command if you are using a client that logs and want to mark down what time it is in the log for future reference.

TOPIC

Usage: TOPIC <#channel> <topic>
All users (or only channel operators if the channel has CMODE +t set) can use this command. The TOPIC command lets you change the topic of a channel.Examples:
/topic #ConferenceRoom Welcome to the Webmaster support channel.
The topic is one of the first things people see about a channel. The topic often gives some information about the channel, or highlights an amusing quote that came up in the channel recently.
The ability to use this command may be further restricted to a certain level of access in the channel, see PROP CHANNEL TOPIC and PROP CHANNEL TOPICLOCK.

TRACE

Usage: TRACE <server>
Show the route between you and that server.Examples:
/trace webmaster.*
This command can be used to determine where lag exists by following the route. It can also help network operators determine how to reroute servers based on their current connections.

TRANSFER

Usage: TRANSFER <#channel> <nick>
Used to transfer channel ownership to another nick. You must be founder of the channel and the specified nick must be registered. The specified nick will receive a memo with instructions to complete the transfer.Examples:
/transfer #BakerStreet221B MrsHudson
Note that after transferring you no longer will have founder access to the channel. The new founder then owns the channel and can manage it as he pleases.

UFIELD

Usage: UFIELD <field> <GET|SET> [<value>]
This command is an alias for FIELD <yournick> and just more convenient to change your own fields.Examples:
/ufield set name John Doe
/ufield get name
See also FIELD.

Sets modes on yourself, you can use the UMODE command only for the nickname you are using at the time. Administrators can set modes on users by using MODE with the target nickname.
Available user/oper modes:

USER MODE a

Usage: This mode is automatically set on a user if they have the priviliges configured in their operator configuration.a - Services Administrator
Services Administrator status. You need to have UMODE +o set before you can set yourself +a, and your operator entry has to specify you as a services administrator. This will allow you access to super user status in services. You will be able to getpass and set other services options.

USER MODE A

Usage: This mode is automatically set on a user if they have the priviliges configured in their operator configuration.A - Server Administrator
Server Administrator status.

USER MODE b

Usage: UMODE +|-bUsage: MODE <nick> +|-bb - Chatops
This mode is used in order to see CHATOPS messages occurring on the server and network. Since globops should be reserved for very important oper-only messages, chatops allow opers to communicate about less important things. If an oper is very busy they might turn chatops off, but they should still have UMODE +g set.
Exactly how chatops are used will depend on the network, but they can be used simply as a way for opers to chat and have fun or for less important but still network-related oper-communications.Privilege: operatorExamples:
/mode jimmers +b
/umode +b
See also: GLOBOPS

USER MODE B

Usage: UMODE +|-BUsage: MODE <nick> +|-BB - Buddy exception for +m
This mode is only effective if you have UMODE +m set, it allows all users on your buddy list to message you while you block private messages.
By using +m and +B, you can make sure only your buddies are allowed to message you.Privilege: userExamples:
/mode jimmers +B
/umode +B
See also: UMODE +W

USER MODE c

Usage: UMODE +|-cUsage: MODE <nick> +|-cc - Clients
This will show all clients as they enter and exit the server.Privilege: operatorExamples:
/mode jimmers +c
/umode +c

USER MODE C

Usage: UMODE +|-CUsage: MODE <nick> +|-CC - Channel exception for +m
This mode is only effective if you have UMODE +m set, it allows users to message you if they are in a channel with you.
By using +m and +C, you can make sure only users you see in channels can message you, so spamming or flooding from outside is not possible.Privilege: userExamples:
/mode jimmers +C
/umode +C
See also: UMODE +M

USER MODE d

Usage: UMODE +|-dUsage: MODE <nick> +|-dd - DCC protection
The server will block DCC requests of certain file types by default, those include .exe, .dll, .mrc, .scr and similar dangerous types. This is done to prevent the spreading of worms, viruses and trojan horses.
If you set +d, then those DCC requests are allowed, letting you send and receive such files from users you trust.Privilege: userExamples:
/mode jimmers +d
/umode +d
See also: UMODE +e

USER MODE e

Usage: UMODE +|-eUsage: MODE <nick> +|-ee - DCC block
If this mode is set, DCC transfers cannot be sent to your client. This is a good idea for children and computer novices. It is also useful for experts who do not want to be bothered by DCC requests. Since many files can be harmful, it is a good idea to leave this on and only turn it off if you have chosen to receive a file from someone you trust.
You will still need to accept the file transfer. Do not run any scripts or files that you do not understand. Even harmless looking files might contain a virus. Avoiding all file transfers is the safest course.Privilege: userExamples:
/mode jimmers +e
/umode +e
See also: UMODE +d

USER MODE f

Usage: UMODE +|-fUsage: MODE <nick> +|-ff - Flood notices
Will notify you in the event users on your server exceed the flood settings that have been administratively set. If the same user is repeatedly flooding, you might wish to kline or akill that user.Privilege: operatorExamples:
/mode jimmers +f
/umode +f

USER MODE g

Usage: UMODE +|-gUsage: MODE <nick> +|-gg - Globops
Shows globops. Opers should generally be +g in order to see urgent or important globops messages. See the GLOBOPS command for information on how to send globops.Privilege: operatorExamples:
/mode jimmers +g
/umode +g
See also: CHATOPS and LOCOPS

USER MODE G

Usage: UMODE +|-GUsage: MODE <nick> +|-GG - Global notices
Shows all GNOTICE messages and other global notices from the server. Opers should generally be +G so that they will not miss any important information sent by the server, services or other operators.Privilege: operatorExamples:
/mode jimmers +G
/umode +G
See also: GNOTICE

USER MODE h

Usage: UMODE +|-hUsage: MODE <nick> +|-hh - Helpops
Identifies you to others as a "helper". If this mode is set, your WHOIS HTML display will show a message stating that you are "helpful". Also, if a user requests help on a specific subject, you will receive a 'helpop' message informing you of what subject he is looking for help on.
Any messages for helpserv that does not give a help file will be sent to the helpops so that they can assist.Privilege: help operatorExamples:
/mode jimmers +h
/umode +h

USER MODE i

Usage: UMODE +|-iUsage: MODE <nick> +|-ii - Invisible
Makes a user invisible, you will not be able to see what channels this user has joined unless you are in that channel with the user. Most people set themselves +i to avoid being randomly spammed or followed into channels.
The mode also hides your idle and connect times from other users, which otherwise would be shown in the WHOIS info.Privilege: userExamples:
/mode jimmers +i
/umode +i

USER MODE I

USER MODE j

Usage: This mode is automatically set on a user if they have the priviliges configured in their operator configuration.j - Java client
See CMODE +j for one way to treat java users specially in a channel.

USER MODE k

Usage: UMODE +|-kUsage: MODE <nick> +|-kk - Kill notices
Will show you all the kill messages occurring on your server and the network. On a big network this will often be more information than you want to deal with, although you could set up a bot to log it in case you wanted to be able to check for any problems later. On smaller networks this can sometimes help give you a better feel for what is going on.Privilege: operatorExamples:
/mode jimmers +k
/umode +k
See also: KILL

USER MODE L

Usage: UMODE +|-LUsage: MODE <nick> +|-LL - Language filter
If filtering is set on for the server then messages to this user will be censored. This mode says the user has sensitive ears when someone performs a WHOIS on them.Privilege: userExamples:
/mode jimmers +L
/umode +L

USER MODE m

Usage: UMODE +|-mUsage: MODE <nick> +|-mm - Message block
This will protect you from getting direct messages from other users. This is useful if you are away and do not want people trying to communicate with you or if you do not want to be bothered outside of channels. It also is a good mode to set for children.
While it is best to either supervise a child or educate them thoroughly and only allow them to chat unsupervised when their guardians feel they are ready, removing private messages provides some additional protection. Then if they remain in well-supervised channels the operators may make sure that the conversation is acceptable.Privilege: userExamples:
/mode jimmers +m
/umode +m
You can define a number of exceptions for this block, see: UMODE +B, UMODE +C, UMODE +J, UMODE +M, UMODE +R, UMODE +W

USER MODE M

Usage: UMODE +|-MUsage: MODE <nick> +|-MM - Registered users on channel exception for +m
This mode is only effective if you have UMODE +m set, it allows users to message you if they have a registered nickname and are in a channel with you.
By using +m and +M, you can make sure only registered users you can see in a channel are allowed to message you.Privilege: userExamples:
/mode jimmers +M
/umode +M
See also: UMODE +R and UMODE +C
Note: The difference between +mM and +mCR is, that +M only allows users that are registered AND in the channel, while +CR allows users that are registered OR in a channel with you.

USER MODE n

Usage: UMODE +|-nUsage: MODE <nick> +|-nn - Newsflash
This will allow the users to receive newsflash messages. Some people enjoy getting information about world events while chatting, others find it annoying or distracting. If you like receiving news, then you can set yourself +n.Privilege: userExamples:
/mode jimmers +n
/umode +n

USER MODE o

Usage: This mode is automatically set on a user if they have the priviliges configured in their operator configuration.o - Operator
The server will set this mode for you after you identify yourself as an operator. This is the mode that tells people you are a network operator and gives you the basic oper powers.

USER MODE p

Usage: UMODE +|-pUsage: MODE <nick> +|-pp - CTCP block
This will prohibit others from sending you CTCP requests. You will see CTCPs that are sent to channels that you are in, but you won't reply to them. This mode is useful to prevent CTCP flooding or just annoying CTCPs. CTCPs are used to measure lag or gather information about someone, such as what client they are using. Operators can bypass this mode.Privilege: userExamples:
/mode jimmers +p
/umode +p

USER MODE q

Usage: UMODE +|-qUsage: MODE <nick> +|-qq - Quiet
This mode will disable a users ability to talk on the server at all. Once set it can't be unset. Normally this is used in an event client class where you set the initial mode to +q so that the user can't speak on the server.Privilege: userExamples:
/mode jimmers +q
/umode +q

USER MODE r

Usage: This mode is automatically set on a user if they have the priviliges configured in their operator configuration.r - Registered
User is using a registered nickname and has identified for the nick. This is only meant to be informative, users cannot set themselves + or - r.

USER MODE R

Usage: UMODE +|-RUsage: MODE <nick> +|-RR - Registered users exception for +m
This mode is only effective if you have UMODE +m set, it allows all users with registered nickname to bypass the message block.
This is useful if you only want to block unregistered users, which also greatly reduces the possibility of receiving spam or being flooded.Privilege: userExamples:
/mode jimmers +R
/umode +R
See also: UMODE +M

USER MODE s

Usage: UMODE +|-sUsage: MODE <nick> +|-ss - Server notices
Allows you to see messages that the server sends. This is usually kill messages. It isn't very useful for the average user, but it is an option for the curious. This mode is automatically set on Operators.Privilege: userExamples:
/mode jimmers +s
/umode +s

USER MODE t

Usage: UMODE +|-tUsage: MODE <nick> +|-tt - Reports
This mode will show you a report of what is done on the server, such as, STATS commands or ADMIN. Every time someone issues certain commands, you will be notified. If you want to watch who is curious about the network you can set yourself +t. Sometimes when users are trying various odd commands they are trying to learn something because they do not know the correct commands.Privilege: operatorExamples:
/mode jimmers +t
/umode +t

USER MODE w

Usage: UMODE +|-wUsage: MODE <nick> +|-ww - Wallops
Messages sent by opers to users will be visible. This is usually a good mode to have set on. Opers will sometimes send information that is helpful but not urgent through wallops. For example, if the network were in the process of rerouting some servers, causing some quick splits, there might be a wallop about it.Privilege: userExamples:
/mode jimmers +w
/umode +w

USER MODE W

Usage: UMODE +|-WUsage: MODE <nick> +|-WW - Watch list exception for +m
This mode is only effective if you have UMODE +m set, it allows users to message you if you have them on your WATCH list.
By using +m and +W, you can declare which users may message you, just by adding the nicks to your WATCH list. This can be useful if you are busy or just want to talk to a very few, possibly only one user at some point.Privilege: userExamples:
/mode jimmers +W
/umode +W
See also: UMODE +B

USER MODE x

Usage: UMODE +|-xUsage: MODE <nick> +|-xx - Hash host
IP masking of the hostmask which helps to prevent denial of service attacks. In the formation of =numbersletters or numbersletter=. You can still ban specific users by their full address, just ban the munged version that you can see in their whois, and they will be unable to join.Privilege: operatorExamples:
/mode jimmers +x
/umode +x

USER MODE y

Usage: UMODE +|-yUsage: MODE <nick> +|-yy - Whois notices
This will show you who performs a WHOIS on you. Since most users do not realize anyone can see when they are being whoised, they may be surprised if you mention it to them. Also you should not take offense at being whoised unless someone is repeatedly whoising you as an attempt to flood you. There are numerous reasons to whois someone, such as to check their idle time.
But people who are whoising opers often desire help, and you can offer it to them or wait for them to message you.Privilege: operatorExamples:
/mode jimmers +y
/umode +y

USER MODE z

Usage: This mode is automatically set on a user if they have the priviliges configured in their operator configuration.z - Services Agent
This is set on a services agent and will show in the WHOIS information.

UNAKILL

Usage: UNAKILL <ident@host>
This command will remove an AKILL from the server you are connected to. Unlike the RAKILL command, which will remove the akill from all the servers, the UNAKILL command will remove it only from your server.Examples:
/unakill *@*.aol.com
This can be a way to give someone a chance to come back onto the network while still limiting them to one server and keeping a close eye on them. But generally you will want to remove akills globally with RAKILL rather than locally.

UNBAN

Usage: UNBAN <#channel> [<*>]
If issued without the '*' parameter, it will remove all bans that would affect you. With the '*' parameter, all bans are lifted.
You need high enough access to the channel to use this command.Examples:
/unban #mychannel
/unban #mychannel *
This is a convenient and fast way to clear the entire ban list of a channel, but it can also be used if you find yourself banned from a channel you have access in, as you can remove the bans from outside and then join.
This replaces the service command /CS UNBAN.

UNIDENTIFY

Usage: UNIDENTIFY [<nick>]
This command makes the server forget that you identified to a nick, if no nickname is specified, it drops the identification for the nick you are currently using.Examples:
/unidentify
/unidentify MyAlterEgo

UNKLINE

Usage: UNKLINE <ident@host>
Will remove a kline from your server. You can NOT use wildcards to erase multiple klines at one time, the mask specified must be an exact match.Examples:
/unkline *@*.aol.com
This undoes the KLINE command. It is generally good to remove klines periodically. Klines will often ban people who did not do anything wrong, and people will often start behaving when given a second chance. It's a good idea to keep track of anyone who is being repeatedly klined so that stronger measures can be taken or the kline can be kept.

UNQLINE

Usage: UNQLINE <nick|mask>
This command will remove a temporary QLINE from your qline list. Qlines are prohibited nicknames. To place a qline please see QLINE.Examples:
/unqline IRCOperator
You may wish to remove a qline if you decide that a nick is acceptable or the qline is proving to be too broad and you wish to set more specific qlines.

UNSHUN

Usage: UNSHUN <nick>
This command will remove a nickname from a shun list. A shun means that the person who has been shunned cannot send any messages through the server. Very often the user doesn't even notice that he/she has been shunned. See SHUN.Examples:
/unshun Fred
Shuns should generally be temporary measures unless the person is aware of being shunned. Otherwise it can be very confusing to the user.

UNZLINE

Usage: UNZLINE <host>
This command will remove a zline from the /STATS k list, the zlines are prefixed by a 'z'. See ZLINE for more information.Examples:
/unzline 24.183.186.180
As with the other commands that ban users from the network, it is a good idea to remove old entries to allow people back on.

UPROP

Usage: UPROP <property> [<value>]
This command is an alias for PROP <yournick> and just more convenient to change your own modes.Examples:
/uprop language en
/uprop theme webmaster
See PROP for details on the properties.

USERHOST

Usage: USERHOST <nick> [<nick>]
Returns the user@host information of all nicks specified, you can pass up to five nick names as parameters.Examples:
/userhost Al Shadoe Gaz Bek
If you just want the address for some users this is a faster way to retrieve them than individually WHOISing each of them. It also only returns the mask, unlike the whois command that will several lines of information. You might want to userhost some people if you needed their mask to identify them.

VERSION

Usage: VERSION [<server>]
Gives the current version of the server you are logged into or the one you specified.Examples:
/version
/version arena.webchat.org
/version arena.*
For more details about the server see INFO.

VOICE

Usage: VOICE <#channel> [<nick>]
This will voice a user or yourself in a channel, but the mode change is done by the server, you need to have AOP or higher access to the channel to use this command on other users and VOP access to use it for yourself.
It's particularly useful if you are not opped or voiced but need to voice someone else or yourself.Examples:
/voice #mychannel Zorgor
voice #mychannel
See also CMODE +v and OP.
This replaces the service command /CS VOICE.

WALLOPS

Usage: WALLOPS <message>
This command will send a message to all users who have UMODE +w set.Examples:
/wallops We're going to be doing some re-routing, so you will experience some quick splits. Please be patient.
Wallops can be seen by anyone on the network, so they should be carefully considered before being sent. They are usually reserved for important information that would interest the users, but is not vital enough to be sent as a newsflash (see NFLASH) or one of the other methods of notifying most or all users.

WATCH

Usage: WATCH [cslL] [+|-<nick|command>] [+|-<nick>]
This command works the same way as the ISON command, although it will notify you if the user appears or goes away until the person is removed from your watch list. You can input up to 5 nick names or channels into each watch command. You can send multiple watch commands.
Adding a nick/channel prefixed with a '-' will remove the entry from the watch list. If you add a channel, it will tell you when the channel empties or has a user join after it was empty.
The single letter commands have the following functionalities:
c - Clear the watch list
s - Show your watch list and how many watch lists your nick is on
l - Show who on our watch list is online
L - Show the entire watch list, indicating which users are online and which are offlineExamples:
/watch +SirenDevil +#gravity +Dagobert
/watch c
/watch L
Watch is designed to let you know when your friends are online. It works much like the BUDDY command, although you have to set it each time you log into the network. It also does not require the authorization of the people you want to add.
Operators may find it useful to add channels to their watch lists at times, for instance if the channel is known to be a meeting point for known abusive users or bots.

WEBSTART

Usage:
Forces the web server to restart.Examples:
/webstart
This should be used if the web server needed to be stopped. If the web server is not running then people cannot connect to the network through web pages and people with configuration access cannot use the web configuration tools.
Note: this is equivalent to WEBADMIN.

WEBSTOP

Usage:
Forces the web server to stop.Examples:
/webstop
Note: see WEBSTART to start the web server.

WHISPER

Usage: WHISPER <#channel> <nick>[,<nick>,...]
A WHISPER is a private message that is sent in the context of the channel. This means that channel operators and the nicks specified can see these messages, but other users can't.Examples:
/whisper #webmaster Mark,Nik,David How is the project coming?

WHO

Usage: WHO <#channel|nick|mask>
When a WHO is done on a channel you are in, you will get a list of the nicks, masks, and "real names" of everyone in the channel and their status in the channel. There will be a letter after their nick, either a 'H' for "here" or a 'G' for "gone". If there is a 'G' it means they set themselves AWAY. A '%' sign means that the person has UMODE +i set.
When a WHO is done on a channel while outside of the channel, only people who are not +i will show, and if the channel is secret or private, then no names will show.
When a WHO is done on a nick, you will get the info only for the user, operators can specify wildcard masks to list users from the entire network.Examples:
/who #webchat/who *.t-dialin.net
A who is a good way to get a list of people and their masks. The who command for a channel is much like the names command except that it gives more information. WHO, when used on a nick, is much like WHOIS except that it gives less information.
Sometimes you want to see nicks and their masks. For example, if you wanted to see if there are clones in the channel then WHO would be the best tool. Or it can be an easy way to see how many people are actually present. Although in large channels a NAMES is better for most purposes, because it is shorter and a WHO may fill up your screen.
Note: the special case "/WHO 0 o" will show all opers on the network, see also OPER to list all opers on the server you are on.

WHOIS

Usage: WHOIS <nick>
Displays information about a nickname. This includes the (hashed) host that they are logged in from, the server they are logged into, the public channels they are in, private channels you are both in. There may be additional information depending upon what fields and modes they have set.Examples:
/whois Oliver
WHOIS is generally the first command you would use on people to learn something about them. For related commands see WHO, WHOWAS, and USERHOST.
Note: the UMODE +y for operators makes them see when someone performs a WHOIS on them. However, WHOISing is considered a valid tool for any user, so you shouldn't worry about it.

WHOWAS

Usage: WHOWAS <nick>
For a certain amount of time after a client has left the server you can still get information about that client. The information is the same as the information given by the WHOIS command.Examples:
/whowas Oliver
If you just missed someone, but you want to know the whois info and forgot to check, you can WHOWAS them. You can also use WHOWAS if someone keeps switching nicks and you cannot whois them easily.

ZLINE

Usage: ZLINE <ip range>
This command is a form of firewall for your server. This will prevent problem users from a specified host address from accessing the server.Examples:
/zline 10.127.0.1-10.127.1.255
This is the strongest ban you can place against an address. The person will not even see a reason why they are banned; they will just be unable to connect. The ban must be set on the numeric version of the address.