SCRIPT ADD

    Usage: SCRIPT <profile> ADD

    Creates and names a new empty script.

    Example:
    /as script open add


    SCRIPT COMANDS

    Usage: SCRIPT <profile> COMMANDS

    INSERT|DEL|APPEND|ERASE|LIST [<parameters>]

    This defines the actual commands to be executed by the script. The semantics are similar to those of greeting messages and motds as listed under the CHAN command and CLIENT SET MOTD. It is important to remember to erase an old script before replacing it with a new set of commands. You can only include AdminServ commands, but the AdminServ UTIL commands have the same functions as certain server commands that you might want to script. See UTIL for more information.

    Example:
    /as script open commands append

    These are the commands that the script will run. It will run them in the order you list them. They will work exactly as if you sent them yourself in that order.


    SCRIPT DEL

    Usage: SCRIPT <profile> DEL

    Deletes the named script and all of its settings.

    Example:
    /as script open del

    This removes a script you never intend to use again, as opposed to disable which merely deactivates it.


    SCRIPT DISABLE

    Usage: SCRIPT <profile> DISABLE

    Temporarily disables the script.

    Example:
    /as script open disable

    The script can not be used until it is enabled.


    SCRIPT ENABLE

    Usage: SCRIPT <profile> ENABLE

    Enables a disabled script.

    Example:
    /as script open enable

    After you first make the script you will need to enable it.


    SCRIPT LIST

    Usage: SCRIPT <profile> LIST

    Lists the settings of the indicated script.

    Example:
    /as script open list

    It is a good idea to review your script before you allow anyone to use it.


    SCRIPT RENAME

    Usage: SCRIPT <profile> RENAME <newprofile>

    Changes the name of the script. Note that this does not affect the command as set with SET COMMAND.

    Example:
    /as script open rename daily

    This changes the profile name, which only affects how it is referred to within the AdminServ SCRIPT commands. You might want to change its name to something more descriptive or something simpler to type.


    SCRIPT SET

    Usage: SCRIPT <profile> SET COMMAND|ACCESS <parameter>

    The ACCESS setting controls who has access to starting or stopping a script. Available options are IRCOP, SA, ADMIN, and @<room>. IRCOP refers to network operators, SA to services admins, ADMIN to server admins, and the @<room> format to all users with operator status in the specified room.

    The COMMAND setting changes the command with which the script is executed. Once a command (in this example, open) is set, anyone in the ACCESS list can execute the script by typing '/<commandname>' (for example, '/open').

    Examples:
    /as script open set access admin
    /as script open set command open

    The script will appear much like any server command and you issue it in the same way. In this way you can add commands designed to do things that are useful on your server.