RisingNet.net : Web Hosting - Shell Account - VPS Hosting

Eggdrop Command Reference (Channels)

[ Back to Reference Index ]

The channels module provides the means for storing channel information about users. It does not provide the means for sitting on a channel (this is in the irc module).

DCC Commands
+ban
-ban
bans
+chan
-chan
chaninfo

chanload
chansave
chanset
chinfo
+chrec
-chrec

+exempt
-exempt
exempts
info
+invite
-invite

invites
stick
unstick

+ban	o\|o
`+ban <hostmask> [channel] [%<XdXhXm>] [comment]`
Adds a ban to the list of permanent bans stored on the bot, with optional comment and bantime. This ban will be in effect for every channel on the bot if no channel is supplied, and is stored with your nickname and comment. Prefixing a comment with @ will make it only visible within the bot. Bantime has to be expressed in days, hours and/or minutes.
Examples	`.+ban !loser@.isp.net #CowChat get out .+ban yousuck!@ %1h30m change your nick please`

-ban	o\|o
`-ban <hostmask OR number>`
Removes the ban from the list of permanent bans stored on the bot. You may reference the ban by the number shown in .bans.
Examples	`.-ban !loser@.isp.net .-ban 12`

bans	o\|o
`bans [[channel] wildcard] bans all`
Shows you a list of the global bans active on the current channel, and the list of channel-specific bans, as well as any bans that are on the channel but weren't placed by the bot. Here's a sample entry: [ 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.
Examples	`.bans #NiceChan .bans #CowChat loser`

+chan	n\|-
`+chan <channel>`
Lets you add another channel to the bot. This causes the bot to join the channel, and you can make changes to it's settings. The channel is not permanent unless "chanfile" has been defined in the config file, and is saved every time the userfile is saved, or by using .chansave.
Examples	`.+chan #TuesdayTrivia`

-chan	n\|-
`-chan <channel>`
This removes ALL information about a channel from the bot. It's not made permanent unless a channel-file has been defined in the user file, in which case it's saved each time the userfile is, or by using .chansave. 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.
Examples	`.-chan #TuesdayTrivia`

chaninfo

m|m

`chaninfo <channel>`

This lists all the settings for the bot on the given channel. It shows any of the following:

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.

   stopnethack-mode de-op anyone who enters the channel with server ops
      0 turn off
      1 isoptest (allow serverop if registered op)
      2 wasoptest (allow serverop if op before split)
      3 allow serverop if isop or wasop
      4 allow serverop if isop and wasop
      5 if channel -bitch: see stopnethack-mode 3
         if channel +bitch: see stopnethack-mode 1
      6 if channel -bitch: see stopnethack-mode 2
         if channel +bitch: see stopnethack-mode 4

   revenge-mode defines how the bot should punish bad users when revenging
      0 for deop
      1 for deop and +d
      2 for deop, +d and kick
      3 for deop, chattr +d, kick and ban

   aop-delay autoop or autovoice delaytime
      0:0 no delay
      x:x x sec delaytime
      x:y random delay, minimum x sec, maximum y sec

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

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

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

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

nodesynch allow non-ops to perform channel modes? (stops bot from fighting with services such as ChanServ)

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

chanload	n\|n
`chanload`
Reloads the channel settings from the file defined by the "chanfile" setting. This allows you to return to a previous setting if you've really messed things up.

chansave	n\|n
`chansave`
Saves the channel settings to the file defined by the "chanfile" setting. This file is reloaded during rehash and restarting the bot. This allows you to change channel modes without having to edit the config file every time.

chanset	n\|n
`chanset <channel> <settings>`
Allows you to change the channel settings for a channel. See .chaninfo for the settings. These are used until the next rehash/chanload/restart, and are saved whenever the channel settings are saved.
Examples	`.chanset #GrumpyOldMen +dynamicbans -revenge .chanset #losers flood-ctcp 6:30 .chanset #Horses chanmode +snt-k`

chinfo	m\|m
`chinfo <user> [channel] [info-line]`
Sets the information line for a user. This line is shown via .who and .whois, and if you have set greet on, it is shown when a user joins the channel. If the info line begins with a '@', then it is "locked", and that user may no longer change it. If the channel name is omitted, the default info line is changed.
`chinfo <user> [channel] none`
Erases a user's info line.
Examples	`.chinfo \|Rosie\| I'll have all the answers for you in about 10 minutes.`

+chrec	m\|m
`+chrec <handle> [channel]`
Adds an empty channel record for the user so that channel lastons and info lines can be saved. No flags are associated with the channel.
Examples	`.+chrec Arthur #GrumpyOldMen`

-chrec	m\|m
`-chrec <handle> [channel]`
Deletes a channel record for the user, including channel lastons, info lines, and flags.
Examples	`.-chrec dweeb #losers`

+exempt	o\|o
`+exempt <hostmask> [channel] [%<XdXhXm>] [comment]`
Adds a ban exempt to the list of permanent exempts stored on the bot, with optional comment and exempttime. This exempt will be in effect for every channel on the bot if no channel is supplied, and is stored with your nickname and comment. Prefixing a comment with @ will make it only visible within the bot. Exempttime has to be expressed in days, hours and/or minutes.
Examples	`.+exempt !niceguy@ lets niceguy in .+exempt !mouse@ #CowChat`

-exempt	o\|o
`-exempt <hostmask OR number>`
Removes the exemption from the list of permanent exempts stored on the bot. You may reference the exempt by the number shown in .exempts.
Examples	`.-exempt 5 .-exempt !niceguy@`

exempts	o\|o
`exempts [[channel] wildcard] exempts all`
This command is almost exactly the same as .bans, but applies to the exempts list. See .bans help for more info.
Examples	`.exempts #CowChat .exempts niceguy`

info	-\|-
`info [channel] [info-line]`
Sets your info line. This is shown via .who and .whois, and possibly when you join the channel. If you omit the info line, it will just show you what your current info line is. If you omit the channel name, your default info line will be displayed/changed. Your default info line is the info line shown for channels where you have no specific info line set. Note that by beginning a user's info line with '@' it will be locked and they will not be able to change it.
`info [channel] none`
Removes your info line.
Examples	`.info #GrumpyOldMen I'm too sexy for this channel...`

+invite	o\|o
`+invite <hostmask> [channel] [%<XdXhXm>] [comment]`
Adds an invite to the list of permanent invites stored on the bot, with optional comment and invitetime. This invite will be in effect for every channel on the bot if no channel is supplied, and is stored with your nickname and comment. Prefixing a comment with @ will make it only visible within the bot. invitetime has to be expressed in days, hours and/or minutes.
Examples	`.+invite !@*blah.net #nicechan CoolDude's invite`

-invite	o\|o
`-invite <hostmask OR number>`
Removes the invite from the list of permanent invites stored on the bot. You may reference the invite by the number shown in .invites.
Examples	`.-invite 12 .-invite !@*blah.net`

invites	o\|o
`invites [[channel] wildcard] invites all`
This command is almost exactly the same as .bans, but applies to the exempts list. See .bans help for more info.
Examples	`.invites #chess pawn`

stick	o\|o
`stick [ban/exempt/invite] <hostmask OR number> [channel]`
Makes a ban/exempt/invite "sticky", meaning the bot will always try to keep it active on the channel, even if the channel is using dynamic bans.
Examples	`.stick ban !@*.lamers.net .stick ban 13`

unstick	o\|o
`unstick [ban/exempt/invite] <hostmask OR number> [channel]`
Makes a "sticky" ban/exempt/invite normal again.
Examples	`.unstick invite !@*.chickens.net #BarnHouse .unstick exempt 4`

Reverse.Net: Great Unix Shell Accounts

Eggdrop Command Reference (Channels)

[ Back to Reference Index ]

+ban <hostmask> [channel] [%<XdXhXm>] [comment]

-ban <hostmask OR number>

bans [[channel] wildcard] bans all

+chan <channel>

-chan <channel>

chaninfo <channel>

chanload

chansave

chanset <channel> <settings>

chinfo <user> [channel] [info-line]

chinfo <user> [channel] none

+chrec <handle> [channel]

-chrec <handle> [channel]

+exempt <hostmask> [channel] [%<XdXhXm>] [comment]

-exempt <hostmask OR number>

exempts [[channel] wildcard] exempts all

info [channel] [info-line]

info [channel] none

+invite <hostmask> [channel] [%<XdXhXm>] [comment]

-invite <hostmask OR number>

invites [[channel] wildcard] invites all

stick [ban/exempt/invite] <hostmask OR number> [channel]

unstick [ban/exempt/invite] <hostmask OR number> [channel]

`+ban <hostmask> [channel] [%<XdXhXm>] [comment]`

`-ban <hostmask OR number>`

`bans [[channel] wildcard] bans all`

`+chan <channel>`

`-chan <channel>`

`chaninfo <channel>`

`chanload`

`chansave`

`chanset <channel> <settings>`

`chinfo <user> [channel] [info-line]`

`chinfo <user> [channel] none`

`+chrec <handle> [channel]`

`-chrec <handle> [channel]`

`+exempt <hostmask> [channel] [%<XdXhXm>] [comment]`

`-exempt <hostmask OR number>`

`exempts [[channel] wildcard] exempts all`

`info [channel] [info-line]`

`info [channel] none`

`+invite <hostmask> [channel] [%<XdXhXm>] [comment]`

`-invite <hostmask OR number>`

`invites [[channel] wildcard] invites all`

`stick [ban/exempt/invite] <hostmask OR number> [channel]`

`unstick [ban/exempt/invite] <hostmask OR number> [channel]`