(Info-Names)
INFO 
Format: /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
Format: /invite nick #room
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
Format: /ison nick1 nick2 nick3...
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 Mike
/ison Mike Dan
/ison Mike Dan Laura
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
Format: /join #room
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
Format: /kick #room nick comments
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
Format: /kill nick reason
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
Format: /kline user@host reason
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 Flooders aren't allowed
/kline *@*.digex.net Flooders aren't allowed
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
Format: /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 +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
Format: /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
Format: /list room mask
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
Format: /load panel name
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
Format: /locops message
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
Format: /lusers server name
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
Format: /memoserv
This is an alias for /msg memoserv so that you can send MemoServ commands with less typing.
Example:
/memoserv list
/ms list
/msg memoserv list
Any memoserv command can be sent with /memoserv /ms or /msg memoserv
MFLASH
Format: /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.
MKILL
Format: /mkill IP address reason
This command will mass kill users from the same IP address, it is usually used when users have been cloning on a server.
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.
MODE
Format: /mode nick|#room +|-modes nick(s)
Modes set properties on rooms and users. For more information on modes you can look under Channel Modes(cmode) or User Modes(umode).
MOTD
Format: /motd server
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
Format: /move nick #room
This command will move a user to another room. It is very similar to the FJOIN command, however, this one will make that user part all the rooms he/she may be in.
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.
MSG
Format: /msg nick|#room
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?
/privmsg #Help Hello!
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
Format: /names #room
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.
