ADMIN

Retrieves administrative information about the chat server you are currently using. Often provides an email address for the server administrator and tells which server administrators are online for that server. If the server name is omitted, then this command will provide information about the server to which you are connected.

Examples:
/admin irc.webmaster.com
/admin glass.*
/admin

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.

AKILL

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 param.

Example:
/akill lamer@pm02.digex.net spamming 50
/akill Rachel flooding

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 room ban works, except that it prevents someone from logging into the network rather than from just joining a room.

AWAY

The system will automatically send this message to anyone trying to message you. The message will also show in your information if someone does a 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.

Example:
/away I am away from my computer
/away

If you will be logged onto the chat network, but not actually reading text from it, then you should mark yourself as away. If you do not mark yourself as away then people may try to speak with you and be offended when you do not reply. 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 room, I am busy and not replying to private messages."

CFLASH

This will send a newsflash to all of the users who are +n in the specified room.

Example:
/cflash #Chat Welcome nikb to our SOP team.

This can be used to send newsflashes that only go to people in a particular room. It is mostly useful if you are running an event or meeting in a room and want to add newsflashes about particular information that relates.

CHANSERV

An alias for /msg chanserv so that you can send ChanServ commands with less typing.

Example:
/chanserv info #ConferenceRoom

Any chanserv command can be sent with /chanserv /cs or /msg chanserv

CHATOPS

Sends a notice to all network operators that are set +b.

Example:
/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 in globops.

CLEARAKILLS

This will remove all the global klines or akills from your server. This command does not affect any other servers.

Example:
/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 innocent people who may have matched the ban will not be able to join and chat until the ban is removed.

CLOSE

This command will close your /stats U unknown connections to your server.

Example:
/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 al off so that other users can join.

Sets various options for the room. You must be an operator in the room to issue these commands, some commands are reserved for Server Operators:

A - Auditorium, b - Ban, c - Prevent Colors, d - Nick Change Restriction, e - Prevent CTCPs, i - Invite Only, j - Java Only, k - Keyed, l - Limit, L - Language Filtering, m - Moderated, M - Moderation Forward, n - No External Messages, N - Moderation Receive, o - Channel Operator Status, O - Channel Overflow, p - Private, r - Registered, R - n/a, s - Secret, t - Topic, u - Channel User, v - Voice, w - n/a, y - n/a, z - Encrypt Only

For more information type /hs cmode

Examples:
/hs help cmode <mode>

CONNECT

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.

Example:
/connect server1 6667 server2

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

An alias for /msg chanserv so that you can send ChanServ commands with less typing.

Example:
/cs info #ConferenceRoom

Any chanserv command can be sent with /chanserv /cs or /msg chanserv

DIE

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 carefull using this command.

Example:
/die

This command 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.

FJOIN

This will force a user into the specified room.

Example:
/fjoin John #conferenceroom

This can be a way to send someone who needs help to the proper room, especially if they are having trouble joining rooms. However, it can be disorienting to find yourself in a room you didn't intentionally join. It is often a good idea to inform the user of what you are doing.

FURL

This command will force a user's browser to open and view an URL. This will only work on java users.

Example:
/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

This command is used to get requested Field data.

Examples:
/get Jennifer Avatar

GLOBOPS

Sends a message to all opers that are user mode +g. This command is usually used for network wide communication between opers for details that concern the entire network.

Example:
/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.

HelpServ Topics

Please Note: If you request help that is not in this list your help request will go to all the Operators that are set mode +h.

All user modes and channel modes are listed. To get help

Available help topics:

ACTION - ADMIN - AKILL - AWAY - CFLASH - CHANSERV - CHATOPS - CLEAR - CLEARAKILLS - CLOSE - CMODE (Channel Modes) - CONNECT - CS - DIE - EMBED - FJOIN - FURL - FLOAT - GET - GLOBOPS - HELPOP - HELPOPS - HIDETICKER - HS - IDENTIFY - INFO - INVITE - ISON - JOIN - KICK - KILL - KLINE - LFLASH - LINKS - LIST - LOAD - LOCOPS - LUSERS - ME - MEMOSERV - MFLASH - MKILL - MODE - MOTD - MOVE - MS - MSG - NAMES - NEWJOIN - NFLASH - NICKSERV - NOTICE - NS - OPER - REHASH - PART - PASS - PING - PRIVMSG - PROP - PROTOCTL - QLINE - QUIT - RAKILL - RESTART - ROLL - SAJOIN - SAMODE - SERVER - SERVICES - SERVSTART - SET - SHOWTICKER - SHUN - SILENCE - SOUND - SQUIT - STATS - STREAM - STREAMSTART - STREAMSTOP - TIME - TOPIC - TRACE - UMODE (User Modes) - UNAKILL - UNKLINE - UNQLINE - UNSHUN - UNZLINE - UPROP - USERHOST - VERSION - WALLOPS - WATCH - WEBADMIN - WEBSTART - WHISPER - WHO - WHOIS - WHOWAS - ZLINE

Example:
/hs <command>
/helpserv <command>
/msg helpserv <command>

HELPOP

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 is +h so that they can help the user.

Example:
/helpop Where can I go for help?

See HELP for a detailed list of commands.

HELPOPS

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 is +h so that they can help the user.

Example:
/helpops Where can I go for help?

See HELP for a detailed list of commands.

HIDETICKER

This command will prevent the scrolling message at the bottom of the Java client from scrolling. The scrolling message is called the ticker.

Example:
/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

Access help information on server commands.

Example:
/hs hs

This command allows you to get information on any server command.

IDENTIFY

This command is an alias for /msg nickserv identify. You can use it to identify for your current nickname by sending just your password or for any specified nickname by sending that nick and its password.

Example:
/identify Surel MyP4ss

This is a simpler and more secure way to identify, since you are less likely to have a typo send the command to the wrong person.

INFO

Displays information about the server you are connected to including up time, address, version, and how to connect.

Example:
/info

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

This command is used to invite people to join a room. The server will send a message to the user inviting them to join and allowing them to enter through +i. This is the only way to let someone into a room that is +Iif they are not at least a UOP in or have bot access to it.

Example:
/invite residue #support

In general, if you have an invite only room, this is how you will let people join. You generally only want to invite people you know, because random invites are usually considered rude.

ISON

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 nicks that are online.

Example:
/ison Surel

This is fast way to check if a nick is in use. You could use the /whois nick 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

The join command lets you enter a room and for java users parts them from the rooms they were in. 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 room name. Normally the # symbol is considered to be a part of the room's name. The example below would have you enter #webmaster. The maximum room name width is 200 characters.

Example:
/join #webmaster

Rooms are the virtual environments in which people chat. When you are in a room, you see all of the text sent to the room, as does everyone else present. While you can have private conversations with individuals who are in the same room as you are, or even with people who are elsewhere if you know their nicknames, most chat takes place in rooms. You can be in multiple rooms at the same time, but it can become confusing. Some networks may restrict the number of rooms you can be in simultaneously. It is generally best to be in a very small number of rooms that are moderately active. Java users can also look at the NEWJOIN command.

KICK

Used to force people to leave a room. The comment field is not required but will be sent to the client after they have been kicked. Only people who are opped in the room, AOPs and higher or those moded +o, can kick others out.

Example:
/kick #webmaster Phillip Don't flood this room.

The room's ops may kick anyone for any reason, but this command should be reserved for people who are causing problems in the room. In general, rooms 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.

KILL

Used to forcibly disconnect someone from the server. This is usually used when someone is rude or is being disruptive. For global operators you can kill users who are on any server on the network.

Example:
/kill Jamie flooding

You can disconnect any user from any server on the network.

KLINE

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 the same way as room bans, except that they ban people from the server instead of from a room.

Examples:
/kline lamer@pm02.digex.net Flooding isn't allowed
/kline *@*.digex.net Flooding isn't allowed 30

A kline is often a good action to take against someone who refuses to behave despite having been killed a few times. They can still get onto the chat network if there is another server for them to use.

LFLASH

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 +n users will see newsflashes.

Example:
/lflash Greetings, special announcement ...

This is in many ways similar to wallops, although being +n is probably more common than being +w.

LINKS

This command will show all the servers currently linked together on the network.

Example:
/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

Shows all the public rooms 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 rooms that start with the word support. Private or secret rooms will not show up on the list.

Example:
/list support*
/list >10
/list <20
/list

The room list may be very large, depending on the network. You can use the command /lusers to see how many rooms are on the network. The list command will take some time to display.

LOAD

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 panel
MemoServPanel - 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 panel

Examples:
/load NickServPanel
/load BuddyList
/load OpPanel

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

Sends a notice to all network operators who are on the same server and set +g.

Example:
/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

Displays information about the number of users currently logged on to your server and the network. If you leave the server field blank, it will return with the current 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 than it will return the number of users that your server shows at the current time.

Example:
/lusers
/lusers webmaster.*
/lusers webmaster.webchat.org

MEMOSERV

This is an alias for /msg memoserv so that you can send MemoServ commands with less typing.

Example:
/memoserv list

This is just an easier way to send MemoServ commands.

MFLASH

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.

MKILL

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 and in the case of a channel where you want to clear a channel out completely.

Example:
/mkill pp23.ntsvr4-2.tor.idirect.com cloning

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.

Modes set properties on rooms and users. For more information on modes you can look under Channel Modes (cmode) or User Modes (umode).

Examples:
/hs cmode
/hs umode

MOTD

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. You can see the motd for another server by just typing the first part of the server name and then using a ".*".

Example:
/motd webmaster.webchat.org
/motd webmaster.*
/motd

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 rooms, and that may change as new rooms are added.

MOVE

This command will move a user to another room. It is very similar to the FJOIN command. If the user is in more then one channel at the time of the move then it will join them to an additional channel and will not remove them from any of their current channels.

Example:
/move John #spiderslair

This is primarily useful to force users to go to help rooms 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

This is an alias for /msg memoserv so that you can send MemoServ commands with less typing.

Example:
/ms list

This is identical to /memoserv but even shorter.

MSG

This command will allow you to send a private message to a specific user or send a message to an entire room. This command is exactly the same as PRIVMSG.

Example:
/msg Web How are you?
/msg #webchat hey guys, what's up?

Sending a msg to the room is exactly the same as speaking in the room. With some clients it is easier to specify the room in the command than to just speak in the room normally. Rooms that are not set +n will allow you to msg them even if you are not in them, but this is rarely useful. On the other hand, sending msgs to specific nicks is often useful. This is a good way to have private conversations or just send quick messages to friends.

NAMES

Show all of the nicknames that are in the specified room. If you are a server operator and no room is specified then it shows the nicks of all the users on the network. If you are not in a room and try to get the names list, +I users will not show up, but if you are in the room then you can get a complete list.

Examples:
/names #webmaster
/names

Some clients do not show the users in a room, and so you can use this command to list them after joining the room. 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

This command is for Java users only, it will allow the Java user to join additional rooms, without leaving any rooms they are in.

Example:
/newjoin #conferenceroom

The new rooms will show up on the bottom of the chat window as buttons that can be clicked on to switch between which room is being viewed. If something is said in a room that you are not watching, then the button will change color to inform you that you should look at that room.

NFLASH

This command will send a global NewsFlash Message on the network. The users will not know the nickname of the sender.

This command will also allow you to change the scrolling message in the Java client default theme. For further details on this please refer to the section Ticker in the Java parameters section. The users need to be mode +n to see newsflash messages.

Example:
/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.

NICK

This command will change your nickname to a new one that you select. This will update all the rooms that you are on. The example below would change your nickname to lucky. Nicknames are limited to 30 characters although some clients may have difficulty understanding more than 9. If so, use /quote nick <nick> or whatever that client requires.

Example:
/nick Lucky

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) although you can also use the away command.

NICKSERV

This is an alias for /msg nickserv so that commands can be sent with less typing.

Example:
/nickserv info Jennifer

This is simply a shorter easier way to send NickServ commands.

NOTICE

Sends a message into a room or to a specific user. Usually reserved for important messages.

Example:
/notice #webmaster Check out our new web page
/notice Phil What time is the meeting?

Notices are much like msgs. See msg. 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 msgs and send notices, this prevents the possibility of an infinite loop between two bots.

NS

This is an alias for /msg nickserv so that commands can be sent with less typing.

Example:
/ns info Jennifer

This is identical to the /nickserv command except even shorter.

OPER

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.

Example:
/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. This command puts you on-duty and marks you as an oper. To de-oper /mode <nick> -o. In order to oper you must have an oper definition, your mask much 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

The part command has you leave a room. The other people in the room will see the message if you send one. The example below would make you leave the room #webmaster.

Example:
/part #webmaster See you later.

You don't need to use a part message, but many people like to use it either to say good-bye or to include a small personal quote, much like an email signature. Parting a room has you leave that room, but remain on the chat network and in any other rooms you might be in.

PASS

The pass command has the same functionality as the identify command used with NickServ. See identify.

Example:

/pass mypassword

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.

PING

This is a server function used to determine if a client is still responding on the server. Many times because of Internet routing you will drop off the server without telling the server you're gone. If the server doesn't get a PONG when it sends out a PING the ghost connection will get terminated.

PRIVMSG

The privmsg command has the same functionality as the /msg command.

Example:
/privmsg #webchat hi y'all!
/privmsg residue How's it going?

The command takes at least 2 arguments -- an object name, and a property name (or the reserved character '*') -- and returns a variety of numerics.

The object name can be the name of a nickname, the name of a channel or a GUID.

The property name depends on the object type, and the attributes of the object.

Example:
/prop mark language Spanish
/prop #lobby joinmute 5

PROTOCTL

PROTOCTL is sent during the log in process to tell clients the capabilities of the server. This is not a user command.

QLINE

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:.

Example:
/qline badname offensive nickname

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

Causes the server to terminate your current session. You are free to log back on after issuing this command.

Example:
/quit I'll be back in awhile.

/quit

This is much like part, except that you leave the network instead of just a room. Everyone you are in a room with will see you leave. People who you are talking to with private messages will not know you have left unless they have you on their watch or buddy list. They will receive a no such nick/channel error message if they try to message you after you have left, unless someone else starts using your nick. It is generally best to inform people you are talking to that you are leaving before you quit.

RAKILL

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.

Example:
/rakill lamer@pm02.digex.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.

REHASH

Used to to clear temporary settings such as klines and qlines.

Example:
/rehash
/rehash chat2.*

A good command to use at the end of an event, or every so often on a community chat server.

RESTART

This command will restart ConferenceRoom. It will reset the /lusers information, it will not reset the database or the configuration settings in your ConfRoom.conf file. All users will be forced off the server while it quits.

Example:
/restart

This will force every user off the server while it shuts down. Then the server will start up again and people can rejoin. Since it is very disruptive it should only be used if necessary.

ROLL

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.

Example:
/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.

Note: mIRC will eat the first die, so if you're using mIRC then add one die to your roll to get the correct output.

SAJOIN

This command will allow you to join rooms that are locked, keyed or have bans set against you. You will also not be able to be kicked out from any room you entered with an 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).

Example:
/sajoin #test
/sajoin all

If the people running a room 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 room and remove anyone who is misbehaving. This command can be used simply to make you unkickable.

SAMODE

This gives the services administrator the ability to set modes in a room without being a room operator.

Example:
/samode #test +o Steve
/samode #test -i

This is a good method for taking control of any room 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 room.

SERVER

This command is for chatting with an IRC client, and allows you to connect to another server. It will disconnect you from the server you are using and try to connect you to the server you specify.

Example:
/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.

SERVICES

This command will call upon NickServ commands. See notes above for NickServ help.

Example:
/services help register

This is another alias to make the commands easier to type. You can also see ns under the nickserv command set.

SERVSTART

This command will restart your services while you are online.

Example:
/servstart

This is the easiest way to bring services back if they are removed for any reason. See @shutdown in the operserv root commands to shut services down.

SERVSTOP

This command will stop your services.

Example:
/servstop

This is the easiest way to stop services.

SET

This command works simultaneously with the AdminServ FIELD command. Any FIELD added using AdminServ FIELD would then be SET using the /SET command. SET can either be used by a network operator or by a user, depending on the level of the FIELD you added.

Example:
/set Jennifer UserComment asks too many questions

If you are not using the web interface, the client might not understand this command, so use /quote set <nick> <field> <comment>. The fields are a good way to give people additional information about yourself. Remember to only provide information that you do not mind making public.

SHOWTICKER

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.

Example:
/showticker

This command undoes the hideticker command so that you can once again see the ticker.

SHUN

Allows you to specify nicks that will not be able to send private messages or notices on that specific server. You can also shun a user from speaking in a particular room; 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. If you send the SHUN command without any parameters you will see the entire shun list.

Examples:
/shun Mark testing
/shun #WebMaster Mark

This can be used on people who have been harassing or flooding people through private messages or notices. They can still talk in rooms, but the room operators can keep an eye on things. They can also use other servers where they are not shunned, if there are any. 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 rooms if a particular user is causing problems there, but generally behaving elsewhere.

SILENCE

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. To use the silence command, specify /silence plus a user@host mask or nickname. 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

Example:
/silence rowdy
/silence Flooder!trill@pm02.digex.net
/silence *!*@*.digex.net
/silence -Rowdy!*@*.digex.net

This is a good command to stop people from annoying you. You will see anything they say in rooms 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.

SQUIT

Causes the specified server to be disconnected from the network. Use the /connect command to connect the server back to the network.

Example:
/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 globop before rerouting, in case someone has a good reason not to reroute. It is also nice to wallop before squiting so that users who wish to be kept informed will expect the split.

Shows statistics for the server you designate, if you don't specifically designate a server it defaults to the server you are on.

Commands:
c - Connections, h - Hubs, i - Allowed Hosts, j - Client Type Count, k - Automatic Kills, l - Links, m - Commands, o - Operators, q - Qlines, Q - Send Queue, u - Uptime, U - Unknown Connections, V - Streaming Server, w - Statistics, x - Unconnected Servers, Z - Internal Information, 1 - Memory stats, 2 - System stats, 4 - Resolver information, 5 - Version history

Example:
/hs stats <command>

Shows statistics for the server you designate, if you don't specifically designate a server it defaults to the server you are on.

Commands:
AUTH - Authorize a user or channel.
DEAUTH - Deauthorize a user or a channel.
FEED - Specificy who can feed a stream.
INFO - Get specific information about streams.
JOIN - Join a specified channel stream.
PART - Part a specified channel stream.

Example:
/hs stream <command>

STREAMSTART

This command will start the streaming server.

Example:
/streamstart

If for some reason the streaming server is offline you can start it with this command. Remember that you can check current status using the INFO command.

STREAMSTOP

This command will stop the streaming server.

Example:
/streamstop

Use this command if you need to shut down the streaming server completely or to restart it. Remember that you can check current status using the INFO command.

TIME

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

All Users (or only room operators if the room is mode +t) can use this command. The topic command lets you change the topic of a channel, topics can be up to 80 characters long.

Example:
/topic #ConferenceRoom The webmaster Support Room

The topic is one of the first things people see about a room. The topic often gives some information about the room, or highlights an amusing quote that came up in the room recently. The specific use of the topic varies from room to room, but the topic should generally reflect something about the conversation going on in the room. Most rooms will limit the topic command to room operators to prevent topics that they dislike.

TRACE

Show the route between you and that server.

Example:
/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.

Sets options on yourself You can use the /umode command only for the nickname you are using at the time. Operators can set modes on users by using the target nickname.

Available user/oper modes:

a - Services Administrator, b - ChatOps, c - Clients, e - DCC, E - English, f - Flood Notices, F - French, g - Globops, G - German, h - Helpops, i - Invisible, j - Java, k - KillMode, L - Language Filtering, m - Messages, M - Malaysian, n - NewsFlash, o - Operator, p - CTCP, q - Quiet, r - Registered, R - Recognized, s - Server Messages, S - Spanish, t - Reports, w - Wallops, x - Hash Host, X - DeHash Host, y - Whois, z - Services Agent

For more information type /hs umode

Examples:
/hs umode <command>

UNAKILL

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.

Example:
/unakill mark@*.webmaster.com

This can be a way to give someone a chance to come back onto the network while still limiting their use and keeping a close eye on them. But generally you will want to remove akills globally rather than locally.

UNKLINE

Will remove a kline from your server. Note: you must match the user@host information exactly or the unkline will not work. You can use wildcards to erase multiple klines at one time.

Example:
/unkline lamer@pm02.digex.net
/unkline *@*.digex.net

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

This command will remove a temporary QLINE from your qline list. Qlines are prohibited nicknames. To place a qline please see QLINE.

Example:
/unqline badword

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

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.

Example:
/unshun Webmaster

Shuns should generally be temporary measures unless the person is aware of being shunned. Otherwise it can be very confusing to the user.

UNZLINE

This command will remove a zline from the /stats k list, the zlines are prefixed by a z. See zline for more information.

Example:
/unzline 999.999.99.999

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.

USERHOST

Returns the user@host information for up to five users at a time.

Example:
/userhost josh phil

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

Gives the current version of the server you are logged into and information about the modes the server is set in, such as, CR1.8.1.win32.ws2 irc.webmaster.com dnfu

d - DNS
f - Flood control
u - Users are able to register channels
A - Alpha NT
B - BSDi
D - Digital Unix
F - FreeBSD
H - HPUX
I - IRIX
L - Linux
N - NetBSD
S - Solaris
ws2 Winsock2
win32 Windows 95/98/NT

Examples:
/version webmaster.webchat.org
/version webmaster.*
/version

Any user can retrieve version information. Although it is unlikely you will need the information.

WALLOPS

This command will send a message to all users that are set mode +w.

Example:
/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 or one of the other methods of notifying most or all users.

WATCH

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 names or rooms into each watch command. You can send multiple watch commands. This command will allow you to see a user connect/disconnect from the network. If you are watching a room, it will tell you when the room empties or has a user join after it was empty.

Commands:

+<nick|room> Add nick(s) to the watch list
-<nick|room> Remove nick(s) from the watch list

Flags:

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 watch list, indicating which users are online and which are offline

Example:
/watch +JoelKatz +WebMaster +Samurai +#Spiderslair
/watch s
/watch L

Watch is designed to let you know when the things that interest you 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.

WEBADMIN

Forces the web server to restart.

Example:
/webadmin

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.

WEBSTART

Forces the web server to start.

Example:
/webstart

This is the same as WEBADMIN.

WEBSTOP Usage: WEBSTOP

Forces the web server to stop.

Example:
/webstop

Used to stop the web server.

WHO

When a who is done on a room you are in, you will get a list of the nicks, masks, and "real names" of everyone in the room and their status in the room. 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 is +I, invisible. When a who is done outside the room only people who are not +I will show, and if the room is secret or private no names will show. When a who is done on a nick, you will see the person's name, mask, and "real name".

Examples:
/who #ConferenceRoom
/who Jennifer

A who is a good way to get a list of people and their masks. The who command for a room 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 room 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 rooms a /names is better for most purposes because it is shorter and a /who may fill up your screen.

WHOIS

Displays information about a nickname. This includes the host that they are logged in from, the server they are logged into, the public rooms they are in, private rooms you are both in, and the number of seconds that have passed since they last communicated with the server. There may be additional information depending upon what fields they have set.

Example:
/whois webmaster

Whois is generally the first command you would use on people to learn something about them. For related commands see who, whowas, and names.

WHOWAS

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 in the whois command.

Example:
/whowas webmaster

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

This command is a form of firewall for your server. This will prevent problem users from a specified host address from accessing the server.

Example:
/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 sent on the numeric version of the address.