<botnick> ping <nick>

<botnick> whois [channel] <nick>

<botnick> access <nick>

<botnick> flags global

*Note: setting minutes to 0 (zero) will disable this feature

Example: Nebula chanset flood-chan 8:10

This would cause a user to be kicked if she posts more than 8 lines in a 10 second interval.

<botnick> suspend <u@h>

<botnick> unsuspend <u@h>

Search strings can be:

approval <date>

approval <network>

approval <channel>

approval <nick>

approval <status type, either approved, reject, installed, removed>

<botnick> op [channel] <nick 1, 2, 3>

<botnick> deop [channel] <nick 1, 2, 3>

<botnick> ban [channel] <user@ host> <reason>

**Using Perm will ban this person permanently from the channel

** You can only add someone lower than your access i.e. ChanOps can only add Chanvoice users

INSTALLED <network> <channel> <owner> <date> <botnick> <installed by>

REMOVED <Network> <channel> <date> <reason>

REJECT <network> <channel> <owner> <date> <reason>

APPROVED <network> <channel> <owner> <date>

DCC Commands

These commands are given within a DCC chat session with the bot, and always begin with a dot followed by the command. The most powerful of the bot's commands are done this way. Any user who has access to the bot can also enter into DCC chat with it, using the same method as you would for any other IRC user. There are only two differences:

• You must have logged in with the bot before attempting to DCC it
• When you enter the DCC, you will be asked for your password with the bot
• All DCC commands begins with a dot (example: .help)
• Items inside [ ]'s are optional.

Command/Syntax

Command bindings:

TYPE FLGS COMMAND HITS BINDING (TCL)

msg -|- rose 0 msg_rose

msg -|- go 0 msg_go

DCC m|- bind 0 cmd_bind

pub -|- gross 0 pub_gross

The fields should be self-explanatory, except for HITS, which records the number of times that binding has been called. If not, go read the file 'TCL-commands.doc' for help on the TCL bind command. Note that the built in commands are now shown. You may also specify a type of binding to show (ie, '.binds msg' ) if you want to narrow the field a bit.

msg - op *msg:op

boot <nick@bot> [reason]

Example: Bots: cEvin, ruthie, Killa1

There is no indication of which bots are directly connected to this one. Use 'who' or 'bottree' for that information.

.chattr Lamer +pf

Or to remove Denali from the global op list:

.chattr Denali –o

You may also do any combination of the above:

.chattr Fred1 -m+xj-o

You can also change the flags for Usagi on a specific channel by supplying the channel after the attributes:

.chattr Usagi -m+dk-o #blah

Changing global and channel specific flags within the same command line is now possible! Example:

.chattr Bill f|o #lamer (global +f, +o #lamer)

Whether or not you change any flags, it will show you the user's attributes afterwards. To get a list of the flags possible, do 'help whois'

NOTES: Only the owner may add or remove the 'n' (owner), 'm' (master) and 't' (botnet master) flags. It is pointless to -n a permanant owner. You must remove the permanant owner in the config file. This command can no longer be used to change bot flags, they are a seprated entity, changeable with the '.botattr' command. See also: whois

Valid levels are:

m display private msgs/ctcps to the bot

p display public talk and ctcps on the channel

k display kicks/bans/mode changes on the channel

j display joins/parts/nick changes/signoffs/etc on the channel

b display bot links/unlinks/userfile-sharing

s display server messages and connect/disconnects

w display msgs between IRCops (wallops)

Channel master only:

c display user commands (DCC and msg)

o display other bot notices [HIGHLY RECOMMENDED]

Master only:

x display file transfers and file-area commands

d display debug messages that only coders would care about

Owner only:

r display all raw text from the server (if enabled)

v display raw text SENT to the server (if enabled)

There are also 8 user-defined console modes '1' thru '8' --

The mode can also be a modifier like '+p' or '-jk' or '+mp-b'. If you omit the channel and modes, it will show your current console channel and setting.

SOCK the socket of this connection (always unique)

ADDR the IP-number of the host the connection is to, if applicable

PORT the port number being used for communication

NICK the nickname of the user or bot, if it's a user or bot

HOST sometimes, the hostname corresponding to the IP address

TYPE the type of DCC connection (see below)

The types of connection currently possible are as follows (but more are being added literally all the time):

chat user in DCC-chat command mode

pass -user entering DCC chat (being asked for her password)

send - raw data connection: user sending a file

get - raw data connection: sending a file to a user

getp - pending get (waiting for the user to acknowledge)

lstn - telnet listening port (in place of a hostname, it will show the proc to call, or mask of acceptable nicks)

t-in - incoming telnet user (being asked for his nickname)

file - user in DCC-chat file area

bot - bot linked in (aka botnet connection)

bot* - pending bot link (waiting for acknowledgement)

rela - user in relay connection to another bot

>rly - bot being relay'd to (one for each "rela")

conn - pending telnet connection (chat, relay, bot-link, etc)

new - new user via telnet, entering a handle

newp - new user via telnet, entering a password

In addition, 'chat' and 'bot' have flags listed for each connection. Capital letters mean the flag is on, and lowercase letters mean the flag is off.

For 'chat', the flags are:

C in file area, but allowed to return to party line

P party line access only (no +o access)

T telnet connection (instead of DCC chat)

E echo is on

P use is paging

For 'bot', the flags are:

P ping sent, waiting for reply

U user-file sharing is active

C this bot initiated the connection

O user-file offered, waiting for reply

S in the process of sending the user-file

G in the process of getting the user-file

W warned this bot to stop hubbing

L leafed bot (not allowed to hub)

I bot is currently in the 'linking' stage

A bot is being agressively shared with for 'chat' users, the party-line channel is also listed.

-host <nick> <hostmask>

+ignore, ignores

[ 1] *!onaji@* (perm)

Xerxes: spamming me

Started 18:38

This kind of ignore can only be stopped by using '-ignore' . Xerxes is the one who added it, and his comment is "spamming me". he added it at about 18:38 today. A temporary ignore looks like this:

[ 2] *!*@shellx.best.com (expires at 19:59)

MyBot: msg/notice flood

Started 18:59

That means the ignore was made automatically by the bot at 18:59, Because someone flooded it. It can be removed with '-ignore' , or it will expire an hour after it started (this is set in 'ignore-time' ). If you use 'ignores <wildcard>' it will list all the ignores that match against your wildcard. See also: +ignore, -ignore, set ignore-time

.match +o will match any GLOBAL +o's

.match -o&+o will match anyone without a global +o AND

with a channel +o on your console channel

.match +f|+f will match anyone with a global +f or a

channel +f on your console channel

.match |f #fred will match anyone with +f on channel #fred

.match *clemson.edu 15

To get the next 10 (if there are more than 15), you ask to list numbers

16 thru 25:

.match *clemson.edu 16 25

you first joined.

except you don't need to type your old password.

mod-path nat-ip DCC-flood-thr die-on-sighup die-on-sigterm remote-boots max-DCC max-logs enable-simul protect-telnet ident-timeout share-unlinks allow-dk-cmds botnet-nick help-path temp-path userfile motd notify-newusers admin owner

my-hostname my-ip network save-users-at switch-logfiles-atconnect-timeout reserved-port log-time require-p keep-all-logs open-telnets firewall console default-flags whois-fields hourly-updates username ignore-time uptime

version numversion telnet-flood

Use '.help set <variable>' for more info on each variable.

example: .simul dweeb .quit Makes it just as if "dweeb" typed ".quit". this command will not work unless eggdrop has simul enabled in the config file. Please use this command ethically.

status all

I am Snowbot, running eggdrop v1.1.1: 400 users (mem: 42k)

Running on BSDI 2.5

Admin: Robey <robey@wc130.residence.gatech.edu>

#turtle : 2 members, enforcing "+tn-mlk" (greet, bitch)

#gloom : 3 members, enforcing "+tn-i" (greet)

Server minnie.cc.utexas.edu:6667

Online for 4 days, 06:18 (background) CPU 14:18 cache hit 55.3%

The first line tells you the bot's name, what version of eggdrop it's running, the number of users the bot has records of, and the amount of memory being used. The second line, tell what operating system the bot is running under. The third line, if present, is the contents of your 'admin' line in the config file. Next is a line for each of the channels your bot is currently monitoring. for each channel, it lists the number of people on the channel ("members"), what channel modes it's trying to enforce, and which options are set for that channel. If your bot is sharing user files with anyone, and is currently either transmitting or receiving the userfile from a bot, it will say so here, and tell how many users have been received so far, or how many more users need to be transmitted. The next few lines show the current server, and if the helpbot is in use, its nickname and current server. To prevent server flooding, both the bot and its helpbot use queues to store replies to queries from users. If either queue has a

significant amount of information in it, this status display will show how full (%) the queue is. The next line tells you how long the bot has been online, and whether it is operating in the background or foreground. If it's in the foreground, it will tell you whether it's in terminal mode or channel display mode. (terminal mode makes the local console simulate a DCC chat connection, and channel display mode displays a '.status' and '.channel' output every few seconds.) it will also give you an estimate of the amount of CPU time (minutes and seconds) the bot has used so far, and how well the cache is working. (the cache is an attempt to keep the CPU time down, and anything over 50% or so is just great.) If you do '.status all' you will see another pageful of info, showing every internal setting as specified in the config file. It should be self-explanatory to anyone who needs to use it. See also: set, channel, debug

b remove all boldface codes

c remove all color codes

r remove all reverse video codes

u remove all underline codes

a remove all ansi codes

g remove all ctrl-g (bell) codes

The mode can also be a modifier like '+c' or '-bu' or '+ru-c'. If you omit modes, it will show your current setting.

Trace result -> Valis:Stonewall:NoBoty:SomeBoty it's a list of the bots between you and the destination bot. It should also return the time in seconds it took for the trace to occur. See also: bots, bottree

-bot

The next section is bots directly linked to this one:

-> MagField (14 Oct 01:16) eggdrop v1.0j

The arrow indicates who initiated the connection -- the right arrow means this bot connected to MagField. a left arrow means they connected to us.a '+' next to the arrow indicates that the bot is sharing userfiles with us.The connection time (14 Oct 01:16) and bot version are also shown. Nowadays it may also show the network the bot resides on. Owners will also see the bots DCC idx The final section is a list of users on this bot who are not on your channel. (this section may be omitted if everyone is on the same channel as you.) If you specify a bot's name, as in '.who valis', the who request will be sent to that bot, as long as that bot is on the botnet. Masters may

also see "(con)" after a user's entry, this shows that user's console modes (see

the '.console' help page). In the final section (users that aren't on this channel), masters will see the actual channel other users are on. also, people in the file system will be listed (as being in channel "files") --a '+' next to the nickname here means the user has access to return to the party line. See also: whom

HANDLE the handle (nickname) of the user

PASS "yes" if she has a password set, "no" if not

NOTES number of notes stored waiting for the user

FLAGS the list of flags for this user (see below)

LAST the time or date that the user was last on the channel

The valid flags under FLAGS are:

o global op (bot will op this user on any channel)

m master (user is a bot master)

n owner (user is the bot owner)

t botnet master (user is a botnet master)

x xfer (user has file-area access)

j janitor (user is a file-area master)

p party-line (user has party-line access)

c common (user record is a common-access site) [see 'help common']

u unshared (not sent to other share-bots)

b bot (user is another bot)

d global deop (user cannot get ops)

k global auto-kick (user kicked & banned automatically)

f global friend (user is not punished for doing bad things)

v global voice (user get +v automatically on +autovoice channels)

a global auto-op (always op this user on join)

h high-light flag, user sees highlighting in text output

(Plus 26 user-defined flags, A-Z)

Each channel that the user has joined will have a specific record for it, with the channel-specific flags and possibly an info line. The channel-specific flags are:

m master (user is a master for the channel)

n owner (user is an owner for the channel)

o op (bot will give this user chanop)

d deop (bot will not allow this user to become a chanop)

f friend (user is not punished for doing bad things)

k kick (user is auto-kicked)

v voice (user gets +v automatically on +autovoice channels)

q quiet (user never gets +v on +autovoice channels)

a auto-op (always op this user on join)

(plus 26 user-defined flags, A-Z)

Hostmasks for the user are displayed on the following lines. If the user entry is for a bot, there will be a line below which says "ADDRESS:" and gives the bot's telnet address. some user entries may have "EMAIL:" and "INFO:" entries too. There may be additional information displayed depending on the modules loaded.

For bots, there are additional flags seen under the BOTATTR: entry, these

include:

s share (bot is sharing user records, aggressively)

p share (bot is sharing user records, passively)

g global share (share all channels)

h hub (bot is auto-linked at highest priority)

a alternate (bot is auto-linked if no hub bots can be linked)

l leaf (bot is not allowed to link in other bots)

r reject (bot will not be allowed on the net)

i isolate (isolate the party line across a botlink)

(plus 10 user-defined flags, 0-9)

Bots may also have +s (share) settings for individual channels masters: if there is a comment, you will see it under "COMMENT:" See also: match

"*" if they are the owner of their bot, "+" if they are a master, "%" if they are a botnet master "@" if they are an op.

In other columns it will show which bot the user is on, and his or her host. If the user is away, the away message will be shown. likewise, if they are idle, the idle time will be displayed. If you are on a different channel than the party line (channel 0), then this will show the people on every bot who are on your current channel. You can also optionally give the"channel" option to list who is on a particular channel. See also: who,

bots, chat

The channels module provides the means for STORING channel information about users, it OES NOT provide the means for sitting on a channel (this is in the irc module). The following commands are provided by the channels module:

stick, unstick

bans all

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 is 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 permban list, but is not currently on the channel. a "*" marks a ban which is NOT in the permban list but IS on the channel. After 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. See also: -ban, +ban, console, set ban-time, stick, unstick

permanent unless a channel-file has been defined in the user file, in which

case it's saved each time the usefile is, or by using .chansave.

*** IMPORTANT ***

This erases ALL information about the channel, including channel settings

and channel records for users-- EVERYTHING .

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 no-idle-kick to turn this off)

need-op: TCL command to execute when the bot doesnt have ops

need-invite: TCL command to execute when the bot needs to be invited to the channel (ie 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

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

clearbans: clear all the channel bans when the bot joins the channel?

enforcebans: kicks people who match channel bans?

dynamicbans: only activate bans on channel when they are needed

userbans: allow other users to place bans on the channl

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 users info line when they join the channel

protectops: re-op a +o user who gets deopped?

dontkickops: never kick +o flag people

statuslog: log the channel status every 5 minutes

stopnethack: de-op anyone who enters the channel with server ops

revenge: take revenge on anyone who deops, kicks or bans the bot or any

valid user

secret: don't provide info about the channel over the botnet

shared: share user settings for this channel ( NOTE : this can only be set

in the config file)

autovoice: this causes the bot to also monitor channel voice settings, using

the +v/+q settings.

The following are flood settings, they are set by going .chanset flood-type number:seconds where number & seconds are integers indicating the number of times in how many seconds the flood will be triggered

flood-chan: this defines the flood level for public chatter & actions

flood-ctcp: this defines the flood level for ctcp's to the channel (include

PING & VERSION), except for ACTION's

flood-join: this 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

See also: +chan, -chan, chansave, chanload, chanset

setting. This allows you to return to a previous setting if you've really

messed things up. See also: +chan, -chan,

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.

See also: +chan, -chan

The console module provides the ability to store your console settings so that next time you use the party line they are set. You can use the '.store' command at any time to store it, or it may be configured to save automatically.

This module provides all the normal ctcp replies for the bot, including handling of DCC chat.

see also: set ctcp-version, set ctcp-userinfo

ircII 2.8 Linux 1.2.4 :ircii 2.6: almost there...

see also: set ctcp-finger, set ctcp-userinfo

This module provides support for file transfers by the bot. It's used by both the share and filesys modules.

have timeout, if no traffic occurs on the transfer for the given time, it closes.

The IRC module provides DCC commands

channel), as if the bot did it. Just like the /me command in IRC. See also: console

channel attributes. By default, it shows you the channel you are currently viewing on the console, but you can specify another channel if you wish.

The first line will look like:

Channel #hiya, 8 members, 45 users, mode +tn:

This means that the bot is sitting on channel #hiya, where 8 other irc'ers are. There are 45 people that the bot knows by hostmask, and the channel mode is +tn. If the bot isn't on the channel it is supposed to be on, it will say "Desiring channel #hiya" instead. Next is a list of the users on the channel, with each entry looking like this:

NICKNAME HANDLE JOIN IDLE USER@HOST

@kantSF kantSF 14:53 o 6m josh@random.edu

The "@kantSF" means that the user's nickname is kantSF and that he is a chanop. The second "kantSF" is the nickname that the bot knows him by. Sometimes this will differ from the nickname a person is using. The time displayed is the time the user joined the channel. The next field is the attributes:

n - bot owner o - can get ops (+o)

m - bot master or owner f - channel friend

b - another bot d - cannot get ops (+d)

The last field is the user@host he is using irc from. See also: status, whois

This module provides the means for storing & retreiving notes at a later stage.

notes read <# or ALL>

notes erase <# or ALL>

see also: note, whom

This module provides the classic 'seen' command, which returns the last time a user was seen by the bot, both DCC & msg commands are provided

This module provides the classic 'seen' command, which returns the last time a user was seen by the bot, both DCC & msg commands are provided

This module provides all that's need to get a bot on a server and sitting there, it provides server connection, raw irc, private message/notice/ctcp handling