<ElfStar> [00:14] #simple# help addlog
<ElfStar> ### addlog <text>
<ElfStar> Adds your comment to the bot's logfile. Bot masters can go back later and
<ElfStar> review the log, and will see your comment (with your handle attached). This
<ElfStar> is useful for explaining confusing activity.
<ElfStar> [00:14] #simple# help console
<ElfStar> ### console [channel] [modes]
<ElfStar> Changes your console level so that you will see only the types of console
<ElfStar> messages that you want to. Your current console channel is the channel (that
<ElfStar> the bot is on) from which you can view from the party line, and which
<ElfStar> channel-specific commands (like 'say' and 'op') take affect on.
<ElfStar>
<ElfStar> Valid flags are:
<ElfStar> j joins, parts, quits, and netsplits on the channel
<ElfStar> k kicks, bans, and mode changes on the channel
<ElfStar> m private msgs, notices and ctcps to the bot
<ElfStar> p public text on the channel
<ElfStar> s server connects, disconnects, and notices
<ElfStar>
<ElfStar> Masters only:
<ElfStar> b information about bot linking and userfile sharing
<ElfStar> d misc debug information
<ElfStar> c commands
<ElfStar> o misc info, errors, etc (IMPORTANT STUFF)
<ElfStar> w wallops (make sure the bot sets +w in init-server)
<ElfStar>
<ElfStar> Owners only (these have to be enabled in the config file via "set raw-log"):
<ElfStar> h raw share traffic
<ElfStar> r raw incoming server traffic
<ElfStar> t raw botnet traffic
<ElfStar> v raw outgoing server traffic
<ElfStar>
<ElfStar> There are also 8 user-defined console modes ('1' through '8').
<ElfStar>
<ElfStar> The mode can also be a modifier like '+p' or '-jk' or '+mp-b'. If you omit
<ElfStar> the channel and modes, your current console channel and flags will be shown.
<ElfStar>
<ElfStar> ### console <user> [channel] [modes]
<ElfStar> This is used to set the console level of another user. This can even be used
<ElfStar> on users who normally would not be able to set their own console mode.
<ElfStar> [00:14] #simple# help match
<ElfStar> ### match <attr> [channel] [[start] limit]
<ElfStar> This displays all user records with the attributes requested.
<ElfStar>
<ElfStar> "attr" is of the form: <+/-><global>[&/|<channel>[&/|<bot>]]
<ElfStar>
<ElfStar> Specifying "&" as the separator will cause AND style matching.
<ElfStar>
<ElfStar> For example:
<ElfStar> .match p&o
<ElfStar>
<ElfStar> This will match all users with both the "p" global flag and the "o" channel
<ElfStar> flag on your current console channel.
<ElfStar>
<ElfStar> Specifying "|" as the separator will cause OR style matching.
<ElfStar>
<ElfStar> For example:
<ElfStar> .match p|o
<ElfStar>
<ElfStar> This will match all users with either the "p" global flag or the "o" channel
<ElfStar> flag on your current console channel. If you specify a channel, it will be
<ElfStar> used instead of the current console channel.
<ElfStar>
<ElfStar> For example:
<ElfStar> .match p|o #eggdrop
<ElfStar>
<ElfStar> This will match all users with either the "p" global flag or the "o" channel
<ElfStar> flag on the channel #eggdrop. You can also match bot flags.
<ElfStar>
<ElfStar> For example:
<ElfStar> .match o|o|h
<ElfStar>
<ElfStar> This will match all bots with either the "o" global flag, the "o" channel
<ElfStar> flag on the current console channel, or the "h" botflag. You can also limit
<ElfStar> the number of total results returned by specifying a limit at the end of the
<ElfStar> command. A starting point can also be specified.
<ElfStar>
<ElfStar> For example:
<ElfStar> .match p&o #eggdrop 16 25
<ElfStar>
<ElfStar> This would show results 16 through 25 matching any users with the "p" global
<ElfStar> flag or the "o" channel flag on #eggdrop.
<ElfStar>
<ElfStar> ### match <wildcard-string> [[start] limit]
<ElfStar> This displays all user records where the user's handle or any of the user's
<ElfStar> hostmasks match the specified wildcard string. You can also limit the number
<ElfStar> of total results returned by specifying a limit at the end of the command. A
<ElfStar> starting point can also be specified.
<ElfStar>
<ElfStar> For example:
<ElfStar> .match *.edu 16 25
<ElfStar>
<ElfStar> This would show results 16 through 25 matching any users with a hostmask
<ElfStar> that ends with ".edu".
<ElfStar> [00:14] #simple# help whois
<ElfStar> ### whois <nickname>
<ElfStar> Shows you stored information about a user record. Five headings are
<ElfStar> displayed:
<ElfStar> HANDLE - the handle (nickname) of the user
<ElfStar> PASS - "yes" if she has a password set; "no" otherwise
<ElfStar> NOTES - number of stored notes waiting for the user
<ElfStar> FLAGS - the list of flags for this user (see below)
<ElfStar> LAST - the time or date that the user was last on the channel
<ElfStar>
<ElfStar> Valid global flags:
<ElfStar> a - autoop (user is opped automatically upon joining any channel)
<ElfStar> b - bot (user is a bot)
<ElfStar> c - common (see '.help common')
<ElfStar> d - deop (user cannot gain ops in any channel)
<ElfStar> e - nethack-exempt (user is exempted from stopnethack protection)
<ElfStar> f - friend (user is not punished for flooding, etc on any channel)
<ElfStar> g - autovoice (user is voiced automatically upon joining any channel)
<ElfStar> h - highlight (use bold text in help/text files)
<ElfStar> j - janitor (user is a file-area master)
<ElfStar> k - autokick (user is kicked and banned automatically)
<ElfStar> l - halfop (user has halfop access to all of the bot's channels)
<ElfStar> m - master (user has access to almost every feature of the bot)
<ElfStar> n - owner (user has absolute control over the bot)
<ElfStar> o - op (user has op access to all of the bot's channels)
<ElfStar> p - party-line (user has access to the partyline)
<ElfStar> q - quiet (user cannot gain voice on any channel)
<ElfStar> r - dehalfop (user cannot gain halfops on any channel)
<ElfStar> t - botnet master (user has access to features related to the botnet)
<ElfStar> u - unshared (user's user record is not sent to other bots)
<ElfStar> v - voice (user gets +v automatically on +autovoice channels)
<ElfStar> w - wasop-test (needs wasop test for +stopnethack procedure)
<ElfStar> x - xfer (user has filesystem access)
<ElfStar> y - autohalfop (user is auto-halfopped upon joining any channel)
<ElfStar> z - washalfop-test (needs washalfop test for +stopnethack procedure)
<ElfStar>
<ElfStar> There are also 26 user-defined global flags (A-Z).
<ElfStar>
<ElfStar> Users can also have flags specific to a channel:
<ElfStar>
<ElfStar> a - autoop (user is opped automatically upon joining the channel)
<ElfStar> d - deop (user cannot gain ops on the channel)
<ElfStar> e - nethack-exempt (user is exempted from stopnethack protection)
<ElfStar> f - friend (user is not punished for flooding, etc)
<ElfStar> g - autovoice (user is voiced automatically upon joining the channel)
<ElfStar> k - autokick (user is kicked and banned automatically)
<ElfStar> l - halfop (user has halfop access to the channel)
<ElfStar> m - master (user is a channel master)
<ElfStar> n - owner (user is a channel owner)
<ElfStar> o - op (user has op access to the channel)
<ElfStar> q - quiet (user cannot gain voice on the channel)
<ElfStar> r - dehalfop (user cannot gain halfops on the channel)
<ElfStar> v - voice (user gets +v automatically if the channel is +autovoice)
<ElfStar> w - wasop-test (needs wasop test for +stopnethack procedure)
<ElfStar> y - autohalfop (user is auto-halfopped upon joining the channel)
<ElfStar> z - washalfop-test (needs washalfop test for +stopnethack procedure)
<ElfStar>
<ElfStar> There are also 26 user-defined channel flags (A-Z).
<ElfStar>
<ElfStar> Hostmasks for the user are displayed on the following lines. If the user is
<ElfStar> a bot, there will be a line below which says "ADDRESS:" and gives the bot's
<ElfStar> telnet address. Some user entries may have "EMAIL:" and "INFO:" entries too.
<ElfStar> There may be additional information displayed depending on the modules
<ElfStar> loaded, such as filesys and console.
<ElfStar>
<ElfStar> For bots, there are additional flags seen under the "BOTATTR:" section.
<ElfStar> Valid botflags include:
<ElfStar> s - share aggressively (SEND userfile to a passive bot)
<ElfStar> p - share passively (ACCEPT userfile from an aggressive bot)
<ElfStar> g - global share (bot is sharing all channels)
<ElfStar> h - hub (bot is autolinked at highest priority)
<ElfStar> a - alternate (bot is autolinked if no hub bots can be linked)
<ElfStar> l - leaf (bot is not allowed to link other bots onto the botnet)
<ElfStar> r - reject (bot will not be allowed to link to the botnet)
<ElfStar> i - isolate (isolate the party line across a botlink)
<ElfStar>
<ElfStar> There are also 10 user-defined bot flags (0-9). Bots may also have +s
<ElfStar> (share) settings for individual channels.
<ElfStar>
<ElfStar> Masters: if the user has a comment, you will see it under "COMMENT:".
<ElfStar>
<ElfStar> See also: match, who, whom, chattr, botattr
<ElfStar> [00:14] #simple# help +bot
<ElfStar> ### +bot <handle> [address[:bot port[/user port]]] [host]
<ElfStar> Creates a user record for a new bot with the handle given. If no hostmask
<ElfStar> is specified, the bot will try to automatically add a host from the channel.
<ElfStar> The bot's address will be used in linking. If the bot has a separate port
<ElfStar> for bots and users they should be separated with a slash (/).
<ElfStar>
<ElfStar> See also: -bot
<ElfStar> [00:14] #simple# help botattr
<ElfStar> ### botattr <handle> [flags] [channel]
<ElfStar> Lets you view and change the bot flags for a bot. For example, to set
<ElfStar> "Fred1" +share and -hub, you would do '.botattr Fred1 +s-h.'
<ElfStar>
<ElfStar> Whether or not you change any flags, it will show you the bot's flags
<ElfStar> afterwards. To get a list of the flags possible, see '.help whois'.
<ElfStar>
<ElfStar> NOTE: This command is NOT used to replace .chattr. It modifies bot flags,
<ElfStar> such as s, h, a, u, etc.
<ElfStar> NOTE: You can't use this command on bots which are directly linked to your
<ElfStar> bot at the current moment.
<ElfStar>
<ElfStar> See also: whois, chattr
<ElfStar> [00:14] #simple# help chhandle
<ElfStar> ### chhandle <oldhandle> <newhandle>
<ElfStar> Changes the handle of a user. For example, to change the handle of user
<ElfStar> 'gavroche' to 'jamie', you would use 'chhandle gavroche jamie'.
<ElfStar>
<ElfStar> See also: chpass
<ElfStar> [00:14] #simple# help chpass
<ElfStar> ### chpass <handle> [newpassword]
<ElfStar> Changes a user's password. If you do not specify the new password, the user
<ElfStar> effectively no longer has a password set. A password is needed to get ops,
<ElfStar> join the party line, etc.
<ElfStar>
<ElfStar> NOTE: In previous versions, setting a password to "nopass" would clear
<ElfStar> a user's password -- with encrypted passwords. This no longer works!
<ElfStar>
<ElfStar> See also: chhandle
<ElfStar> [00:14] #simple# help +host
<ElfStar> ### +host [handle] <hostmask>
<ElfStar> Adds a hostmask to a user's user record. Hostmasks are used to identify your
<ElfStar> handle on IRC. If a handle is not specified, the hostmask will be added to
<ElfStar> YOUR user record.
<ElfStar>
<ElfStar> See also: -host
<ElfStar> [00:14] #simple# help -bot
<ElfStar> ### -bot <bot>
<ElfStar> This is exactly the same as '.-user' (it removes a user record). It is
<ElfStar> included for convenience.
<ElfStar>
<ElfStar> See also: +bot, +user, -user
<ElfStar> [00:14] #simple# help link
<ElfStar> ### link [via-bot] <bot-to-link>
<ElfStar> Attempts to link a bot to the botnet. The local bot must have a bot record
<ElfStar> for the remote bot in order for it to be linked (see '.help +bot'). If
<ElfStar> you do not set a password on both bots, one will be automatically negotiated
<ElfStar> the first time they link. If you specify a "via-bot", a request will be sent
<ElfStar> to that bot to link to "bot-to-link".
<ElfStar>
<ElfStar> See also: unlink, +bot, -bot
<ElfStar> [00:14] #simple# help chaddr
<ElfStar> ### chaddr <bot> <address[:bot port[/user port]]>
<ElfStar> Changes the address for a bot. This is the address your bot will try to
<ElfStar> connect to when linking. If the bot has a separate port for bots and users,
<ElfStar> they should be separated by a slash (/).
<ElfStar>
<ElfStar> See also: link, +bot
<ElfStar> [00:14] #simple# help boot
<ElfStar> ### boot <handle[@bot]> [reason]
<ElfStar> Kicks a user off the party line and displays the reason, if you specify
<ElfStar> one. You can also specify a bot, and attempt to boot someone from another
<ElfStar> bot on the botnet, though it may be rejected if that bot does not allow
<ElfStar> remote boots. You can not boot a bot owner.
<ElfStar> [00:14] #simple# help unlink
<ElfStar> ### unlink <bot/*>
<ElfStar> This disconnects the specified bot from the botnet (assuming it was linked
<ElfStar> in the first place). Some bots (sharebots in particular) might not allow you
<ElfStar> to unlink them. If "*" is specified as the parameter, all bots will be
<ElfStar> unlinked.
<ElfStar>
<ElfStar> See also: link, +bot, -bot, bots, bottree
<ElfStar> [00:14] #simple# help banner
<ElfStar> ### banner <text>
<ElfStar> Displays a message to everyone currently using the bot's party line or file
<ElfStar> area. This is useful for announcing that the bot will go down, etc.
<ElfStar> [00:14] #simple# help dccstat
<ElfStar> ### dccstat
<ElfStar> Displays a table-format list of all "dcc" connections in use on the bot.
<ElfStar> Dcc stands for "Direct Client-to-client Communication", and Eggdrop expands
<ElfStar> this to cover every open socket. Any type of network connection to the bot
<ElfStar> is considered a "dcc" connection.
<ElfStar>
<ElfStar> The headings of the table are:
<ElfStar> SOCK the socket number of this connection (always unique)
<ElfStar> ADDR the ip address mask of the host the bot is connected to, if
<ElfStar> applicable
<ElfStar> PORT the port number being used for this connection
<ElfStar> NICK the handle of the user or bot, if applicable
<ElfStar> HOST the hostname corresponding to the IP address, if available
<ElfStar> TYPE the type of dcc connection (see below)
<ElfStar>
<ElfStar> The types of connections currently possible are as follows (but more are
<ElfStar> being added all the time):
<ElfStar> CHAT dcc-chat partyline user
<ElfStar> PASS user entering dcc chat (being asked for password)
<ElfStar> SEND user sending a file
<ElfStar> GET sending a file to a user
<ElfStar> GETP pending get (waiting for the user to acknowledge)
<ElfStar> LSTN telnet listening port (in place of a hostname, it will show the
<ElfStar> callback procedure name, or a mask of acceptable handles)
<ElfStar> T-IN incoming telnet user (being asked for handle)
<ElfStar> FILE user in dcc-chat file area
<ElfStar> BOT connected bot (botnet connection)
<ElfStar> BOT* pending bot link (waiting for acknowledgement)
<ElfStar> RELA user in relay connection to another bot
<ElfStar> >RLY bot being relay'd to (one for each "RELA")
<ElfStar> CONN pending telnet connection (chat, relay, bot-link, etc)
<ElfStar> NEW new user via telnet (entering a handle)
<ElfStar> NEWP new user via telnet (entering a password)
<ElfStar>
<ElfStar> In addition, 'CHAT' and 'BOT' have flags listed for each connection. Capital
<ElfStar> letters mean that the flag is on, and lowercase letters mean that the flag
<ElfStar> is off. The flags for 'CHAT' are:
<ElfStar> C in file area, but allowed to return to party line
<ElfStar> P party line access only
<ElfStar> T telnet connection (instead of dcc chat)
<ElfStar> E echo is on
<ElfStar> P paging is on
<ElfStar>
<ElfStar> The flags for 'BOT' are:
<ElfStar> P ping sent, waiting for reply
<ElfStar> U user-file sharing is active
<ElfStar> C local bot initiated the connection
<ElfStar> O user-file offered, waiting for reply
<ElfStar> S in the process of sending the user-file
<ElfStar> G in the process of getting the user-file
<ElfStar> W warned this bot to stop hubbing
<ElfStar> L leaf-only bot (not allowed to be a hub)
<ElfStar> I bot is currently in the 'linking' stage
<ElfStar> A bot is being aggressively shared with
<ElfStar>
<ElfStar> For 'CHAT' users, the party-line channel is also listed.
<ElfStar> [00:14] #simple# help chattr
<ElfStar> ### chattr <handle> [flags] [channel]
<ElfStar> This lets you view and change the flags for a user.
<ElfStar>
<ElfStar> For example, to give Lamer the p and f flags:
<ElfStar> .chattr Lamer +pf
<ElfStar>
<ElfStar> To remove Denali from the global op list:
<ElfStar> .chattr Denali -o
<ElfStar>
<ElfStar> You may also do any combination of the above:
<ElfStar> .chattr Fred1 -m+xj-o
<ElfStar>
<ElfStar> You can also change the flags for Usagi on a specific channel by supplying
<ElfStar> the channel after the attributes:
<ElfStar> .chattr Usagi -m+dk-o #blah
<ElfStar>
<ElfStar> Changing global and channel specific flags within the same command line is
<ElfStar> also possible (global +f, +o #lamer):
<ElfStar> .chattr Bill f|o #lamer
<ElfStar>
<ElfStar> Whether or not you change any flags, it will show you the user's attributes
<ElfStar> afterwards. To get a list of all possible flags, see '.help whois'.
<ElfStar>
<ElfStar> NOTES: Only the owner may add or remove the 'n' (owner), 'm' (master) or
<ElfStar> 't' (botnet master) flags. It is pointless to -n a permanent owner.
<ElfStar> You must remove the permanent owner in the config file.
<ElfStar>
<ElfStar> See also: whois, botattr
<ElfStar> [00:14] #simple# help save
<ElfStar> ### save
<ElfStar> This makes the bot write its entire userfile to disk. This is useful if you
<ElfStar> think the bot is about to crash or something, since the user file is only
<ElfStar> written to disk about once an hour.
<ElfStar>
<ElfStar> See also: reload, rehash, backup
<ElfStar> [00:14] #simple# help backup
<ElfStar> ### backup
<ElfStar> This makes the bot write a backup of its entire user list to the disk. If
<ElfStar> the channels module is loaded, this will also write a backup of the channels
<ElfStar> file. This is useful if you feel the need to backup the userfile and channel
<ElfStar> settings.
<ElfStar>
<ElfStar> See also: reload, rehash, save
<ElfStar> [00:14] #simple# help reload
<ElfStar> ### reload
<ElfStar> Reloads the bot's user file, discarding any changes made since the last
<ElfStar> '.save' command or hourly user file save. Sharebots should probably
<ElfStar> never do this.
<ElfStar>
<ElfStar> See also: save, rehash
<ElfStar> [00:14] #simple# help status
<ElfStar> ### status
<ElfStar> ### status all
<ElfStar> Displays a condensed block of status information about the bot.
<ElfStar> is running. For example:
<ElfStar> [01:15] #Wcc# status
<ElfStar> I am Anakha, running eggdrop v1.6.16+stripping: 171 users (mem: 315k)
<ElfStar> Online for 14 days, 02:50 (background) CPU 71:29 cache hit 40.3
<ElfStar> Admin: Wcc
<ElfStar> Config file: eggdrop.conf
<ElfStar> OS: FreeBSD 4.8-RELEASE-p1
<ElfStar> Tcl library: /usr/local/lib/tcl8.4
<ElfStar> Tcl version: 8.4.2 (header version 8.4.2)
<ElfStar> Loaded module information:
<ElfStar> Channels: #|DAWG|Net, #|DAWG|Tcl
<ElfStar> Online as: D|Anakha!wcc@cia.nu (|DAWG|Anakha - |DAWG|Net)
<ElfStar> Server irc.inet.tele.dk:6667 (connected for 11 days)
<ElfStar> #|DAWG|Net: 6 members, enforcing "+istn" (lurking)
<ElfStar> #|DAWG|Tcl: 42 members, enforcing "+tn" (lurking)
<ElfStar>
<ElfStar>
<ElfStar> The first line tells you the bot's name, what version of Eggdrop it's
<ElfStar> running, the number of users the bot has records of, and the amount of
<ElfStar> memory being used by the userfile. The second line tells you the uptime of
<ElfStar> the bot, CPU time, and cache hit. The third shows the bot's admin, and the
<ElfStar> forth shows its current config file. The fifth line shows what operating
<ElfStar> system the bot is running on. The next two lines show Tcl information. If
<ElfStar> debug mode is enabled, additional info may be shown. Sharing information
<ElfStar> will also be shown if it's being used.
<ElfStar>
<ElfStar> Select information from modules will be displayed after the core
<ElfStar> information. If you use '.status all' instead, you will see all status
<ElfStar> information available from loaded modules.
<ElfStar>
<ElfStar> See also: channel, set, debug
<ElfStar> [00:14] #simple# help traffic
<ElfStar> ### traffic
<ElfStar> Shows total and daily net traffic stats since the last '.restart'.
<ElfStar> Stats groups are IRC, Botnet, Partyline, Transfer.mod and Misc.
<ElfStar>
<ElfStar> See also: restart
<ElfStar> [00:14] #simple# help uptime
<ElfStar> ### uptime
<ElfStar> Displays the bot's current uptime.
<ElfStar>
<ElfStar> See also: status
<ElfStar> [00:14] #simple# help +user
<ElfStar> ### +user <handle> [hostmask]
<ElfStar> Creates a new user record for the handle given. The new user record will
<ElfStar> have no flags, an optional hostmask, and no password.
<ElfStar>
<ElfStar> See also: -user, +host, -host
<ElfStar> [00:14] #simple# help +ignore
<ElfStar> ### +ignore <hostmask> [%<XdXhXm>] [comment]
<ElfStar> Adds an ignore to the list of ignores stored on the bot, with optional
<ElfStar> comment and ignore time. This ignore is stored with your handle as the
<ElfStar> creator. Ignore time has to be expressed in days, hours, and/or minutes.
<ElfStar>
<ElfStar> See also: -ignore, ignores
<ElfStar> [00:14] #simple# help comment
<ElfStar> ### comment <user> <comment>
<ElfStar> Creates or changes the comment field for a user. The comment field can only
<ElfStar> be seen via 'whois' or 'match'. Non-masters cannot see the comment field.
<ElfStar> [00:14] #simple# help binds
<ElfStar> ### binds [type/match] [all]
<ElfStar> Shows the Tcl bindings in effect, in a list similar to this:
<ElfStar> Command bindings:
<ElfStar> TYPE FLGS COMMAND HITS BINDING (TCL)
<ElfStar> msg -|- rose 0 msg_rose
<ElfStar> msg -|- go 0 msg_go
<ElfStar> dcc m|- bind 0 cmd_bind
<ElfStar> pub -|- gross 0 pub_gross
<ElfStar> The fields should be self-explanatory, except for HITS, which records the
<ElfStar> number of times that binding has been called. If not, go read the file
<ElfStar> 'doc/tcl-commands.doc' for help on the Tcl bind command. Note that the
<ElfStar> builtin commands are now shown. You may also specify a type of binding to
<ElfStar> show (i.e. '.binds msg') or you can specify a wild card match (i.e.
<ElfStar> '.binds *seen*') if you want to narrow the field a bit. The wild card
<ElfStar> matches will match against the TYPE, COMMAND and BINDING fields. You can
<ElfStar> view more binds by adding 'all' to the end of the command.
<ElfStar>
<ElfStar> See also: tcl
<ElfStar> [00:14] #simple# help ignores
<ElfStar> ### ignores [wildcard]
<ElfStar> Shows a list of hostmasks from which the bot is currently ignoring msgs,
<ElfStar> notices, etc. There are two types of ignores: permanent and temporary.
<ElfStar> Permanent ignores never automatically expire. You must use '.-ignore'
<ElfStar> to remove them.
<ElfStar>
<ElfStar> Here is a sample permanent ignore:
<ElfStar> [ 1] *!*@217.156.44.184 (perm)
<ElfStar> Wcc: go away
<ElfStar> Started 523 days ago
<ElfStar>
<ElfStar> The number (1) can be used to reference the ignore if you wish to remove it
<ElfStar> (see '.help -ignore'). Next is the actual hostmask being ignored. The
<ElfStar> "(perm)" means that the ignore is "permanent": that is, it doesn't
<ElfStar> automatically expire. The second line of the ignore entry is the comment
<ElfStar> ("go away"), and who set the ban (Wcc). The last line shows when the ignore
<ElfStar> was added.
<ElfStar>
<ElfStar> Here is a sample temporary ignore:
<ElfStar> [ 10] blah!blah@blah.cc (expires in 1 day)
<ElfStar> Wcc: requested
<ElfStar> Started 18:02
<ElfStar>
<ElfStar> Here, you see the "perm" in the parentheses next to the hostmask is instead
<ElfStar> an expire time. This means that the ignore will expire automatically in one
<ElfStar> day.
<ElfStar>
<ElfStar> If you use '.ignores <wildcard>', it will list all the ignores
<ElfStar> that match against your wildcard.
<ElfStar>
<ElfStar> See also: +ignore, -ignore
<ElfStar> [00:14] #simple# help -user
<ElfStar> ### -user <handle>
<ElfStar> Removes the specified handle's user record.
<ElfStar>
<ElfStar> See also: +user, +bot, -bot
<ElfStar> [00:14] #simple# help -ignore
<ElfStar> ### -ignore <hostmask/number>
<ElfStar> Removes the specified ignore from the list of ignores stored on the bot. You
<ElfStar> may also reference the ignore by the number shown by the 'ignores' command.
<ElfStar>
<ElfStar> See also: +ignore, ignores
<ElfStar> [00:14] #simple# help dccstat
<ElfStar> ### dccstat
<ElfStar> Displays a table-format list of all "dcc" connections in use on the bot.
<ElfStar> Dcc stands for "Direct Client-to-client Communication", and Eggdrop expands
<ElfStar> this to cover every open socket. Any type of network connection to the bot
<ElfStar> is considered a "dcc" connection.
<ElfStar>
<ElfStar> The headings of the table are:
<ElfStar> SOCK the socket number of this connection (always unique)
<ElfStar> ADDR the ip address mask of the host the bot is connected to, if
<ElfStar> applicable
<ElfStar> PORT the port number being used for this connection
<ElfStar> NICK the handle of the user or bot, if applicable
<ElfStar> HOST the hostname corresponding to the IP address, if available
<ElfStar> TYPE the type of dcc connection (see below)
<ElfStar>
<ElfStar> The types of connections currently possible are as follows (but more are
<ElfStar> being added all the time):
<ElfStar> CHAT dcc-chat partyline user
<ElfStar> PASS user entering dcc chat (being asked for password)
<ElfStar> SEND user sending a file
<ElfStar> GET sending a file to a user
<ElfStar> GETP pending get (waiting for the user to acknowledge)
<ElfStar> LSTN telnet listening port (in place of a hostname, it will show the
<ElfStar> callback procedure name, or a mask of acceptable handles)
<ElfStar> T-IN incoming telnet user (being asked for handle)
<ElfStar> FILE user in dcc-chat file area
<ElfStar> BOT connected bot (botnet connection)
<ElfStar> BOT* pending bot link (waiting for acknowledgement)
<ElfStar> RELA user in relay connection to another bot
<ElfStar> >RLY bot being relay'd to (one for each "RELA")
<ElfStar> CONN pending telnet connection (chat, relay, bot-link, etc)
<ElfStar> NEW new user via telnet (entering a handle)
<ElfStar> NEWP new user via telnet (entering a password)
<ElfStar>
<ElfStar> In addition, 'CHAT' and 'BOT' have flags listed for each connection. Capital
<ElfStar> letters mean that the flag is on, and lowercase letters mean that the flag
<ElfStar> is off. The flags for 'CHAT' are:
<ElfStar> C in file area, but allowed to return to party line
<ElfStar> P party line access only
<ElfStar> T telnet connection (instead of dcc chat)
<ElfStar> E echo is on
<ElfStar> P paging is on
<ElfStar>
<ElfStar> The flags for 'BOT' are:
<ElfStar> P ping sent, waiting for reply
<ElfStar> U user-file sharing is active
<ElfStar> C local bot initiated the connection
<ElfStar> O user-file offered, waiting for reply
<ElfStar> S in the process of sending the user-file
<ElfStar> G in the process of getting the user-file
<ElfStar> W warned this bot to stop hubbing
<ElfStar> L leaf-only bot (not allowed to be a hub)
<ElfStar> I bot is currently in the 'linking' stage
<ElfStar> A bot is being aggressively shared with
<ElfStar>
<ElfStar> For 'CHAT' users, the party-line channel is also listed.
<ElfStar> [00:14] #simple# help debug
<ElfStar> ### debug
<ElfStar> Display a dump of memory allocation information, assuming the bot was
<ElfStar> compiled with memory debugging. It's useless to anyone but developers
<ElfStar> trying to find memory leaks.
<ElfStar> [00:14] #simple# help rehash
<ElfStar> ### rehash
<ElfStar> Reloads the bot's config file, which resets all changes made via the
<ElfStar> '.set' command and reloads any Tcl scripts your config loads. It also
<ElfStar> saves and reloads the user file from disk, just to give it some exercise.
<ElfStar>
<ElfStar> See also: save, reload, restart, rehelp, relang
<ElfStar> [00:14] #simple# help restart
<ElfStar> ### restart
<ElfStar> Restarts the Tcl interpreter, wipes all timers, reloads all modules, and
<ElfStar> reloads the config file for the bot (which resets any changes made via the
<ElfStar> '.set' command and reloads any Tcl scripts your config loads). As with
<ElfStar> the '.rehash' command, it also saves and reloads the user file from disk.
<ElfStar>
<ElfStar> See also: rehash, reload, save
<ElfStar> [00:14] #simple# help module
<ElfStar> ### module [modulename]
<ElfStar> Reports the names of currently loaded modules, including dependencies and a
<ElfStar> status report. If you specify a module name, only information on that module
<ElfStar> will be displayed.
<ElfStar>
<ElfStar> See also: modules, loadmod, unloadmod
<ElfStar> [00:14] #simple# help die
<ElfStar> ### die [reason]
<ElfStar> This kills the bot. The bot goes offline immediately, logging who issued
<ElfStar> the 'die' command. You shouldn't have to use this too often. If you specify
<ElfStar> a reason, it is logged, otherwise the reason is "authorized by <handle>".
<ElfStar> [00:14] #simple# help simul
<ElfStar> ### simul <handle> <text>
<ElfStar> This allows you to simulate the specified handle typing the given text.
<ElfStar>
<ElfStar> For example:
<ElfStar> .simul dweeb .quit
<ElfStar>
<ElfStar> This would appear just as if "dweeb" typed ".quit". This command will not
<ElfStar> work unless eggdrop has simul enabled in the config file. Please use this
<ElfStar> command ethically.
<ElfStar> [00:14] #simple# help loadmod
<ElfStar> ### loadmod <module>
<ElfStar> Loads the specified module.
<ElfStar>
<ElfStar> See also: modules, module, unloadmod
<ElfStar> [00:14] #simple# help unloadmod
<ElfStar> ### unloadmod <module>
<ElfStar> Unloads the specified module.
<ElfStar>
<ElfStar> See also: modules, module, loadmod
<ElfStar> [00:14] #simple# help language
<ElfStar> No help available on that.
<ElfStar> [00:14] #simple# help set
<ElfStar> ### set <variable> [value]
<ElfStar> Changes the values of config-file settings of the bot, or, if used without
<ElfStar> a value parameter, shows the current value of a setting. Any config file
<ElfStar> setting changed with this command will be reset when the config file is
<ElfStar> reloaded. Here are the variables that can be modified with this command
<ElfStar> (note that other modules can add variables):
<ElfStar> botnet-nick userfile motd paranoid-telnet-flood
<ElfStar> my-ip telnet-banner admin use-telnet-banner
<ElfStar> temp-path notify-newusers owner my-hostname
<ElfStar> nat-ip dcc-sanitycheck network whois-fields
<ElfStar> username version firewall telnet-flood
<ElfStar> ignore-time dcc-flood-thr hourly-updates connect-timeout
<ElfStar> resolve-timeout dupwait-timeout require-p keep-all-logs
<ElfStar> open-telnets stealth-telnets handlen reserved-portrange
<ElfStar> console default-flags log-time max-logsize
<ElfStar> quick-logs logfile-suffix quiet-save sort-users
<ElfStar> die-on-sighup die-on-sigterm remote-boots max-dcc
<ElfStar> max-logs protect-telnet ident-timeout share-unlinks
<ElfStar> allow-dk-cmds userfile-perm switch-logfiles-at
<ElfStar> Use '.help set <variable>' for more info on each variable.
<ElfStar> [00:14] #simple# help tcl
<ElfStar> ### tcl <command>
<ElfStar> Executes the specified Tcl command.
<ElfStar>
<ElfStar> See doc/tcl-commands.doc for details on Tcl commands added to Eggdrop, and
<ElfStar> visit http://tcl.activestate.com/ for more information on Tcl.
<ElfStar> [00:14] #simple# help rehelp
<ElfStar> ### rehelp
<ElfStar> This command forces the bot to recheck all of its help files for changes.
<ElfStar>
<ElfStar> See also: save, reload, restart, relang
<ElfStar> [00:14] #simple# help modules
<ElfStar> ### modules [botname]
<ElfStar> Displays a list of currently loaded modules. If a botname is specified, the
<ElfStar> modules currently loaded on that bot will be displayed instead.
<ElfStar>
<ElfStar> See also: module, loadmod, unloadmod
<ElfStar> [00:14] #simple# help +lang
<ElfStar> ### +lang <language>
<ElfStar> Adds a new language to the top of the language list. All sections are
<ElfStar> rechecked to test if there are language files supporting the language.
<ElfStar>
<ElfStar> See also: -lang, +lsec, -lsec, lstat, relang
<ElfStar> [00:14] #simple# help -lang
<ElfStar> ### -lang <language>
<ElfStar> Removes a language from the language list. If possible, the next available
<ElfStar> language will be loaded.
<ElfStar>
<ElfStar> See also: +lang, +lsec, -lsec, lstat, relang
<ElfStar> [00:14] #simple# help +lsec
<ElfStar> ### +lsec <section>
<ElfStar> Adds a new language section. The bot tries to load the section with the
<ElfStar> preferred language if possible.
<ElfStar>
<ElfStar> See also: -lang, +lang, -lsec, lstat, relang
<ElfStar> [00:14] #simple# help -lsec
<ElfStar> ### -lsec <section>
<ElfStar> Removes a language section. The language bindings are not removed, however.
<ElfStar>
<ElfStar> See also: +lang, -lang, +lsec, lstat, relang
<ElfStar> [00:14] #simple# help lstat
<ElfStar> ### lstat
<ElfStar> Shows the language statistics: all selected languages and a list of all
<ElfStar> language sections.
<ElfStar>
<ElfStar> See also: +lang, -lang, +lsec, -lsec, relang
<ElfStar> [00:14] #simple# help relang
<ElfStar> ### relang
<ElfStar> Try to find language files with a more preferred language than right now.
<ElfStar>
<ElfStar> See also: +lang, -lang, +lsec, -lsec, lstat
<ElfStar> [00:14] #simple# help ldump
<ElfStar> ### ldump
<ElfStar> Dumps all language data to the partyline.
<ElfStar>
<ElfStar> See also: +lang, -lang, +lsec, -lsec, relang, lstat
<ElfStar> [00:14] #simple# help seen
<ElfStar> ### seen <handle>
<ElfStar> Shows the last time <handle> was seen by the bot.
<ElfStar> [00:14] #simple# help store
<ElfStar> ### store
<ElfStar> Stores your console settings so that they are restored automatically the
<ElfStar> next time you join the party line.
<ElfStar> [00:14] #simple# help notes
<ElfStar> ### notes index
<ElfStar> ### notes read <# or ALL>
<ElfStar> ### notes erase <# or ALL>
<ElfStar> Lets you manipulate notes that have been stored for you while you were
<ElfStar> gone.
<ElfStar>
<ElfStar> '.notes index' gives a listing of all the stored notes: who they are
<ElfStar> from, and when they were left.
<ElfStar>
<ElfStar> '.notes read' lets you read some or all notes, according to a
<ElfStar> list of numbers and/or intervals separated by semicolon.
<ElfStar>
<ElfStar> '.notes erase' erases notes after you are finished with them.
<ElfStar>
<ElfStar> Example:
<ElfStar>
<ElfStar> .notes erase 2-4;8;16-
<ElfStar>
<ElfStar> This will erase notes 2-4, note 8, and all notes after (and including) 16.
<ElfStar>
<ElfStar> See also: whom, note, noteigns
<ElfStar> [00:14] #simple# help +noteign
<ElfStar> ### +noteign [user] <ignoremask>
<ElfStar> Add a new ignore to the user's note ignore list. The ignoremask is
<ElfStar> matched against the handle of a user attempting to send a note. Wildcards
<ElfStar> are permitted.
<ElfStar>
<ElfStar> See also: -noteign, noteigns
<ElfStar> [00:14] #simple# help -noteign
<ElfStar> ### -noteign [user] <ignoremask>
<ElfStar> Remove an existing ignore from the user's note ignore list.
<ElfStar>
<ElfStar> See also: +noteign, noteigns
<ElfStar> [00:14] #simple# help noteigns
<ElfStar> ### noteigns [user]
<ElfStar> List all note ignores for the user. All notes sent from users who's handle
<ElfStar> matches one of these ignore masks will be rejected.
<ElfStar>
<ElfStar> See also: +noteign, -noteign
<ElfStar> [00:14] #simple# help note
<ElfStar> ### note <nickname[@bot]> <message>
<ElfStar> Sends a private note to a user on the partyline. If that user is currently
<ElfStar> logged in and not marked as away, the message will be received immediately.
<ElfStar> Otherwise, it will be stored and displayed the next time that user joins the
<ElfStar> partyline. To send a note to someone on a different bot, add "nick@bot" to
<ElfStar> the nickname.
<ElfStar>
<ElfStar> See also: whom, notes
<ElfStar> [00:14] #simple# help fwd
<ElfStar> ### fwd <handle> [destination]
<ElfStar> This allows you to set a 'forwarding address' for notes sent to a user.
<ElfStar> This means if a note needs to be stored for the user, the bot will attempt
<ElfStar> to pass it on to the given user@bot. If the bot is not online then the note
<ElfStar> is still stored locally. If the remote user doesn't exist, the note is lost.
<ElfStar> [00:14] #simple# help files
<ElfStar> ### files
<ElfStar> Moves you into the file transfer sub-system, if it has been enabled on this
<ElfStar> bot. From there you can browse through the files online and use dcc file
<ElfStar> transfers to download and upload.
<ElfStar> [00:14] #simple# help flush
<ElfStar> ### flush <bot>
<ElfStar> This clears the resync buffer for a share-bot. This is useful if you want
<ElfStar> to start over with a userfile transfer. You can unlink the sharebots, flush
<ElfStar> the resync buffer, and relink.
<ElfStar>
<ElfStar> See also: link, unlink, chattr, botattr
<ElfStar> [00:14] #simple# help act
<ElfStar> ### act [channel] <text>
<ElfStar> Performs an action on the current console channel (or otherwise specified
<ElfStar> channel), as if the bot did it. This is just like the /me command in mIRC.
<ElfStar>
<ElfStar> See also: say
<ElfStar> [00:14] #simple# help halfop
<ElfStar> ### halfop <nickname> [channel]
<ElfStar> Gives halfops (+h) to the specified user, so long as the bot has ops on the
<ElfStar> given channel. If no channel is specified, the current console channel will
<ElfStar> be used.
<ElfStar>
<ElfStar> See also: console, dehalfop
<ElfStar> [00:14] #simple# help say
<ElfStar> ### say [channel] <text>
<ElfStar> Sends the specified text to the given channel, as if the bot "said" it. If
<ElfStar> a channel is not specified, the current console channel will be used.
<ElfStar>
<ElfStar> See also: console, act, msg
<ElfStar> [00:14] #simple# help resetbans
<ElfStar> ### resetbans [channel]
<ElfStar> Resets the ban list for the specified channel. Any bans on the channel that
<ElfStar> aren't in the bot's ban list (either the global list or the local channel
<ElfStar> ban list) will be removed, and if there are any bans in the global ban list
<ElfStar> or channel ban list that are not currently on the channel but should be,
<ElfStar> they will be added.
<ElfStar>
<ElfStar> See also: resetexempts, resetinvites, bans, +ban, -ban
<ElfStar> [00:14] #simple# help deop
<ElfStar> ### deop <nickname> [channel]
<ElfStar> Removes ops (-o) from the specified user, so long as the bot has ops on the
<ElfStar> given channel. If no channel is specified, the current console channel
<ElfStar> will be used.
<ElfStar>
<ElfStar> See also: console, op
<ElfStar> [00:14] #simple# help invite
<ElfStar> ### invite <nickname> [channel]
<ElfStar> Invites someone from irc to given channel. If no channel is specified,
<ElfStar> the current console channel will be used. This is most useful when the
<ElfStar> channel is +i. A user with the +o flag can also request an invite from
<ElfStar> the bot with /MSG INVITE.
<ElfStar>
<ElfStar> See also: console
<ElfStar> [00:14] #simple# help topic
<ElfStar> ### topic [channel] [text]
<ElfStar> Changes the specified channel's topic, assuming the bot is a chanop or
<ElfStar> the channel is not +t. If a channel is not specified, the current console
<ElfStar> channel will be used. If no text is specified, the current topic will be
<ElfStar> displayed.
<ElfStar>
<ElfStar> See also: console
<ElfStar> [00:14] #simple# help resetinvites
<ElfStar> ### resetinvites [channel]
<ElfStar> Resets the invite list for the channel. This command behaves exactly like
<ElfStar> resetbans, except it is for invites.
<ElfStar>
<ElfStar> See also: resetbans, resetexempts, invites, +invite, -invite
<ElfStar> [00:14] #simple# help op
<ElfStar> ### op <nickname> [channel]
<ElfStar> Gives ops (+o) to the specified user, so long as the bot has ops on the
<ElfStar> given channel. If no channel is specified, the current console channel will
<ElfStar> be used.
<ElfStar>
<ElfStar> See also: console, deop
<ElfStar> [00:14] #simple# help channel
<ElfStar> ### channel [channel-name]
<ElfStar> Shows you an extensive display of the users on a channel, and the current
<ElfStar> channel attributes. By default, it shows you the channel you are currently
<ElfStar> viewing on the console, but you can specify another channel if you wish.
<ElfStar>
<ElfStar> The first line will look like:
<ElfStar>
<ElfStar> Channel #hiya, 36 members, mode +tnl 43:
<ElfStar>
<ElfStar> This means that the bot is on the channel #hiya, which has a total of 36
<ElfStar> members (including itself), and the channel mode is +tnl 43. If the bot
<ElfStar> isn't on the channel it is supposed to be on, it will say "Desiring channel
<ElfStar> #hiya, 0 members, mode +:" instead. Next is a list of the users on the
<ElfStar> channel, with each entry looking like this:
<ElfStar>
<ElfStar> <D|Ares> NICKNAME HANDLE JOIN IDLE USER@HOST
<ElfStar> <D|Ares> @Wcc Wcc --- N Wcc@blah.atlaga.adelphia.net
<ElfStar>
<ElfStar> The "@Wcc" means that the user's nickname is Wcc and that he is a chanop.
<ElfStar> The second "Wcc" is the user's handle. Sometimes this will differ from the
<ElfStar> nickname a person is using. The time displayed is the time the user joined
<ElfStar> the channel. The next field is the user's status flag. These are the same
<ElfStar> as the flags listed in .help whois. Global flags are uppercase. Only
<ElfStar> the 'highest' flag is displayed.
<ElfStar>
<ElfStar> The last two fields are the user's idle time, and the user@host they are
<ElfStar> connecting from
<ElfStar>
<ElfStar> See also: console, whois, status
<ElfStar> [00:14] #simple# help dehalfop
<ElfStar> ### dehalfop <nickname> [channel]
<ElfStar> Removes halfops (-h) from the specified user, so long as the bot has ops on
<ElfStar> the given channel. If no channel is specified, the current console channel
<ElfStar> will be used.
<ElfStar>
<ElfStar> See also: console, halfop
<ElfStar> [00:14] #simple# help resetexempts
<ElfStar> ### resetexempts [channel]
<ElfStar> Resets the exempt list for the channel. This command behaves exactly like
<ElfStar> resetbans, except it is for exempts.
<ElfStar>
<ElfStar> See also: resetbans, resetinvites, exempts, +exempt, -exempt
<ElfStar> [00:14] #simple# help devoice
<ElfStar> ### devoice <nickname> [channel]
<ElfStar> Removes a voice (-v) from the specified user, so long as the bot has ops on
<ElfStar> the given channel. If no channel is specified, the current console channel
<ElfStar> will be used.
<ElfStar>
<ElfStar> See also: console
<ElfStar> [00:14] #simple# help voice
<ElfStar> ### voice <nickname> [channel]
<ElfStar> Gives a voice (+v) to the specified user, so long as the bot has ops on the
<ElfStar> given channel. If no channel is specified, the current console channel will
<ElfStar> be used.
<ElfStar>
<ElfStar> See also: console, devoice
<ElfStar> [00:14] #simple# help msg
<ElfStar> ### msg <nickname> <text>
<ElfStar> Sends a private message to a nick on IRC from the bot.
<ElfStar>
<ElfStar> See also: say, act
<ElfStar> [00:14] #simple# help adduser
<ElfStar> ### adduser [!]<nickname> [handle]
<ElfStar> Creates a new user record for a user on the channel, using their current
<ElfStar> hostname. It's similar to a user /msg'ing the bot 'hello', except that no
<ElfStar> information is sent to the user. If the bot already knows someone by that
<ElfStar> nickname, and the user on the channel doesn't have a bot record, then it
<ElfStar> does the equivalent of an 'ident' for that user--except that, again, no
<ElfStar> information is sent to the user.
<ElfStar>
<ElfStar> If the user is using a different nickname than the bot normally knows them
<ElfStar> by, you can specify their "handle" (the nickname that the bot remembers
<ElfStar> them by).
<ElfStar>
<ElfStar> If you want to add a user using a static hostmask, prefix their nick
<ElfStar> with a '!'. For example:
<ElfStar>
<ElfStar> .adduser !Lamer
<ElfStar>
<ElfStar> See also: deluser, +host, -host, +user, -user
<ElfStar> [00:14] #simple# help deluser
<ElfStar> ### deluser <nickname>
<ElfStar> Deletes a user record for a user on the channel, using their current
<ElfStar> hostname. Channel masters can remove users so long as the user isn't a
<ElfStar> global master.
<ElfStar>
<ElfStar> See also: adduser, +user, -user, +host, -host
<ElfStar> [00:14] #simple# help reset
<ElfStar> ### reset [channel]
<ElfStar> Clears out the bot's channel information and forces it to gather the
<ElfStar> information from the server all over again, as if it had just joined the
<ElfStar> channel. It's not really very useful, but it could be if an odd bug causes
<ElfStar> the channel information to get scrambled. You can omit the channel name
<ElfStar> to reset ALL channels.
<ElfStar>
<ElfStar> See also: channel
<ElfStar> [00:14] #simple# help servers
<ElfStar> ### servers
<ElfStar> Lists the servers contained in the bot's server list. This is the list
<ElfStar> the bot rotates through when changing servers. It starts with a static list
<ElfStar> which is loaded from the config file when the bot is started. After that,
<ElfStar> you can add servers with the '.jump' command. The server list will
<ElfStar> indicate which server the bot is currently on. For example:
<ElfStar>
<ElfStar> <D|Ares> irc.arcti.ca:6667 (irc.arcti.ca) <- I am here
<ElfStar> See also: jump
<ElfStar> [00:14] #simple# help jump
<ElfStar> ### jump [server [port [pass]]]
<ElfStar> Makes the bot jump to another server. If you don't specify a server, it
<ElfStar> will jump to the next server in the server list (see '.help servers').
<ElfStar> If you specify a server, it will jump to that server (the default port is
<ElfStar> 6667, unless you specified a different default port in your config file).
<ElfStar> If the server is not in the server list already, it will be added to it.
<ElfStar> Jumping servers ALWAYS makes the bot lose ops! Be careful!
<ElfStar>
<ElfStar> Remember, you can't specify a password without specifing a port as well.
<ElfStar>
<ElfStar> See also: servers
<ElfStar> [00:14] #simple# help dump
<ElfStar> ### dump <text>
<ElfStar> Dumps the given text to the IRC server.
<ElfStar>
<ElfStar> See http://www.ietf.org/rfc/rfc1459.txt for more information on the
<ElfStar> IRC protocol.
<ElfStar> [00:14] #simple# help clearqueue
<ElfStar> ### clearqueue <queue>
<ElfStar> Removes all msgs from the specified queue.
<ElfStar>
<ElfStar> The queue argument can be one of:
<ElfStar>
<ElfStar> mode, server, help, all
<ElfStar> [00:14] #simple# help info
<ElfStar> ### info [channel] [info-line]
<ElfStar> Sets your info line. This line is shown via the /msg commands 'who' and
<ElfStar> 'whois'. If you have set greet on, it is also shown when you joins the
<ElfStar> channel. If the info line begins with an '@', then it is "locked", and tou
<ElfStar> may no longer change it.
<ElfStar> See also: chinfo
<ElfStar> [00:14] #simple# help +ban
<ElfStar> ### +ban <hostmask> [channel] [%<XdXhXm>] [comment]
<ElfStar> Adds a ban to the list of bans stored on the bot, with optional comment and
<ElfStar> ban time. This ban is stored with your handle as the creator, and will be
<ElfStar> in effect for every channel if no channel is specified. Prefixing a comment
<ElfStar> with '@' will make it only visible within the bot, and not used as the ban
<ElfStar> reason. Ban time has to be expressed in days, hours, and/or minutes.
<ElfStar>
<ElfStar> See also: bans, -ban, stick, unstick
<ElfStar> [00:14] #simple# help -ban
<ElfStar> ### -ban <banmask or number> [channel]
<ElfStar> Removes the specified ban from the list of bans stored on the bot. You may
<ElfStar> also reference the ban by the number shown by the 'bans' command.
<ElfStar>
<ElfStar> See also: bans, +ban, stick, unstick
<ElfStar> [00:14] #simple# help bans
<ElfStar> ### bans [[channel/all]/wildcard]
<ElfStar> Shows you a list of the global bans active on the current channel, and the
<ElfStar> list of channel-specific bans, as well as any bans that are on the channel
<ElfStar> but weren't placed by the bot.
<ElfStar>
<ElfStar> Here's a sample entry;
<ElfStar> [ 5] *!*habib@*frys.com (perm)
<ElfStar> paulie: revolving check policy
<ElfStar> Created 15:10
<ElfStar>
<ElfStar> The number (5) can be used to reference the ban if you wish to remove it
<ElfStar> (see '-ban'). Next is the actual hostmask being banned. The "(perm)"
<ElfStar> means that the ban is "permanent": that is, it doesn't automatically expire.
<ElfStar> If there is an elapsed time showing instead, the time displayed is how long
<ElfStar> the ban has been active. These types of bans expire after two hours. The
<ElfStar> second line of the ban entry is the comment ("revolving check policy"), and
<ElfStar> who set the ban (paulie). The last line shows when the ban was added, and
<ElfStar> possibly the last time the ban was activated on the channel (if it's
<ElfStar> different from the creation time).
<ElfStar>
<ElfStar> Sometimes there will be a "!" or "*" right before the number. A "!" means
<ElfStar> the ban is in the bot's ban list, but is not currently on the channel. A "*"
<ElfStar> marks a ban which is NOT in the bot's ban list but IS on the channel.
<ElfStar>
<ElfStar> If you use 'bans' without an argument, it will show you only the bans which
<ElfStar> are currently active on the channel. If you use 'bans all', it will show you
<ElfStar> every ban in the global ban list and on the channel. If you use 'bans
<ElfStar> <wildcard>', it will list all bans (active or not) that match against your
<ElfStar> wildcard. Consider it a 'bans all' list matched against your wildcard.
<ElfStar>
<ElfStar> The ban list may change according to which channel you're currently viewing
<ElfStar> in the console. Different bans may be active on different channels. If you
<ElfStar> specify a channel name, that channel will be used instead of your current
<ElfStar> console channel.
<ElfStar>
<ElfStar> See also: -ban, +ban, console, chanset, chaninfo, stick, unstick
<ElfStar> [00:14] #simple# help stick
<ElfStar> ### stick [ban/exempt/invite] <hostmask/number> [channel]
<ElfStar> Makes a ban, exempt, or invite "sticky". This means that the bot will always
<ElfStar> try to keep it active on the channel, even if the channel is using dynamic
<ElfStar> bans. Obviously, if the channel isn't using dynamic bans, this has no
<ElfStar> effect.
<ElfStar>
<ElfStar> See also: unstick, bans, exempts, invites, +ban, +exempt, +invite
<ElfStar> [00:14] #simple# help +exempt
<ElfStar> ### +exempt <hostmask> [channel] [%<XdXhXm>] [comment]
<ElfStar> Adds an exempt to the list of exempts stored on the bot, with optional
<ElfStar> comment and exempt time. This exempt is stored with your handle as the
<ElfStar> creator, and will be in effect for every channel if no channel is specified.
<ElfStar> Exempt time has to be expressed in days, hours, and/or minutes.
<ElfStar>
<ElfStar> See also: exempts, -exempt, stick, unstick
<ElfStar> [00:14] #simple# help -exempt
<ElfStar> ### -exempt <hostmask or number>
<ElfStar> Removes the specified exempt from the list of exempts stored on the bot. You
<ElfStar> may also reference the exempt by the number shown by the 'exempts' command.
<ElfStar>
<ElfStar> See also: exempts, +exempt, stick, unstick
<ElfStar> [00:14] #simple# help exempts
<ElfStar> ### exempts [[channel/all]/wildcard]
<ElfStar> Shows you a list of the global exempts active on the current channel, and
<ElfStar> the list of channel-specific exempts, as well as any exempts that are on the
<ElfStar> channel but weren't placed by the bot.
<ElfStar>
<ElfStar> Here's a sample entry;
<ElfStar> ! [ 3] *!test@test.com (perm)
<ElfStar> Wcc: requested
<ElfStar> Created 01:15
<ElfStar>
<ElfStar> The number (3) can be used to reference the exempt if you wish to remove it
<ElfStar> (see '-exempt'). Next is the actual hostmask being exempted. The "(perm)"
<ElfStar> means that the exempt is "permanent": that is, it doesn't automatically
<ElfStar> expire. If there is an elapsed time showing instead, the time displayed is
<ElfStar> how long the exempt has been active. These types of exempts expire after one
<ElfStar> hour. The second line of the exempt entry is the comment ("requested"), and
<ElfStar> who set the exempt (Wcc). The last line shows when the exempt was added, and
<ElfStar> possibly the last time the exempt was activated on the channel (if it's
<ElfStar> different from the creation time).
<ElfStar>
<ElfStar> Sometimes there will be a "!" or "*" right before the number. A "!" means
<ElfStar> the exempt is in the bot's exempt list, but is not currently on the channel.
<ElfStar> A "*" marks an exempt which is NOT in the bot's exempt list but IS on the
<ElfStar> channel.
<ElfStar>
<ElfStar> If you use 'exempts' without an argument, it will show you only the exempts
<ElfStar> which are currently active on the channel. If you use 'exempts all', it will
<ElfStar> show you every exempt in the global exempt list and on the channel. If you
<ElfStar> use 'exempts <wildcard>', it will list all exempts (active or not) that
<ElfStar> match against your wildcard. Consider it a 'exempts all' list matched
<ElfStar> against your wildcard.
<ElfStar>
<ElfStar> The exempt list may change according to which channel you're currently
<ElfStar> viewing in the console. Different exempts may be active on different
<ElfStar> channels. If you specify a channel name, that channel will be used instead
<ElfStar> of your current console channel.
<ElfStar>
<ElfStar> See also: -exempt, +exempt, console, chanset, chaninfo, stick, unstick
<ElfStar> [00:14] #simple# help unstick
<ElfStar> ### unstick [ban/exempt/invite] <hostmask/number> [channel]
<ElfStar> Makes a "sticky" ban, exempt, or invite normal again.
<ElfStar>
<ElfStar> See also: stick, bans, exempts, invites, -ban, -exempt, -invite
<ElfStar> [00:14] #simple# help +invite
<ElfStar> ### +invite <hostmask> [channel] [%<XdXhXm>] [comment]
<ElfStar> Adds an invite to the list of invites stored on the bot, with optional
<ElfStar> comment and invite time. This invite is stored with your handle as the
<ElfStar> creator, and will be in effect for every channel if no channel is specified.
<ElfStar> Invite time has to be expressed in days, hours, and/or minutes.
<ElfStar>
<ElfStar> See also: invites, -invite, stick, unstick
<ElfStar> [00:14] #simple# help -invite
<ElfStar> ### -invite <hostmask or number>
<ElfStar> Removes the specified invite from the list of invites stored on the bot. You
<ElfStar> may also reference the invite by the number shown by the 'invites' command.
<ElfStar>
<ElfStar> See also: invites, +invite, stick, unstick
<ElfStar> [00:14] #simple# help invites
<ElfStar> ### invites [[channel/all]/wildcard]
<ElfStar> Shows you a list of the global invites active on the current channel, and
<ElfStar> the list of channel-specific invites, as well as any invites that are on the
<ElfStar> channel but weren't placed by the bot.
<ElfStar>
<ElfStar> Here's a sample entry;
<ElfStar> ! [ 3] *!test@test.com (perm)
<ElfStar> Wcc: requested
<ElfStar> Created 01:15
<ElfStar>
<ElfStar> The number (3) can be used to reference the invite if you wish to remove it
<ElfStar> (see '-invite'). Next is the actual hostmask being invited. The "(perm)"
<ElfStar> means that the invite is "permanent": that is, it doesn't automatically
<ElfStar> expire. If there is an elapsed time showing instead, the time displayed is
<ElfStar> how long the invite has been active. These types of invites expire after one
<ElfStar> hour. The second line of the invite entry is the comment ("requested"), and
<ElfStar> who set the invite (Wcc). The last line shows when the invite was added, and
<ElfStar> possibly the last time the invite was activated on the channel (if it's
<ElfStar> different from the creation time).
<ElfStar>
<ElfStar> Sometimes there will be a "!" or "*" right before the number. A "!" means
<ElfStar> the invite is in the bot's invite list, but is not currently on the channel.
<ElfStar> A "*" marks an invite which is NOT in the bot's invite list but IS on the
<ElfStar> channel.
<ElfStar>
<ElfStar> If you use 'invites' without an argument, it will show you only the invites
<ElfStar> which are currently active on the channel. If you use 'invites all', it will
<ElfStar> show you every invite in the global invite list and on the channel. If you
<ElfStar> use 'invites <wildcard>', it will list all invites (active or not) that
<ElfStar> match against your wildcard. Consider it a 'invites all' list matched
<ElfStar> against your wildcard.
<ElfStar>
<ElfStar> The invite list may change according to which channel you're currently
<ElfStar> viewing in the console. Different invites may be active on different
<ElfStar> channels. If you specify a channel name, that channel will be used instead
<ElfStar> of your current console channel.
<ElfStar>
<ElfStar> See also: -invite, +invite, console, chanset, chaninfo, stick, unstick
<ElfStar> [00:14] #simple# help +chrec
<ElfStar> ### +chrec <handle> [channel]
<ElfStar> Adds an empty channel record for the specified user so that channel lastons
<ElfStar> and info lines can be saved. No flags are associated with the channel.
<ElfStar>
<ElfStar> See also: -chrec, +chan, -chan, chattr
<ElfStar> [00:14] #simple# help -chrec
<ElfStar> ### -chrec <handle> [channel]
<ElfStar> Removes a channel record for the specified user, including channel lastons,
<ElfStar> info lines, and flags.
<ElfStar>
<ElfStar> See also: +chrec, chattr
<ElfStar> [00:14] #simple# help chaninfo
<ElfStar> ### chaninfo <channel>
<ElfStar> This lists all the settings for the bot on the given channel.
<ElfStar> It shows any of the following:
<ElfStar> chanmode These modes are enforced on the channel. Both + and -
<ElfStar> modes can be enforced.
<ElfStar> idle-kick Kick idle users that are not +f or above on the channel
<ElfStar> after how many minutes (set this to 0 to disable).
<ElfStar> ATTENTION: Due to security concerns, only permanent owners can set
<ElfStar> the need-* modes.
<ElfStar> need-op This Tcl command will be executed when the bot doesn't
<ElfStar> have ops.
<ElfStar> need-invite This Tcl command will be executed when the bot needs
<ElfStar> an invite to the channel (i.e. the channel is +i).
<ElfStar> need-key This Tcl command will be executed when the bot needs
<ElfStar> the key to the channel to join.
<ElfStar> need-unban This Tcl command will be executed when the bot needs
<ElfStar> to be unbanned from the channel to join.
<ElfStar> need-limit This Tcl command will be executed when the bot needs
<ElfStar> the channel limit to be raised to join.
<ElfStar> stopnethack-mode This setting will make the bot de-op anyone who
<ElfStar> enters the channel with serverops. There are seven
<ElfStar> different modes for this settings:
<ElfStar> 0 turn off
<ElfStar> 1 isoptest (allow serverop if registered op)
<ElfStar> 2 wasoptest (allow serverop if user had op before
<ElfStar> split)
<ElfStar> 3 allow serverop if isop or wasop
<ElfStar> 4 allow serverop if isop and wasop
<ElfStar> 5 If the channel is -bitch, see stopnethack-mode 3
<ElfStar> If the channel is +bitch, see stopnethack-mode 1
<ElfStar> 6 If the channel is -bitch, see stopnethack-mode 2
<ElfStar> If the channel is +bitch, see stopnethack-mode 4
<ElfStar> revenge-mode This settings defines how the bot should punish
<ElfStar> bad users when revenging. There are four possible
<ElfStar> settings:
<ElfStar> 0 Deop the user.
<ElfStar> 1 Deop the user and give them the +d flag for the
<ElfStar> channel.
<ElfStar> 2 Deop the user, give them the +d flag for the
<ElfStar> channel, and kick them.
<ElfStar> 3 Deop the user, give them the +d flag for the
<ElfStar> channel, kick, and ban them.
<ElfStar> ban-time Set here how long temporary bans will last (in
<ElfStar> minutes). If you set this setting to 0, the bot will
<ElfStar> never remove them.
<ElfStar> exempt-time Set here how long temporary exempts will last (in
<ElfStar> minutes). If you set this setting to 0, the bot will
<ElfStar> never remove them. The bot will check the exempts
<ElfStar> every X minutes, but will not remove the exempt if a
<ElfStar> ban is set on the channel that matches that exempt.
<ElfStar> Once the ban is removed, then the exempt will be
<ElfStar> removed the next time the bot checks. Please note
<ElfStar> that this is an IRCnet feature.
<ElfStar> invite-time Set here how long temporary invites will last (in
<ElfStar> minutes). If you set this setting to 0, the bot will
<ElfStar> never remove them. The bot will check the invites
<ElfStar> every X minutes, but will not remove the invite if a
<ElfStar> channel is set to +i. Once the channel is -i then the
<ElfStar> invite will be removed the next time the bot checks.
<ElfStar> Please note that this is an IRCnet feature.
<ElfStar> aop-delay This is used for autoop, autohalfop, autovoice.
<ElfStar> If an op or voice joins a channel while another op or
<ElfStar> voice is pending, the bot will attempt to put both
<ElfStar> modes on one line.
<ElfStar> aop-delay 0 No delay is used.
<ElfStar> aop-delay X An X second delay is used.
<ElfStar> aop-delay X:Y Random delay between X and Y is used.
<ElfStar> The following can be set + or - (e.g. .chanset #channel -enforcebans)
<ElfStar> enforcebans When a ban is set, kick people who are on the channel
<ElfStar> and match the ban?
<ElfStar> dynamicbans Only activate bans on the channel when necessary?
<ElfStar> This keeps the channel's ban list from getting
<ElfStar> excessively long. The bot still remembers every ban,
<ElfStar> but it only activates a ban on the channel when it sees
<ElfStar> someone join who matches that ban.
<ElfStar> userbans Allow bans to be made by users directly? If turned
<ElfStar> off, the bot will require all bans to be made through
<ElfStar> the bot's console.
<ElfStar> dynamicexempts Only activate exempts on the channel when
<ElfStar> necessary? This keeps the channel's exempt list from
<ElfStar> getting excessively long. The bot still remembers every
<ElfStar> exempt, but it only activates a exempt on the channel
<ElfStar> when it sees a ban set that matches the exempt. The
<ElfStar> exempt remains active on the channel for as long as the
<ElfStar> ban is still active.
<ElfStar> userexempts Allow exempts to be made by users directly? If
<ElfStar> turned off, the bot will require all exempts to be made
<ElfStar> through the bot's console.
<ElfStar> dynamicinvites Only activate invites on the channel when necessary?
<ElfStar> This keeps the channel's invite list from getting
<ElfStar> excessively long. The bot still remembers every invite,
<ElfStar> but the invites are only activated when the channel is
<ElfStar> set to invite only and a user joins after requesting an
<ElfStar> invite. Once set, the invite remains until the channel
<ElfStar> goes to -i.
<ElfStar> userinvites Allow invites to be made by users directly? If turned
<ElfStar> off, the bot will require all invites to be made through
<ElfStar> the bot's console.
<ElfStar> autoop Op users with the +o flag as soon as they join the
<ElfStar> channel? This is insecure and not recommended.
<ElfStar> autohalfop Halfop users with the +l flag as soon as they join
<ElfStar> the channel? This is insecure and not recommended.
<ElfStar> bitch Only let users with the +o flag have op on the
<ElfStar> channel?
<ElfStar> greet Say a user's info line when they join the channel?
<ElfStar> protectops Re-op a user with the +o flag if they get deopped?
<ElfStar> protecthalfops Re-halfop a user with the +l flag if they get
<ElfStar> dehalfopped?
<ElfStar> protectfriends Re-op a user with the +f flag if they get deopped?
<ElfStar> statuslog Log the channel status line every 5 minutes? This
<ElfStar> shows the bot's status on the channel (op, voice, etc.),
<ElfStar> the channel's modes, and the number of +m, +o, +v, +n,
<ElfStar> +b, +e, and +I users on the channel. A sample status
<ElfStar> line follows:
<ElfStar>
<ElfStar> [01:40] @#chan (+istn) : [m/1 o/1 v/4 n/7 b/1 e/5 I/7]
<ElfStar> revenge Remember people who deop/kick/ban the bot, valid ops,
<ElfStar> or friends and punish them? Users with the +f flag are
<ElfStar> exempt from revenge.
<ElfStar> revengebot This is similar to to the 'revenge' option, but it
<ElfStar> only triggers if a bot gets deopped, kicked or banned.
<ElfStar> autovoice Voice users with the +v flag when they join the
<ElfStar> channel?
<ElfStar> secret Prevent this channel from being listed on the botnet?
<ElfStar> shared Share channel-related user info for this channel?
<ElfStar> cycle Cycle the channel when it has no ops?
<ElfStar> dontkickops Do you want the bot not to be able to kick users who
<ElfStar> have the +o flag, letting them kick-flood for instance
<ElfStar> to protect the channel against clone attacks?
<ElfStar> inactive This prevents the bot from joining the channel (or
<ElfStar> makes it leave the channel if it is already there). It
<ElfStar> can be useful to make the bot leave a channel without
<ElfStar> losing its settings, channel-specific user flags,
<ElfStar> channel bans, and without affecting sharing.
<ElfStar> seen Respond to seen requests in the channel? The seen
<ElfStar> module must be loaded for this to work.
<ElfStar> nodesynch Allow non-ops to perform channel modes? This can stop
<ElfStar> the bot from fighting with services such as ChanServ, or
<ElfStar> from kicking IRCops when setting channel modes without
<ElfStar> having ops.
<ElfStar> The following are flood settings, they are set via ".chanset <channel>
<ElfStar> flood-type number:seconds", where number and second are integers
<ElfStar> indicating the number of times in how many seconds the flood will be
<ElfStar> triggered. Setting one of these to 0:0, 0:1, or 1:0 will deactivate the
<ElfStar> respective flood setting.
<ElfStar> flood-chan Set here how many channel messages in how many seconds
<ElfStar> from one host constitutes a flood. Setting this to 0 or 0:0
<ElfStar> disables text flood protection for the channel.
<ElfStar> flood-ctcp Set here how many channel ctcps in how many seconds from
<ElfStar> one host constitutes a flood. Setting this to 0 or 0:0
<ElfStar> disables ctcp flood protection for the channel.
<ElfStar> flood-join Set here how many joins in how many seconds from one
<ElfStar> host constitutes a flood. Setting this to 0 or 0:0 disables
<ElfStar> join flood protection for the channel.
<ElfStar> flood-kick Set here how many kicks in how many seconds from one
<ElfStar> host constitutes a flood. Setting this to 0 or 0:0 disables
<ElfStar> kick flood protection for the channel.
<ElfStar> flood-deop Set here how many deops in how many seconds from one
<ElfStar> host constitutes a flood. Setting this to 0 or 0:0 disables
<ElfStar> deop flood protection for the channel.
<ElfStar> flood-nick Set here how many nick changes in how many seconds from
<ElfStar> one host constitutes a flood. Setting this to 0 or 0:0
<ElfStar> disables nick flood protection for the channel.
<ElfStar> See also: +chan, -chan, chansave, chanset
<ElfStar> [00:14] #simple# help chinfo
<ElfStar> ### chinfo <user> [channel] [info-line/none]
<ElfStar> Sets the information line for a user. This line is shown via the /msg
<ElfStar> commands 'who' and 'whois'. If you have set greet on, it is also
<ElfStar> shown when the user joins the channel. If the info line begins with an '@',
<ElfStar> then it is "locked", and that user may no longer change it. If the channel
<ElfStar> name is omitted, the default info line is changed. If you specify 'none'
<ElfStar> as the info-line, it will be erased.
<ElfStar>
<ElfStar> See also: info
<ElfStar> [00:14] #simple# help chanload
<ElfStar> ### chanload
<ElfStar> Reloads the channel settings from the file defined by the "chanfile"
<ElfStar> setting. This allows you to return to a previous setting if you've really
<ElfStar> messed things up.
<ElfStar>
<ElfStar> See also: chansave, chanset, chaninfo, +chan, -chan
<ElfStar> [00:14] #simple# help chansave
<ElfStar> ### chansave
<ElfStar> Saves the channel settings to the file defined by the "chanfile"
<ElfStar> setting. This file is reloaded during rehash and restarting the bot.
<ElfStar>
<ElfStar> See also: chanload, chanset, chaninfo, +chan, -chan
<ElfStar> [00:14] #simple# help chanset
<ElfStar> ### chanset <channel> <settings>
<ElfStar> Allows you to change the channel settings (see 'chaninfo' for the
<ElfStar> settings) for one specific channel or all channels. Use '*' to to apply the
<ElfStar> change to all channels.
<ElfStar> Changes are used until the next rehash/chanload/restart, and are saved
<ElfStar> whenever the channel settings are saved.
<ElfStar>
<ElfStar> See also: chansave, chanload, chaninfo, +chan, -chan
<ElfStar> [00:14] #simple# help +chan
<ElfStar> ### +chan <channel> [options]
<ElfStar> Adds a channel to the bot's channel list. This channel is not permanent
<ElfStar> unless "chanfile" has been set in the config file. If it has, it is
<ElfStar> saved every time the userfile is saved, or by using '.chansave'. If
<ElfStar> options are specified, the channel will be configured with the options.
<ElfStar>
<ElfStar> See also: -chan, chanset, chaninfo
<ElfStar> [00:14] #simple# help -chan
<ElfStar> ### -chan <channel>
<ElfStar> This removes ALL information about a channel from the bot. It's not made
<ElfStar> permanent unless the channel file has been saved. If you remove a channel
<ElfStar> by accident, you can undo your changes with the 'chanload' command. Note
<ElfStar> that you will lose any other changed made since the last save.
<ElfStar>
<ElfStar> *** IMPORTANT ***
<ElfStar>
<ElfStar> This erases ALL information about the channel, including channel settings,
<ElfStar> bans, exempts, invites, and channel records for users -- EVERYTHING.
<ElfStar>
<ElfStar> DO NOT use it to have the bot temporarily leave a channel. This
<ElfStar> command is for abandoning a channel (e.g. the channel will have to be
<ElfStar> redefined and all user flags for that channel will have to be redone.
<ElfStar>
<ElfStar> Even if you don't have chanfile defined, it will still erase all the
<ElfStar> channel records for users on the next userfile save.
<ElfStar>
<ElfStar> See also: +chan, chansave, chanload, chanset, chaninfo