An AutoOp is a user with special privileges on a channel; the main one being that they will be automatically opped (receive operator status - @) by ChanServ upon entering the channel. Others include any setting the founder of the channel may set to AOps or higher. Below you can find the information you need to know about adding, deleting, and maintaining a list of AOps on your channel. There are also some Extra Notes on some of the miscellaneous information about this function of services.

AutoOperators

• Usage:

  /chanserv aop (channel) ADD (nick) or (mask)
  /chanserv aop (channel) DEL (index number), (nick) or (mask)
  /chanserv aop (channel) LIST (search pattern)

  NOTE: you do not need to use parentheses; the parts of the msg that are in caps are part of the aop command; without them, aop is pretty much useless.

• Breakdown:
  • Channel

    Substitute the channel name, for example #dragonrealm here.

  • ADD

    The add command allows you to add a user to your channel's list of AOps.

    • nick

      Put the nick of the user you want to have aops here; for example, theri
      

    • mask

      In the event that a user has not registered their nick with NickServ, you may add them to the list using their address, which can include wild cards. Examples of this could be: ejc6302@*.tamu.edu (for theri) or msk@final.dystopia.fi (for matti)

    • Examples:

      /chanserv aop #dragonrealm ADD ejc6302@*.tamu.edu
      /chanserv aop #my_channel ADD daluser@*.*.*.*.dynip.alter.net
      /chanserv aop #dragonrealm ADD matti

      This last command, when completed successfully, would have ChanServ reply as such:

      -ChanServ- Added AutoOp on #dragonrealm: matti - entry 42
      -ChanServ- Change will become permanent at next database sync in 5 minute(s)

      The entry number and minutes will change depending on your channel list and the time left to database sync.

      NOTE: you use EITHER the person's nick OR their address. The address is normally only used in cases when a person has not registered their nick.

  • DEL

    The del command allows you to delete a user from your channel's list of AOps.

    • nick
      Put the nick of the user whose aops you want deleted here; for example, matti

    • index number
      You may obtain an index (numbered) list of your AOps by using the LIST command. The output from a list command of AOps would look something like this:

      -ChanServ- AutoOp search results for channel #Gryphons
      -ChanServ- 5 Penka (penka@voyager.abac.com)
      -ChanServ- 4 matti (msk@final.dystopia.fi)
      -ChanServ- 3 *!*kestral@voyager.abac.com
      -ChanServ- 2 Wolenczak (leigh@dial101.phoenix.net)
      -ChanServ- 1 MoMar (momar@buffnet3.buffnet.net)
      -ChanServ- [5 match(es) found]

      If you didn't want matti to be an AOp anymore, you could just del number 4.

    • mask
      In the event that a user has not registered their nick with NickServ, you may del them from the list using their address, which can include wild cards. Using the case above, you would delete kestral from your AOps list by using her address, *!*kestral@voyager.abac.com

    • Examples:

      /chanserv aop #my_channel DEL daluser@*.*.*.*.dynip.alter.net
      /chanserv aop #gryphons DEL matti
      /chanserv aop #gryphons DEL *!*kestral@voyager.abac.com
      /chanserv aop #gryphons DEL 4

      This last command, when completed successfully, would have ChanServ reply as such:

      -ChanServ- Removed AutoOp on #Gryphons: matti
      -ChanServ- Change will become permanent at next database sync in 2 minute(s)

      The nick and minutes will change depending on who is entry number 2 on your aop list and the time left to database sync.

      NOTE: you use EITHER the person's nick, the index number, OR their address. The address is normally only used in cases when a person has not registered their nick.

  • LIST

    The list comand allows you to show a list of all the aops currently entered on your channel.

    • Search Pattern

      If you type the list command by itself, it will come up with an index of your aops. If you add part of an address or nick you want ChanServ to search for, it will come up will all possible matches. For example, you could use matti, or *dystopia.fi*
      NOTE: the * * surrounding dystopia.fi are necessary to do that type of search.

    • Examples:

      /chanserv aop #cool_room list *abac.com*
      /chanserv aop #gryphons list matti
      /chanserv aop #gryphons list

      This last command, when completed successfully, would have ChanServ reply as such:

      -ChanServ- AutoOp search results for channel #Gryphons
      -ChanServ- 5 Penka (penka@voyager.abac.com)
      -ChanServ- 4 matti (msk@final.dystopia.fi)
      -ChanServ- 3 *!*kestral@voyager.abac.com
      -ChanServ- 2 Wolenczak (leigh@dial101.phoenix.net)
      -ChanServ- 1 MoMar (momar@buffnet3.buffnet.net)
      -ChanServ- [5 match(es) found]

• Extra Notes:
  • Nicks versus Masks
    Generally, it is better to add aops to your channel list by nick.
    • The aop has more control over how they get opped on the channel - by using an access list with NickServ, they can gain ops on the channel at a number of different addresses.

    • When adding aops by nick, the founder can avoid clutter by register a user under their most common name. They only need to use that name to gain ops on the channel, thus the founder doesn't have to add every single address the aop might IRC from - the aop keeps their own address list with NickServ.

    • The founder, with consultation with an aop, can set up their aop list for their channel by adding the aop by nick only. The aop then empties the access list for their nick, so that no one can use their nick without the password. This is only necessary in cases where ip spoofing has been suspected, or if the founder wants extremely strict security for their channel.