ChanServ – Part 3
The AKICK System
Some use the auto-kick system to kick users for certain ‘rule’ breaking like flooding the channel and repeating themselves. Well, there is another system if you just want to keep a user out. However, be warned that this could cause a kick flood to happen if your not careful. We’ll first start off with the AKICK list.
/cs akick #channel list
This will give you a list of the current host masks in the AKICK system. However, if your just seeing this for the first time, chances are you have none. ^_~ To add a user, use this:
/cs akick #channel ADD hostmask [reason]
The “reason” is actually optional and not required. But, if you don’t want to get questions, it’s best to have a reason there so people will know why that user is not welcomed. The hostmask is the information after the @ symbol if you /whois someone. Pay careful attention on how you ban people, as it could prevent others from joining the channel.
If you seriously don’t want a user on your channel, you can stick an AKICK to permanently ban the user from the channel, if the hostmask match.
/cs akick #channel stick hostmask
If you stick a hostmask, it will be banned, regardless if you try to take it off. ChanServ will put the ban back so that other operators can’t remove the ban for whatever reason. If you wish to unstick the ban, then here:
/cs akick #channel unstick hostmask
This is the opposite to STICK, in that you can now remove the ban without ChanServ putting it back automatically.
If you wish to delete hostmasks off of the AKICK list, then use this command:
/cs akick #channel del hostmask
This will simply delete the hostmask off of the AKICK list.
If you wish to get a more detailed, verbose information about the AKICK list:
/cs akick #channel view [mask]
This will give you more information about the list. Optionally, if you wish to get information on a specific ban, then you can also add the hostmask.
You can also have ChanServ enforce the AKICK list to kick anyone that matches the hostmask. Be extra careful with this command.
/cs akick #channel enforce
Again, be careful as you could ban users you don’t want to ban.
Like many other lists in ChanServ, the AKICK can also be wiped clean with a single command:
/cs akick #channel clear
This will clear out the list completely and start off with a clean slate.
Clearing Certain Settings
In ChanServ, you can clear out certain information from the channel, such as removing voiced status, half-operator status, etc… We’ll first show you how to clear out the channel modes.
/cs clear #channel modes
This will clear out the channel modes from the channel, thus leaving you with a mode-less channel. However, if you use the MLOCK function, then the modes will automatically be reset to what was set for MLOCK.
/cs clear #channel bans
This command will clear out the bans that are currently set. One thing to note, if you are using the X-Chat client, then you can also hit the “B” button at the top right of the window to get a ban list and clear them all from there. Either method works.
/cs clear #channel ops
This removes all +o status from users that have them.
/cs clear #channel hops
This will remove +h from all users that currently have it.
/cs clear #channel voices
This will remove +v from all users that have it set on them.
/cs clear #channel users
This will essentially kick all current users from the channel except for the BotServ bot if you have one assigned.
Owner and Protect Modes
Owner (+q) and Protect (+a) are additional modes provided by us to give better protection, or other statuses to be shown to other users. As these are additional modes, you will not gain any sort of power besides a new symbol or color, depending on the client your using. Channel operator status must also be given if you wish to be a channel operator along with your protection.
To note, +q status is the only mode that can only be set by services. This is more of a security measure than anything. If you wish to give others owner status, the only thing that can be suggested is to give them the channel password to identify themselves with the channel. However, this is not recommended to do. Channel owner status has no real power over others besides the fact that that person owns the channel as he/she has registered the channel itself to get this status. Protection status just gives protection to certain auto-kick systems and also has no real power.
If you are the channel founder, you should already have +q status. However, if for some reason you don’t, it’s easy to get it back. Just use the following command to do so:
/cs owner [#channel]
If you specify no channel, you will get Owner status in all channels if you have founder access to the channel. However, if you do specify a channel, then you will only get it for that one channel.
/cs protect [#channel [nick]]
If you leave the #channel and nickname information, then this command will just add protection status to yourself. This command is limited to SOPs (using the xOP system), founder, and those with level 10 access or higher if the founder turned off the xOP system. You can specify the channel and nickname information to give protection status to those who probably earned it.
If you wish to remove the founder or protect status, then you can use either one of the commands here:
/cs deowner [#channel]
/cs deprotect [#channel [nick]]
/mode #channel -qa nick1 nick2
This will remove the status on either yourself, or selected nicknames.
Other Useful Commands
If you have a channel that’s invite-only, and you end up getting locked out of the channel, you can tell ChanServ to invite you back in with this command:
/cs invite #channel
This command is only limited to either AOPs or people with level 5 access and higher.
I do believe that concludes the last tutorial for ChanServ. ^_^