Automatic Channel Operator (AOP) Handbook

(This page will be updated as more questions arise)

Op Security

There are three ways for a person to get opped in our rooms:

1. • • 1. The person identifies to CHANSERV that they "own" their nick through the IDENTIFY command, and so CHANSERV gives that person ops. The nickname must be exactly as it was when the founders or SOP’s added them.
       2. Another op sees the person come in, recognizes them, and gives them operator status so that the incoming person doesn’t have to wait for CHANSERV. Some effort should be given to ensure a person is really your fellow op first, such as performing a /whois nickname and seeing if you recognize their information!
       3. My script "sees" you come in, and ops you. This is exactly like number two above, except the script does the /whois, and then ops the person if the address information and ID is correct. If you go changing your information in the mIRC settings tabs after I have added you to my list, it won’t recognize you. Rather than putting your self in that position, I recommend you leave them alone…

Family members who inadvertently get ops because of the same ISP address:

1. • • 1. They can voluntarily de-op themselves every time.
       2. I can remove the op from my script, so that only CHANSERV will op the person, and only with the exact nick and IDENTIFY password.
       3. I can remove the op and family all together (last resort).
       4. They can NOT remain opped without being selected and meeting the requirements herein.

Op Help

For CHANSERV Opping:

Initially…

1. • • • • 1. Registered Nickname
           2. Set Kill On

• • Each time you log on…

1. • • • • 1. Select your registered nickname /nick yournicknamehere.
           2. IDENTIFY to NICKSERV that YOU are really YOU /MSG NICKSERV IDENTIFY yourpasswordhere.
           3. Then, and ONLY then, enter the channel. If you forget and enter the channel before you IDENTIFY to NICKSERV, simply leave and then reenter. If CHANSERV is up, it will then recognize your NICKSERV IDENTIFY, and op you. (Basically, CHANSERV usually looks once when you first come in, to see if you should be opped.)

For Founder’s Script Opping:

• • The script will op you if it sees a correct address and id info. If you change Internet Service Providers (ISP’s), OR you change the settings in your mIRC tabs, you will eliminate my script’s ability to op you. This is not a failing in my script, and you should leave the mIRC ID settings alone (all the stuff that shows up when you do a /whois on yourself.) If you aren’t getting opped anymore, perhaps you should put them back like they were before.

     

     

Here are some common situations when you have a registered nick, and SET KILL ON is enabled (and how to fix them!)

1. 1. You join a server, and use your registered nick. Your status window gets a message that you have selected someone else’s registered nick, and you have 60 seconds to change it.
      
      What you do: type /MSG NICKSERV IDENTIFY yourpasswordhere
      

   2. You join a server, and somebody else is using YOUR registered nick (should not normally happen if you have SET KILL ON enabled.)
      
      What you do: type /MSG NICKSERV ghost yournickname yourpasswordhere
      
      This is also effective if you were on IRC with your nick, and got dropped! Sometimes when you come back on, the server still thinks you never left, and you SEE YOURSELF! This ghost command will kill the other YOU so you can use your own nickname. Just type /nick yournickname now.
      
   3. You were trying to IDENTIFY to CHANSERV that YOU were YOU, but for some reason, CHANSERV messed up and didn’t recognize it. Now the system says your nickname is held by NICKSERV Security or something like that!
      
      What you do: type /MSG NICKSERV release yournickname yourpasswordhere
      
      Now you can get your nickname back. Just type /nick yournickname now.