o|o

o|o

o|o

   [ 5] *!*habib@*frys.com (perm)
   paulie: revolving check policy
   Created 15:10

The number (5) can be used to reference the ban if you wish to remove it (see .-ban). Next is the actual hostmask being banned. The "(perm)" means that the ban is "permanent", that is, it doesn't automatically expire. If there is an elapsed time showing instead, the time displayed shows how long the ban has been active. Those kind of bans expire after one hour. The second line of the ban entry is the comment ("revolving check policy" - it would seem that paulie had to stand in line for a while) and who put the ban there (paulie). The last line shows when the ban was added, and possibly the last time the ban was activated on the channel (if it's different from the creation time).

Sometimes there will be a "!" or "*" right before the number. A "!" means the ban is in the bot's permanent ban list, but is not currently on the channel. A "*" marks a ban which is NOT in the permanent ban list but IS on the channel.

If you use .bans it will show you only the bans which are currently in action on the channel. If you use .bans all it will show you every ban in memory (with 'perm-bans' on, these are identical).

If you use .bans <wildcard> it will list all the bans (active or not) that match against your wildcard. Consider it a .bans all list matched against your wildcard.

The ban list may change according to which channel you're currently viewing in the console. Different bans may be active on different channels. If you specify a channel name, that channel will be used instead of your current console channel.

n|-

n|-

This erases ALL information about the channel, including channel settings and channel records for users - EVERYTHING.

DO NOT use it to have the bot temporarily leave a channel (you can use .chanset #channel +inactive for that). This command is for abandoning a channel. The channel would have to be redefined and all user flags for that channel would have to be redone.

Even if you don't have chanfile defined, it will still erase all the channel records for users on the next userfile save.

m|m

   chanmode     which modes are enforced on the channel, both + and - modes can be enforced
   idle-kick    kick idle users (non +f's anyway) on the channel after how many minutes (use 0, or dont-idle-kick to turn this off)
   need-op      tcl command to execute when the bot doesn't have ops
   need-invite  tcl command to execute when the bot needs to be invited to the channel (i.e. channel has mode +i)
   need-key     tcl command to execute when the bot needs to find out the key to the channel
   need-unban   tcl command to execute when the bot is banned and can't get on the channel
   need-limit   tcl command to execute when the bot can't join the channel because the channel is full
   Note: Due to security concerns, only permanent owners can set the need-* modes.

The following can be set + or - (e.g. .chanset #channel -clearbans)

   clearbans      clear all the channel bans when the bot joins the channel
   enforcebans    kick people who match channel bans
   dynamicbans    only activate bans on channel when they are needed
   userbans       allow other users to place bans on the channel
   dynamicexempts only activate exempts on channel when needed
   userexempts    allow exempts to be set by users directly
   dynamicinvites only activate invites on channel when needed
   userinvites    allow invites to be made by users directly
   autoop         automatically op users when they join the channel
   bitch          only allow users with the +o flag to be ops on the channel
   greet          say a user's info line when they join the channel
   protectops     re-op +o users who get deopped
   protectfriends re-op +f users who get deopped
   dontkickops    never kick +o flag users
   wasoptest      do a wasop test for +stopnethack
   inactive       never join this channel, or leave if already joined. Useful as you can make the bot leave a channel without loosing it's settings or affecting any sharing.
   statuslog      log the channel status every 5 minutes
   stopnethack    de-op anyone who enters the channel with server ops
   cycle          cycle the channel when it becomes op-less
   revenge        take revenge on anyone who deops or kicks friends or ops
   revengebot     take revenge on anyone who deops or kicks the bot
   secret         don't provide info about the channel over the botnet
   shared         share user settings for this channel (note that this can be set online now)
   autovoice      monitor channel voice settings, using the +v/+q settings

The following are flood settings, they are set by doing .chanset <channel> flood-type number:seconds where number and seconds are integers indicating the number of times in how many seconds the flood will be triggered. Using .chanset <channel> flood-type 0:0 (or 0:1 or 1:0) will deactivate the respective flood setting.

   flood-chan   defines the flood level for public chatter & actions
   flood-ctcp   defines the flood level for CTCPs to the channel (include PING & VERSION), except for ACTIONs
   flood-join   defines the number of joins from a give user@host that constitutes a flood
   flood-kick   how many kicks in the given time are a flood
   flood-deop   deops in the given time

n|n

n|n

n|n

m|m

m|m

m|m

o|o

o|o

o|o

-|-

o|o

o|o

o|o

o|o

o|o