%_load manual.var%
Online Administration
ConferenceRoom also includes online administration within the chat environment. This feature is very handy for making on the spot changes to the server. Every aspect of ConferenceRoom can be changed online as well as with a web browser or the configuration utility. For more information about the online command set see the ConferenceRoom Command Reference Guide - Server Administrators section.
Windows Configuration Utility
Use the desktop task bar 'Start' button to enter the following menu sequence: Start->Programs->Webmaster->Configure CR. The Configure CR1.8 utility will launch and remain local to your desktop. Clicking on the spider icon on the Crstatus Monitor will also launch the Configuration utility.
Windows Services Manager
In most cases you'll want to use the Windows Configuration Utility to manage your ConferneceRoom Service. However, in some cases you might want to install or deinstall the service manually. Use the command line to execute crsvcmgr.exe with any of the following switches:
/a -- install & auto-start
/i -- install without auto-start
/d -- install disabled
/u -- uninstall
Web Administration
To use web-based administration the ConferenceRoom chat server must be running. To gain access to ConferenceRoom from remote systems you must either use the name and password that you defined during the installation process or define a new Operator entry (See Operators) and make sure the Server Administrator flag is checked. The entry name and associated password and hostmask will allow remote access to the server. To gain remote access, point your web browser to the system and port on which the ConferenceRoom administrative services are running (This is defined in the Web section of the ConferenceRoom Properties when configuring).
For example, in your web browser type:
http://hostsystem:port/admin/default.adm
So if your host system running ConferenceRoom is named chat.yoursystem.com and the port is 8000 then you would type: http://chat.yoursystem.com:8000/admin/default.adm
ConferenceRoom will then ask you for your operator nick and password. Once they are accepted the Remote Administration Console will be displayed.
Note: The only option that is not available through the web-based remote administration is the ability to turn off the administration services. The administration services can only be turned off when you are on a browser or chat client on the same system containing the ConferenceRoom software.
The top section of the header contains the main categories available. Below the line contains the subcategories for whichever section is currently showing. The server starts with the Home page showing and its subcategories are Help and Update. Remember that you have the option of configuring ConferenceRoom online or with the Configuration panel residing on the host. Each option category is described below:
Home: This area has the controls for stopping and starting the ConferenceRoom server and web administration services.
General: Basic configuration information including the ConferenceRoom server name and network parameters.
Server: Configure the ConferenceRoom server to connect to other ConferenceRoom or ircd servers, edit server bots, network rooms, server messages, and view statistics.
Security: Set general security options, specify domains and users that may not access the ConferenceRoom server, edit profanity filtering options, control prohibited nicknames.
Users: Access control parameters for access to the ConferenceRoom server and configure who has access to commands that control the ConferenceRoom server.
Services: User and channel/room management and configuration as well as Server bots and managed server channels.
Web: Set up information for the ports, web based themes for the Java chat clients and the administration services.
Scribe: Control logging options, events, and scripts.
Upon completion or update of ConferenceRoom configuration, using the Remote Administration Console click on the submit button at the bottom the page for the server to accept the configuration information. If you want to revert to the configuration settings as they were before you made changes, click on the Reset button and the old values will be restored.
We will go through each option and AdminServ commands in details as well. Now we'll see how to make additional configuration settings to your server. You should remember that all the changes to your server can be done through the Web Configuration panel as well as using the AdminServ commands. For complete details and examples on AdminServ please refer to that section.
The home page for ConferenceRoom provides you with the current status of ConferenceRoom as well as options for starting and stopping the difference aspects of the server.
Stop Chat Server (/die): This function will stop the chat portion of the server.
Run Chat Server: This will start the chat portion server if it is currently not running.
Rehash Chat Server (/rehash): This option will rehash your server configurations.
Stop Web Administration Services (use /webstart online to restart): This option will turn off the administration web services. You must use the /webstart command online to restart the administration web services or restart them with the Windows Configuration Utility. Note that this command will only work when you are on the system that you wish to stop. This is a security feature that ensures that you will always be in a position to start the server.
Stop ConferenceRoom (Includes Administration services): This shuts off ConferenceRoom completely. Note that this command will only work when you are on the system you wish to stop. This is a security feature that ensures that you will always be in a position to start the server.
Valid Name: irc.webmaster.com
Invalid Name: webmaster irc
Warning: Servers that connect to your server must supply your Server Name in the Name field of their server connection profile. See: Connecting to other servers.
Example: chat.yourdomain.com
Description: (not required) This is a short description of your server which will be displayed when a user types the /admin or /info commands or in a /links command.
Example: Chat Server [127.0.0.1] or WebMaster's Chat Server
Contact Info: Allows you to have a point of contact for your server. This is so that people using the server can contact the administrator. This information is also available when the /admin command is used.
Example: Contact: John Doe johnd@yourdomain.com
Key: This will read TRIAL unless you have a registered version of ConferenceRoom, then your key will be encrypted for your protection.
Example: 7000,6660-6669
Limit connections: The maximum number of connections (which is equal to the number of users plus the number of server connections) varies depending upon the Edition of ConferenceRoom purchased. The Personal Edition supports up to 100 connections, The Professional & Developer Editions support up to 1000 connections and the Enterprise Edition supports up to 10,000 connections. When the 30 day free demo of ConferenceRoom is downloaded, It is automatically set to 10 connections. When ConferenceRoom is purchased, the software key automatically sets the number of connections to the maximum allowed for the edition purchased. If you want to lower the number of connections that ConferenceRoom will allow, enter the number here.
Host Name: This is the name of the computer the server is running on.
Server Mode: This is where you will select if you want to run your server as a hub or leaf. If you plan on accepting another server to link to yours select the hub option. By default the server is automatically a leaf, which means you cannot allow downstream connections.
Disable DNS Lookups: Client addresses will appear as IP addresses rather than host domains on the server if this option is enabled. In general, this option is not checked.
Example: user@127.0.0.1 instead of user@host.domain.com
Network-wide: Enable the news to be sent to all servers on the network or only the local server.
Flash Priority: Controls how important news has to be to be added to the newsflash queue. The higher the priority the less news will be sent to the user. If you set the priority to medium then news of medium importance and high will be sent as newsflashes but not low priority news.
Initial Priority: Sets how important news has to be to become part of the starting queue of news for a user.
News Flash Interval: Controls how often newsflashes are sent.
This allows you to see a brief description of all of your current bots. You can edit one by clicking on its name. You can delete a bot by marking delete next to its name and then submitting the form.
This form allows you to create a new bot. The default settings are shown. You can edit each field.
Nick Name: This is the name of the bot. A bot uses a nick the same way any other client on the chat server will.
User Name: Select the userid that will show up in the bot's address. This will be seen by users who "/whois" the bot. The default would have the bot appear as service@conference.room.
Host Name: This selects the host the bot appears to be on. It works with the user name to create the bots apparent address.
Real Name: Controls what will show up in the name field during a"/whois".
Password: This field is optional. If a password is provided then anyone who knows the password can use it to control the bot. You can leave a bot passwordless but have it know specific passwords for each room, allowing people to still use the bot to op themselves in particular rooms.
See the channels section below or in the ConferenceRoom Command Set AdminServ section for more information, specifically the BOT and CHAN commands.
Channel Name: Enter a room name. The room does not need to exist yet.
Bot Name: Assign a bot. You can only assign currently existing bots to the room. If you need help making a bot, you can read through the Agent section of the Server help.
Password: This is optional. If a password is used then anyone with the password can access the bot. If not then the bot can only be manipulated through server administration commands. You can still have passwords for individual rooms and let people use the bot to op themselves in these rooms with that password. See the Channels section for more information.
Modes: The modes you want the bot to enforce for the room.
Topic: The topic the bot will set for the room.
Greeting: A message that will be sent by the bot to everyone joining the room.
Note: Bots are explained more fully in the ConferenceRoom Command Set AdminServ section. See BOT and CHAN commands.
Profile Name: The name you want to reference this profile. It can be anything, but it's usually best to use the server name or something short and descriptive.
Server Name: The name of the server, for example webmaster.webchat.org.
Serial Number: The serial number of the server you wish to connect to.
Ping Frequency: How often the server will send pings to make sure the connection still exists.
May Connect DownStream Servers: When enabled the server can connect to many other servers, when disabled it can only connect to one. If you enable it, the server becomes a hub. If you disable it, then the server is a leaf.
Enabled: The server settings do not take effect unless they are currently enabled.
Hostname: This field contains the path/address of the connecting server, either the IP address or the hostname.
Port: Enter your server connecting port for example 7300, as much as possible try to take a different port than your user and web ports.
Strict Host Checking: Requires the server to have the expected IP address. The server address must be placed in the Hostname field. If it is not checked then we heavily recommend using the IP address of the connected server in the Hostname.
Autoconnect: Causes your server to try to reconnect if the connection breaks.
If you have a dynamic address (i.e. one which is assigned to you every time you log on - typical of dial-up connections), you don't need to reconfigure your server each time in order to network. If the hub has a static address, any number of dynamic address servers can connect to it.
The dynamic servers can connect to the static hub by configuring the servers only once.
On the hub, define a downstream connection (for the leaf) and specify only the "servername" and "Password" fields. On the leaf (which has dynamic addresses), enter an Upstream Connection defining the hub. Be sure to provide complete information and select the AutoCorrect option.
Helpful Stats Commands /stats w: Server stats /stats x: Servers not connected to you. /stats c: A list of Servers which can connect to you. /stats u: Server Uptime
Disconnect user when flooding detected: When set on users will not be allowed to send too much text without being disconnected. Too much is defined by the other two options.
Note: It is highly recommended that Windows95/98 users run ConferenceRoom with flood protection on.
Minimum seconds between messages: Sets how quickly users may send text without it being considered flooding.
Maximum penalties before disconnect: Sets how much flooding is allowed before the user is disconnected.
Users Can Issue STATS Commands: When on all users can issue /stats commands when off only network operators may. See STATS in the Server Commands section of the ConferenceRoom Command Set for more information.
PART/QUIT Reasons: When on part and quit messages will be shown. When off the parts and quits will still be visible, but the messages will be surpressed.
Maximum Bans per Channel: Sets how many bans may be in a room's ban list.
Minimum users for Chan List: Sets how many users must be in a room before it will show in a /list command.
New Channel Creation: Sets who may create a new room. If users try to join rooms that don't already exist and the authorization is set higher than All Users then they will receive a message telling them they cannot join because the room does not exist. When it is set to All Users then the room will be created for them and they can be in it.
Action: Sets what the server will do when it finds an insecure proxy. It can do one of the following, Akill the user (ban the user from the server), Zline the user (restrict the address from being allowed to communicate with the server), Net Notice (send a notice to the ops on the network), Op Notice (send a notice to the ops on the server).
Proxy Version: Controls which proxies the server checks for.
Proxy Disconnect Reason: If you choose to have users disconnected automatically for insecure proxies you can create the message they will see. It is recommended that the message send them to somewhere where they can get help and information.
The Next option is the Network bans, which are /akill refer to the Appendix A for more details.
Perform Clone Detection: This is recommended unless another server is already checking for the entire network. Clones are multiple users from the same address. Sometimes they are harmless, like a cybercafe, and sometimes they are malicious.
Check Clients: Either for just your local server or for the entire network.
Issue Alerts: Either to local network operators or to all network operators. Clone alerts are sent, but operators must deal with the clones themselves. This is because only a human can probably tell harmful clones from innocent ones.
Default Trigger Level: How many users from the same address counts as cloning.
Set specific trigger levels by address. For example, if all your employees for example come in from office.webmaster.com you could set a trigger level of 100, which would ignore that IP address until it reaches 100 connections.
Host: The address for the specific trigger.
Level: The number of clients that will trigger a clone alert for that address.
The Security profanity filtering options allows you to manage what is appropriate and what isn't for your server.
Filter Which Messages: All will filter every private message that uses inappropriate as defined by your prohibited words list. Some will only filter messages that go to users who are +L. None will not apply any filtering to private messages.
Local Messages: This controls the server's reaction when profanity filters are triggered for messages to local users . It can either replace the offensive word with asterisks, drop the message entirely, or allow it to go through as sent.
Issue Local Warnings: When set on the sender of the message will be informed when a message contained inappropriate text. When set off the user will have no way of knowing that the message was filtered.
Remote Messages: Controls the same settings for messages not on the server.
Issue Remote Warnings: Controls warnings for users on other servers.
These options work the same was as the Private Message Filtering Options except they control how profanity filters work on text sent to rooms.
Filter Which Channels: All causes filtering to apply to all rooms. None causes filtering to apply only to rooms set +L.
Access Needed for Channel Filtering: This controls who may set a room +L. +L rooms will always be filtered, so if you don't want room messages filtered, set it to admin.
Local Channel Messages: This controls what local users see. Censor replaces the offending word with asterisks. Drop keeps the entire message from getting through.
Issue Local Warnings: Determines whether local users see a warning when they send messages containing profanity.
Remote Channel Messages: Controls what users on other servers see when offending messages are sent.
Issue Remote Warnings: Controls whether remote users receive a warning when they send inappropriate text.
This field is used to define what your server considers to be profanity. It starts out with no words, but one has been added for this example.
Check to Delete: Allows you to remove any prohibited word you find you want to allow.
Enter to Add: Adds new words to be filtered. Remember to select Submit after entering.
The bottom part of the security panel includes, local bans, which are referred to as Klines, and finally restricted address, which are commonly known as Zlines. We will view the details in the AdminServ section. The command reference for the security features are all listed in the AdminServ Manual.
The server allows you to prohibit users from using specific nicknames (i.e. offensive, obscene, confusing, misleading etc.).
Nickname: The nickname you wish to prohibit. Reason: The reason that will be displayed for why it cannot be used. This helps you keep track of your prohibited nicknames. This field is optional.
The server administrator may not want certain users (for example, users from a certain domain) to log onto the ConferenceRoom server. Preventing particular users from accessing ConferenceRoom may be necessary if those users attempt to interfere with the function of the ConferenceRoom server.
There are several kinds of bans, but they all work the same way; so they will be described together. Network bans are global autokills. They prevent people who match the ban from logging into any server. Local bans only ban the users from the one server; they can log on from others. Restricted IP Addresses are similar to akills but there are two main differences. First the user does not even get to log on enough to see the reason why the address is banned. Second, you must use the numeric address, not the resolved one.
Mask: The mask is composed of the userid and the domain. If you only include the domain it will ban all userids from the specified domain. The format of the mask is userid@domain. You can use a * as a wildcard. When restricting domains remember to use the numeric address.
Example: *.digex.net
Reason: Explanation for the ban. This is an optional field.
Example: Running clones on the server
Password: Password required to connect to the server. Leave it blank if no passwords are to be used.
Initial Mode: Define which modes the clients are given at sign on. To read about these modes please read Appendix A or type /hs umode while on your ConferenceRoom server.
Mode Lock: Restricts the clients from changing these modes.
Disable MOTD: Clients will not see a MOTD upon logging in. They can still view it by typing /motd.
No initial Lusers Info: Causes ConferenceRoom to not tell people logging on to the server the number of clients and servers that are currently connected. ConferenceRoom Java client users are always sent this information, even if this box is checked.
Alternate Welcome Message: With Alternate Welcome Message selected, ConferenceRoom will respond with: Welcome to the
Note: This functionality is useful when creating alternate connection classes. For example, on irc.webmaster.com, the MOTD is suppressed for web connections, and an Alternate greeting message is sent. This is for the benefit of the user, as the MOTD can be lengthy. This was accomplished by creating a new class with the Userid field set to Java, checking Alternate Message and deselecting MOTD.
Prohibit Multiple Connections: Does not allow multiple connections from an address. Checking this will prevent users from running clones on the server. If there is a computer from which several users may try to connect to ConferenceRoom simultaneously, define a separate Client Class entry for this machine and allow multiple connections.
Restricted to JAVA: Only users accessing the ConferenceRoom server from the World Wide Web through the ConferenceRoom Java client may gain access to ConferenceRoom.
When editing a client class you are given a few additional options.
Ping Frequency: Determines how often the ConferenceRoom server checks to determine if clients (users) are connected. Time outs can be caused for multiple reasons, such as the user losing Internet connectivity, disconnecting, or a lost router route. If users are experiencing frequent ping time outs, this value may need to be raised.
Connection Limit: Sets how many users may be on this class before it is considered full and cannot be used til someone logs off. Your last class will usually have a very high connection limit.
Enable: You will need to check this to activate a new client class.
Masks from which clients may connect. If a user does not match any of the masks in a client class then the user won't be able to use that client class. In most cases, this field should contain a *, which will allow users from any domain to enter the ConferenceRoom server.
Examples:
Appears to all users when connecting to the server and when the /motd command is used.
Example:
Modify Client Class
Client Masks
*@* This will allow any domain to connect.
*@*.domainname.com This will only allow clients from domainname.com to connect.
Message of the Day (MOTD)
Welcome to our chat server.
Discussion of the latest releases and online help available on #ConferenceRoom
For help type; /msg residue Can you help me?
The Operators Administration panel allows you to give network operator status. There are 5 classes of Operators local, helper, global, services administrator and server administrator. Local operators cannot do much of anything. They have no privileges marked. Helpers can see Help messages and chatops. Global operators are what is generally thought of when people say network operators. Global operators have access to most of the important commands. Services administrators can retrieve passwords and change the modes for any room. Server administrators can change the settings for the server itself. Each rank requires that the person be more and more trustworthy.
Entry Name: This is the nickname for the operator. If your server is running services you should make sure the person has the nick registered. You can oper without using the operator nick, but if an operator's nick is not secure someone may manage to trick people into thinking s/he has operator status.
Password: The password for the operator entry. Passwords care case sensitive, "bob" is different from "bOb". The password should be secure, but something the operator can remember. Good passwords are at least six characters and not a real word or name in any language.
The user must match a mask in the operator specification to use the entry. If no masks are set then no one can oper with it. This information tells ConferenceRoom which domains have access to the server as an administrator, creating an additional level of security against hackers. Be sure to use appropriate wildcards ("*") when your users are accessing the server from dynamic IP addresses and hostnames. An operator definition may have multiple user specifications.
Note: If you receive a message saying "no o-lines for host" and you are sure you are typing the OPER command exactly as it appears in the usage tip, then the problem is that your current userid and/or hostname does not match any of the user specifications. Do a /WHOIS on your nick to see what your current userid and hostname are. If you still don't see the problem, please delete all the user specifications and try again.
UserID: You will find this by doing a /whois on the user while he or she is logged on. It's the information proceeding the @ sign.
Example: for ident@server.isp.com the userid would be "ident".
Hostname: The domain; it's the information you will see after the @ sign Example: for ident@server.isp.com you might use either "server.isp.com" or "*.isp.com"
+A: Gives the person complete control over the server. This should only be for people who are entirely trusted. +h: Allows operators to see help messages and set their nicks +h, which marks them as very helpful. +a: Allows operators to retrieve room and nickname passwords. It also allows them to change room modes for any room. +g: Gives global operator status. This is the most common setting. The operator can /kill any user and can route servers, but cannot use the powers of a service admin (+a).
Provide Network Services: You will want to provide them unless another server on the network is already doing so. If another server is then keep them disabled.
Server Name: This is for aesthetic reasons. Services can appear to be on any server name. "services.net" is good because it makes it clear that it is a special server for services.
Network Name: Put whatever you want to name your network here.
User Name: This is what will appear as the ident of the service's agents.
Host Name: This will be the domain of the service's agents.
Nickname Expiration Days: How many days a nickname has to go without being used before it will expire.
Channel Expiration Days: How many days a room has to go without a room operator joining before it will expire.
Only Operators Can Register: If set to not then any user may register a room.
To search for a nickname you can use * as a wildcard. Or you can put in the exact nick to turn up its entry to edit it. You do not see a list of all currently registered nicknames because on most networks this would be incredibly lengthy.
Nickname: This is the nickname that will be registered. It must not be previously registered.
When you find a nick through the search, it gives you several options you can set.
Real Name: The information that will show in a /whois in the name field.
Password: The password allows complete access to the nickname's settings, even allowing the user to drop the nickname. Passwords are case sensitive, "bob" is different from "Bob".
Email Address: This information is stored but not shown publically unless showemail is set on. It allows services administrators to email lost passwords back to users.
Nickname: Do not edit this field. It is just here to show you which nick you are currently modifying.
Registered: Displays the registration date.
Last Seen: Displays the last time the nickname was seen used by its owner.
User@host: The mask associated with the nickname.
Real Name: The text displayed in the name field.
URL: Optional field to publically display an URL with the nickserv info on the nick.
Password: The password for the nickname.
Nick Kill: When set on anyone who uses the nick without either matching a mask in the access list or identifying with the password will be forced to switch nicknames after 60 seconds.
No Op: When set on the user cannot be added to room operator lists.
Searching for registered rooms works the same way as searching for registered nicks. You can either enter the exact room name (including the # sign) or put in asterisks as wildcards. Once a room is located, you can edit its entry.
Channel Name: Put the intended name for the room, including the # sign.
Founders Nickname: The founder's nickname must be registered. The nick listed will have control over the room.
Password: Insert the password that will give full access to the room. Passwords are case sensitive. For example, "bob" is different from "boB".
This gives you a few more options than when you first create the room. The additional options are explained below.
Modes: You can set modes that will be enforced by services. Modes locked plus will always be set. Modes locked negative will be unset by services if anyone tries to set them. You cannot lock k or l on, only off. For more information on room modes see ROOM MODES in the Server Commands section of the Command Set.
Opguard: When set on only nicknames defined in the room's AOP and SOP lists or the founder will be able to be opped in the room. If anyone else is opped, services will deop the person.
Ident: This causes services to ignore nickname access lists when deciding whether to op people in the room. It forces room operators to identify with their nickname passwords to get their status.
TopicLock: When set on services will remember the last topic and reset it if the room empties and then is used again.
Users can register their nicknames and rooms through a web panel registration server. They can also do it while connected on the server (refer to the NickServ and ChanServ section of this manual for online registration)
The site is http://your.servername.com:port/services
It works the same was as the administrative web registrations work.
However, make sure that there is not web server software already using port 80 (like the Microsoft Internet Information Server IIS).
Warning: ConferenceRoom automatically enables its web interface on port 8000. If you have another server (e.g. Your primary web server running on port 8000), you must disable the web server by selecting the "Disable Web Server" setting or change the port number above to an unused port (e.g. 8080)
Disable web server: If a third party web server is used to serve the ConferenceRoom Java client or no web interface is desired, this setting will disable the ConferenceRoom web server.
Note: The information entered in the General configuration tab rolls over into the Web configuration tab, BUT you must go to the Web configuration tab and select OK to activate the information.
Web Access Log and Web error log: If you enable these options it will log all web access and or Web errors to files residing in your DB folder.
Default Channel: This setting selects the room where the user will automatically enter when logging on to the ConferenceRoom server. This setting will be plugged into the theme where the %channel% substitution variable is used.
Choose a Theme: A theme defines how the client or users interface looks to the people participating in a conference/chat. Select a theme or use the default ConferenceRoom theme. Themes resemble a chat client in their functionality. The themes are described on the same web page.
To connect to your server: Go to http://youhost:portnumber to connect with the java client. You must have a web server running.
This provides an example of the different parameter options for themes.
Current Log Events
This allows you to edit your existing logs. You can also leave them disabled when you do not want them active, but keep them defined so you can quickly enable them whenever you want.
Add New Log Event - Information
Log Event Name: This is the name of the profile. This is only useful for editing the information in this section. Try to pick something fairly short so that if you wish to edit it using online commands you won't have to do too much typing. Also make it something memorable, so you won't forget what this log refers to.
Enabled: The profile will not run unless enabled.
Channel: The room it is set to log.
Log to: Controls where your log is stored. Select whichever is appropriate.
Log File/Directory: This goes with "Log to" to specify exactly where the log is stored.
Web Path: Determines the extension for viewing the file on the web. You should have the file end in .htm or .html.
Title: This can be anything, but it is usually best to pick something descriptive.
Description: This can be anything, but a short accurate description is recommended.
Theme: This will affect what the log output looks like.
Start Time: The fields in order let you select: month, date, year, hour (from 1 to 12), minute (in five minute intervals), and AM or PM. The logging will begin at the start time assuming it is enabled.
End Time: This works the same was as Start Time and determines when it stops logging.
Interval: If you set an interval then it will continue logging every day/week/month at that time. Monthly intervals should not be set to go off on the 29th through 31st because not all months have that many days.
Current Events
You can select an event to edit it or mark it as enabled or disabled. You can also delete events you are no longer using.
Add New Event - Information
Event Name: This is the name for the profile.
Enabled: Allows you to enable or disable the profile.
Start Time: This takes the same paramters as logging, except that you type them into the field.
Start Script: You will get a menu containing all the scripts you have created. If you do not have the event start any script, then the event won't actually do anything. This script will run when the event starts.
End Time: This takes the same parameters as start time.
End Script: This runs a script when the event is ending.
Interval: Causes the script to run regularly or only once if you select that. Do not run scripts monthly if they are set to run between the 29th to 31st since not all months contain those dates.
Current Scripts
Allows you to edit current scripts, enable, disable, or delete them.
Add New Script - Information
Script Name: This is the profile name. The script name will show up in Events so that you can create events that run scripts at specified times.
Enabled: Only enabled scripts can be used.
IRC Command: This is the name you want to give the script that will be used on the chat network. The script will function as a server command. For example, if you put "bob" in this field then when logged onto the server you could type "/bob" to run the script.
Access Level: This sets the access needed to run the command on the chat network. Scripts can call AdminServ commands yet be run by people without AdminServ access if you set the script access level lower. This way you can allow people at different levels to have access to specific commands or sets of commands.
Access Channel: If you set the level to chanop, then you can set it to give access only to channel operators in a particular room.