NOTE: This topic and OpGuard are not entirely compatible. If OpGuard is ON, and LeaveOps are on, LeaveOps gets cancelled out - unless the first person to /join your channel is on your AOp list or above, they will not get ops on your channel regardless of LeaveOps being on. The information provided below will tell you how to use this command and give you pointers for some problems you may come across.

Set LeaveOps

• Usage:

  /chanserv set (channel) leaveops (On|Off)

  NOTE: you do not need to use parentheses.

• Breakdown:
  • Channel
    Substitute the name of the channel you want to change leaveops on here. For example, #hotsoup.
  • On|Off
    The default setting for this command is Off. It will stay off unless you turn it On.

• Examples:

  /chanserv set #hotsoup leaveops on

  ChanServ would respond:

  -ChanServ- Leave ops option on channel #hotsoup is now ON
  -ChanServ- Change will become permanent at next database sync in 19 minute(s)

  Obviously, the name of the channel, the on/off, and the number of minutes left to database sync will change depending on what you input.

• Extra Notes
  • If after typing the example command, ChanServ tells you:

    -ChanServ- Password authentication required for that command:
    -ChanServ- Retry after typing /msg ChanServ identify #hotsoup <password>

    It means that you need to identify yourself, letting ChanServ know that you have access to that command. Only the founder of the channel can change these settings.

  • If after typing the example command, ChanServ tells you:

    -ChanServ- Access denied to that function for channel #hotsoup Several things are possible:

    • You may have typed the name of the channel wrong. Especially if your channel is very similar to another; perhaps yours is #hotsoup! and someone else's is #hotsoup, perhaps you left off the !. Check to make sure you have the channel name inputted correctly.

    • You may not own that channel. Registrations DO expire, sometimes passwords are guessed, perhaps you thought you registered the channel correctly when you actually didn't, and then someone else registered it; there are a multitude of reasons why this might be so. You can use the info command to see who DOES own the channel. If for some reason you feel that you should own a channel and you don't, you can /join #dragonrealm and ask for assistance.

    • If you really do own the channel and know the password for it, using the identify command will allow you to gain access to the channel. If the mask you are using for your nick is not in your NickServ access list, then ChanServ will also not recognize you. (Perhaps you are IRCing from an account that you have never used before, or perhaps your address hasn't resolved and your address is numberfied, both of these things could happen, and if you don't add them to your access list, Services won't recognize you without your password.) That doesn't mean that the channel doesn't belong to you, or the nick either, for that matter, it just means that you would have to use your password to tell the Services that yes, it's really you. That's why it's always very important to write your passwords down. If for any reason you don't remember your password, you can find a listing of services ops by typing

      /motd services.*

      and then finding one of those people listed on-line. You can also go to #dragonrealm if you are unable to find a services op; perhaps they will be able to find one for you.