TWiki > Openflows > OpenFlows > ProjectFlows > IrcProject > IrcServices > IrcChannelManagement	TWiki webs: Know| Main | Openflows | Plugins | Rocketktp | Sandbox | TWiki |
	Openflows . { Changes | Index | TreeIndex | Search | Create/GoTo }

Similar to IrcNicknameManagement, all commands here are assumed to be preceeded with /msg Chanserv (or whatever command in your irc client sends a private msg to another 'user'). Remember to set your flood protection to low or off (/set flood in BitchX? for eg. will show all flood related settings) as when asking the services for help, they can dump up to 30 lines of text.

Channel names must be preceeded with # in commands to the Chanserv.

Useful commands:

• Registering a channel -- Join the channel to create it, and you will automatically get ops in the chan. With ops you can use register #(channel) (password) with the Chanserv. drop #(channel) (password) reverses this. Like with Nickserv and nicks, registering a channel identify 's you automatically with the chanserv as channel founder. drop will drop all registration of a channel.

• Identifying with the Chanserv -- When you rejoin an existing channel, to use any admin commands via chanserv, you must provide the channel password used to register it.

• Set permanent channel modes -- Channel modes (including +k key to set a channel key) can be permanently set or blocked from being set with the set #(chan) modes (modes).

• Setting and locking topics -- Topic can be force changed with set #(chan) (topic) and locked in place (modifyable only via set topic) with set #(chan) topiclock.

• Setting access levels of users -- Users can be given various different priviledge levels on channels with the ChanServ? (see below for level abilities settings). This is set with access add #(chan) (nick) (level) The (nick) statement can actually be a hostmask as well (ie bob*!bob@foo.com) but that provides lower security as the users are not required to register to be given powers in channel. access del #(chan) (nick|pattern|index #) can be used to remove users by nick, matching a pattern, or the #Nth user in the numbered access #(chan) list output. Channel founder's access levels cannot be changed, they are locked at 50. (However, channel founder (and password) can be changed via Chanserv commands accessible to the founder, users with sufficient access levels or IrcServices admins/superusers).

• Configuring access levels' powers -- Channel's access levels are a collection of abilities given to users at that level. Any higher level includes all abilities of the lower levels (unfortuntely -- a bitmask would be more useful, though the nature of the abilities is more or less hierarchical anyway). level #(chan) list will list the current level settings, and level #(chan) (type|index) (newlevel) will change an ability's access level (by ability type or by ability's position in the list index) to the newlevel given. level #(chan) reset will reset all abilities' levels to IrcServices server config defaults. Abilities include autodeop, autovoice, autoop on joining channel, use of op, voice, ban, unban, akick, access and set Chanserv commands.

• Restricting ops -- Channel operator (+o) status can be reserved to only those users with auto-op access level or higher in the channel access list (see set access above) via the command set #(chan) secureops on. (Off removes, null shows current setting.)

• Restricting access

• • The lowest level of restriction is by maintaining the AKICK list to autokick matching users. Use akick add [time] (hostmask) [reason] to add an entry to the autokick list that will kick users matching the hostmast, that optionally expires in [time] minutes, and gives the user an optional [reason] for it. akick #(chan) del to delete entries, and list to list current entries. Note: if an akick matches users currently on the channel, they will be kickbanned immediately.

• • Access to the channel can be restricted to those who have registered and identify 'd with their nicks via Nickserv (see IrcNicknameManagement) with the command set #(chan) secure on (off to cancel, null to show current setting.)

• • Channel access can be completely restricted to those users with auto-op status or higher with the set #(chan) restricted on (off to cancel, null to show setting.)

• Setting founder and successor for a channel -- The channel will cease to be registered if the founder's nick expires, so as not to have channels forever blocked from other users that are actually live on the server. (Of course, preferred nicks can be set to not expire, and their channels wont expire.) Use set #(chan) founder (nick) to change the founder of a channel to a new nick. Use set #(chan) successor (nick) to set the founder's successor, should the founder's nick expire. The founder password of the channel (for use with identify above) can be set with set #(chan) password.

• Setting entry messages -- An entry message that is sent to all users joining the channel can be set with set #(chan) entrymsg (msg). Remove with (msg) set to a single dash "-".

These commands will help regain control of an occupied channel. Some of these commands can be used by services Operators/Admins/Superusers (please see IrcServerManagement) despite not having formed or having any access in the channel.

• Gaining access to or powers on a channel -- The commands invite, voice, op and unban will perform those operations for you via the Chanserv, provided you have sufficient access via the Chanserv access list for that channel, or are an IrcServices admin or superuser. (There are a few different semantics required for each command, please see Chanserv help for these commands.)

• Clearing channel modes -- The command clear #(chan) (modes) will clear those modes from all users or set against users (eg. bans) in the channel. The modes available are ops, voices, bans which clear all of those modes for or against users, or users which will kick all users from the channel. The mode all will do all of the above except users. (Note: all users are cleared from the channel, even channel founders, those with very high access levels and opers/admins/superusers.)

• Resetting channels to defaults -- The cycle #(chan) command will reset the channel to default modes (also clears keys), and will leave only those users with sufficient access levels for AUTOOP with ops in the channel. Does not remove channel bans.

Chanserv provides these commands restricted to IrcServices admins/superusers:

• forbid This prevents anyone from ever registering this channel. Users joining will be autokickbanned and the channel set +i (even services admins/superusers). Users in the channel will be autokickbanned, even channel founders and admins/superusers. No Chanserv commands will work for this channel except drop and unforbid. drop will erase the channel and the forbid action, whereas unforbid will restore the channel as was before the forbid.

• forget *CAUTION* This command causes the Chanserv to forget the registration of the channel forever. There is no way to undo this, except to stop the services daemon, manually edit the services database files, and restart services. Users will not be kicked or anything else, there will just be no services for this channel.

• status #(chan) (nick) Will show the status of a user's access level in a channel's access list.

• setpass This will change the founder password for the channel.

• noexpire This will set the channel to never expire (default expire is a server config setting, currently 8 weeks). clearnoexp will clear this flag.

• resetlevels Will reset access level definitions to services defaults.

-- KenChase - 17 Oct 2004