DALnet #Sibu Channel - Guides on Services Command

                              ChanServ

                         AOp

Command syntax:

     /chanserv  AOP  #channel  ADD  nick

     /chanserv  AOP  #channel  ADD  user@host.mask

     /chanserv  AOP  #channel  LIST

     /chanserv  AOP  #channel  DEL nick

     /chanserv  AOP  #channel  DEL #

     /chanserv  AOP  #channel  WIPE

 

Command description

 

These commands allow SOp and Founder to manage the

list  of  autoOp  (AOp)  in  the  channel.  If  an  user  is 

trustworthy  to be  given  special  privileges and certain 

level of power in the channel, then SOp or Founder may 

add the nick of user to become an AOp in the channel.

The methods of  adding AOp to  ChanServ database can 

either be plain and simple nick or using user's hostmask.

 

Similarly, SOp or Founder can delete any AOp from the 

list, hence removing the deleted user's privilege in the

channel.  Channel Founder may remove the whole AOp

list by using the WIPE command argument.

 

ALL users with AOp level of ACCESS in the channel will

be able to view the list by using LIST command 

argument.

 

 

Command examples

 

If you wish to add <Edify> as AOp to #Sibuop channel,

you will type either one of the following commands:

 

   /chanserv  AOP  #Sibuop  ADD  <Edify>

   /chanserv  AOP  #Sibuop  ADD  Hornbill@sibu.com.my

 

(Note : if <Edify> is connected with a randomly

           generated IP hostmask, then the second 

           command format (IP hostmask) cannot be used)

 

If you wish to view the AOp list of #Sibuop channel, you 

will type:

 

     /chanserv  AOP  #Sibuop  LIST

 

» The user may narrow down the listing if search pattern 

   is included after the command argument LIST.

 

   e.g. /chanserv  AOP  #Sibuop  LIST  *!*@sibu.com.my

 

   This will generate a listing of  AOps whose host.mask

   match sibu.com.my

 

If you wish to remove <Edify> from AOp list, you would

type either one of the following commands:

 

     /chanserv  AOP  #Sibuop  DEL  <Edify>

 

     /chanserv  AOP  #Sibuop  DEL  18

      (assuming that <Edify> was listed as No. 18 in the

        list generated by using command:

                     /chanserv AOP #Sibuop LIST                )

 

     /chanserv  AOP  #Sibuop  DEL  Hornbill@sibu.com.my

      (assuming <Edify>'s hostmask is shown in the LIST)

 

If you are  the  channel Founder  and  wish  to delete the

entire AOp list, you will use the following command:

 

     /chanserv  AOP  #Sibuop   WIPE

 

Special requirement

1) The  ADD  and  DEL  commands are accessible by both 

    SOPs and Founder only. 

2) The  WIPE  command  is  only  accessible  by  channel 

    Founder. 

3) The  LIST  command  is accessible by anyone who has

    ACCESS in the channel (from AOp onward).

4) A channel is limited to a total of 300 AOPs.

5) Only duly registered nick can be added as AOp.

 

 

Comments

 

An  AOp  will  be  given  @Op  status  when entering the

#channel  by ChanServ provided the user has met certain

criteria:

For example 

1) user  has  identified  to  his/her  nick  before joining the

    channel; and

2) if  the  channel  has not  activated the IDENT mode and

    if the user's IP hostmask is matching with the hostmask

    in the ACCESS list.

 

An user  who has not been  auto Oped  by ChanServ can op 

himself/herself using the following command:

 

     /chanserv  OP  #channel  userNick

 

An user with  ACCESS in the channel can  UNBAN himself or

herself if he/she is banned.

 

An user with ACCESS in the channel may send memo to ALL

rank and  file members who are in  the  ACCESS list as long

as  his/her level of ACCESS in the channel is not lower than

those required of channel Founder's setting.

 

An user with ACCESS in the channel may set or change the

channel Topic  if  his/her level of ACCESS is not lower than

those required of channel Founder's setting.

 

An user with  ACCESS in the  channel  can  use  MKICK and 

MDEOP commands to reclaim control of the channel if there

is a  channel  takeover  on  condition  that  his/her level of

ACCESS is not outranked by another existing @Op.

 

An  user  with  ACCESS  in the channel can INVITE himself/

herself into the channel if the channel is set to Invite-only.

 

An AOP can view the channel lists of AOps, SOps, and also

AKICKs.

 

 

 

 

./Last Edited in Oct/2002        ©Copyright - ALL rights reserved