CHAN ADD

    Usage: CHAN <room> ADD

    This command adds a room to the list of official rooms to be managed. You will still need to specify a bot to manage the room.

    Example:
    /as chan #conferenceroom add This is the first step to take when you want to have a room managed by a server bot.


    CHAN BOT

    Usage: CHAN <room> BOT ADD|DEL|EMPTY|LIST [<bot>]

    These commands allow you to add or delete multiple bots from the same server to a room. This is different from SET BOT, which will allow you to set one bot to manage the room.

    ADD - Add a bot to the room
    DEL - Remove a bot from a room
    EMPTY - Remove all bots from the room
    LIST - List which bots are assigned to the room

    Example:
    /as help chan bot <topic>

    One bot per room is generally sufficient. But you might have reasons to add multiple bots. For example, you might have one particular bot that sits in an entire set of similar rooms, such as all the public rooms that provide help. Then if someone needed a list of those rooms they could /whois the bot.


    CHAN DEL

    Usage: CHAN <room> DEL

    This removes a room from the list of officially managed rooms.

    Example:
    /as chan #conferenceroom del

    If you have services this will not effect a room's registration in any way.


    CHAN GREETING

    Usage: CHAN <room> GREETING <command> [<value>]

    This command allows you to make a welcoming message for users as they enter the room. The way you configure a greeting message is the same way you make your MOTD or create scripts. The del function will delete a specific line; use the list function to find out which line you wish to delete. The message will be delivered by whichever server bot is managing the room.

    APPEND - Add a line to a greeting.
    DEL - Delete a greeting line.
    ERASE - Erase your entire greeting message.
    INSERT - Insert a line above the line mentioned.
    LIST - List the greeting.

    Examples:
    /as help chan greeting <command>

    It is generally a good idea not to let the greeting become too large, since it will be sent to someone every time they enter. If they enter often or if the server they are on splits and then rejoins, they will be sent it multiple times, and long messages become annoying. There is no way to enter the room and avoid the message. Use it for important information or for a short greeting.


    CHAN LIST

    Usage: CHAN <room> LIST

    This command will display all the settings you have specified for the room.

    Example:
    /as chan #conferenceroom list

    This is a quick and easy way to check everything related to how a room is set up.


    CHAN LOG

    Usage: CHAN <room> LOG <[on|off]|[param]>

    These commands allow your primary room bot to log the conversation in the room to a file that you specify. You must have a bot in the room to do the logging. This is available in the Enterprise edition only or with the Scribe module.

    OFF - Turn off logging
    ON - Turn on logging
    PARAM - Set the file to log to

    Examples:
    /as help chan log <topic>


    CHAN SET

    Usage: CHAN <room> SET <value>

    This command will define settings for the specified room. Since the server bot works in conjunction with the chan commands, your server bot will keep your room's topic and modes if you configure the server bot to do so.

    BOT - Define which bot to use.
    JOINFURL - Force a URL on a local Java user.
    MODE - Set the default room modes.
    OPFURL - Allow channel operators to furl to channel users.
    PASSWORD - Set the room's password.
    QUEUE - Channel queue configuration.
    STREAM - Streaming server frame speed and limits.
    TOPIC - Set the default topic.

    Example:
    /as help chan set <command>

    The bot will set the topic or mode each time the server restarts. If the modes conflict with a modelock set for the room, the bot will override the modelock. You can also use the bot to set a specific key or limit, which you cannot do with a modelock. Normally you should not set a mode that conflicts with the modelock, but you might wish to do it with l or k. This would allow you to have a set key that should be kept set, yet if anyone tries to change the key, services will not let them to set a new key. This means that the room will always either have the key that you set or it will not have a key. But it will not be keyed to prevent people who should be able to join from joining. You will generally want to use a topiclock if you want a specific topic.