DALnet #Sibu Channel - Guides on Services Command

                              ChanServ

                       ACCESS

Command syntax:

     /chanserv  ACCESS  #channel   nick

 

Command description

 

This command will allow user with at least AOp status to 

view the level of ACCESS of a nick to the channel. The nick

entry is optional and if no nick is entered, then the status

will refer to the user's own nick.

 

ChanServ will report seven different level of ACCESS of a 

nick to the channel:

 

-1 = User is AKICKED from the channel

 0 = User has no ACCESS in the channel (just a regular user)

 1 = User has AOp status in the channel

 2 = User has SOp status in the channel

 3 = User is on the Founder-Nick ACCESS list, but has not

       identified to the Founder-Nick nor the channel

 4 = User has Founder status in the channel because the 

       user has identified to the Founder-Nick

 5 = User has Founder status in the channel because the

       user has identified to the channel

 

 

Command example

 

If you wish to view your own level of ACCESS in #Sibuop

channel, then you would type:

 

     /chanserv  ACCESS  #Sibuop 

 

If you wish to view the status of the nick <boleh> in 

#Sibuop channel, you will type:

 

     /chanserv  ACCESS  #Sibuop  <boleh>

 

Special requirement

The user of this command must first identify to  his/her

nick and must at least have AOp level of ACCESS in the

#channel. 

 

The targeted nick must be in use at the time when this

command is used.

 

 

Comments

 

It is an useful command for channel Operator to quickly

check the status level of an existing channel Operator

and if the Operator's nick is not the regular nick, use

/chanserv WHY #channel opNick to find out the reason

for that opNick being given Operator status.

 

For e.g. if <Edify> has no ACCESS in #Sibuop channel

           but is at @Op at the moment, to find out the

           reason how <Edify> become @op, use the

           WHY command and ChanServ will report the

           reason such as... <Edify> has SOp ACCESS in

           #Sibuop because <Edify> has identified to

           <Banker>'s nick.

 

 

 

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