/chanserv sop (channel) ADD (nick) or (mask)
/chanserv sop (channel) DEL (index number), (nick) or (mask)
/chanserv sop (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 sop command; without them, sop is pretty much useless.

• 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 SOps.

  • nick
    Put the nick of the user you want to have sops here; for example, dalvenjah

  • 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: dalvenja@dragonlair.dal.net (for Dalvenjah) or leigh@*.phoenix.net (for Wolenczak)

  • Examples:

    /chanserv sop #dragonrealm ADD leigh@*.phoenix.net
    /chanserv sop #my_channel ADD daluser@*.*.*.*.dynip.alter.net
    /chanserv sop #dragonrealm ADD dalvenjah

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

    -ChanServ- Added SuperOp on #dragonrealm: dalvenjah - entry 3
    -ChanServ- Change will become permanent at next database sync in 8 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 SOps.

  • nick
    Put the nick of the user whose sops you want deleted here; for example, Data

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

    -ChanServ- SuperOp search results for channel #Gryphons
    -ChanServ- 2 Data (data@voyager.abac.com)
    -ChanServ- 1 Wizzu (mihannin@lk-hp-11.hut.fi)
    -ChanServ- [2 match(es) found]

    If you didn't want Data to be an SOp anymore, you could just del number 2.

  • 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 Wizzu from your SOps list by using his address, mihannin@*.hut.fi

  • Examples:

    /chanserv sop #my_channel DEL daluser@*.*.*.*.dynip.alter.net
    /chanserv sop #gryphons DEL Data
    /chanserv sop #gryphons DEL mihannin@*.hut.fi
    /chanserv sop #gryphons DEL 2

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

    -ChanServ- Removed SuperOp on #Gryphons: Data
    -ChanServ- Change will become permanent at next database sync in 18 minute(s)

    The nick and minutes will change depending on who is entry number 2 on your sop 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 command allows you to access your current sop entries.

  • Search Pattern
    If you type the list command by itself, it will come up with an index of your sops. 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 Data, or *voyager.abac*
    NOTE: the * * surrounding voyager.abac are necessary to do that type of search.

  • Examples:

    /chanserv sop #cool_room list *abac.com*
    /chanserv sop #gryphons list Data
    /chanserv sop #gryphons list

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

    -ChanServ- SuperOp search results for channel #Gryphons
    -ChanServ- 2 Data (data@voyager.abac.com)
    -ChanServ- 1 Wizzu (mihannin@lk-hp-11.hut.fi)
    -ChanServ- [2 match(es) found]

• Nicks versus Masks
  Generally, it is better to add sops to your channel list by nick.
  • The sop 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 sops 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 sop might IRC from - the sop keeps their own address list with NickServ.

  • The founder, with consultation with an sop, can set up their sop list for their channel by adding the sop by nick only. The sop 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.