Eggdrop/Pastebin


 * 1) ! /home/stud/sstankov/eggdrop1.6.10
 * 2) ^- This should contain a fully qualified path to your eggdrop executable.
 * 3) $Id: eggdrop.advanced.conf,v 1.47 2002/03/23 17:27:51 wcc Exp $
 * 4) This is a sample eggdrop configuration file which includes many
 * 5) settings that can be used to configure your bot.
 * 6) PLEASE EDIT THIS FILE COMPLETELY! YOUR BOT WILL NOT FUNCTION PROPERLY IF
 * 7) YOU DO NOT CONFIGURE IT CORRECTLY! WE CAN NOT STRESS THIS ENOUGH!
 * 8) NOTE: Please choose your +n (owner) users carefully! They have COMPLETE
 * 9) access to your bot *AND* account! Only pick ones you trust!
 * 10) More options can be found in the files in doc/settings/.
 * 1) NOTE: Please choose your +n (owner) users carefully! They have COMPLETE
 * 2) access to your bot *AND* account! Only pick ones you trust!
 * 3) More options can be found in the files in doc/settings/.
 * 1) More options can be found in the files in doc/settings/.
 * 1) More options can be found in the files in doc/settings/.


 * 1) BASIC SETTINGS #####

set username "http://www.carnet.hr"
 * 1) This setting defines the username the bot uses on IRC. This setting has
 * 2) no effect if an ident daemon is running on your bot's machine.

set admin "Travelling Buddha "
 * 1) This setting defines which contact person should be shown in .status,
 * 2) /msg help, and other places. You really should include this information.

set network "CARNet"
 * 1) This setting is used only for info to share with others on your botnet.
 * 2) Set this to the IRC network your bot is connected to.

set timezone "CET"
 * 1) This setting defines the timezone is your bot in. It's used for internal
 * 2) routines as well as for logfile timestamping and scripting purposes.
 * 3) The timezone string specifies the name of the timezone and must be three
 * 4) or more alphabetic characters. For example, Central European Time(UTC+1)
 * 5) should be "CET".

set offset "1"
 * 1) The offset setting specifies the time value to be added to the local
 * 2) time to get Coordinated Universal Time (UTC aka GMT). The offset is
 * 3) positive if the local timezone is west of the Prime Meridian and
 * 4) negative if it is east. The value (in hours) must be between -23 and
 * 5) 23. For example, if the timezone is UTC+1, the offset is -1.

set my-hostname "racunarstvo.etfos.hr"
 * 1) If you're using virtual hosting (your machine has more than 1 IP), you
 * 2) may want to specify the particular IP to bind to. You can specify either
 * 3) by hostname or by IP. You may also want to set the hostname here if
 * 4) eggdrop has trouble detecting it when it starts up.
 * 1) set my-ip "99.99.0.0"


 * 1) If you want to have your eggdrop messages displayed in a language other
 * 2) than English, change this setting to match your preference. An alternative
 * 3) would be to set the environment variable EGG_LANG to that value.
 * 4) addlang "english"


 * 1) LOG FILES #####


 * 1) Eggdrop is capable of logging various things, from channel chatter to
 * 2) partyline commands and file transfers. Logfiles are normally
 * 3) kept for 24 hours. Afterwards, they will be renamed to "(logfile).yesterday".
 * 4) After 48 hours, they will be overwritten by the logfile of the next day.
 * 5) Events are logged by certain categories. This way, you can specify
 * 6) exactly what kind of events you want sent to various logfiles.
 * 7) The most common log file flags are:
 * 8)   m  private msgs/ctcps to the bot
 * 9)   k  kicks, bans, mode changes on the channel
 * 10)   j  joins, parts, netsplits on the channel
 * 11)   p  public chatter on the channel
 * 12)   s  server connects/disconnects/notices
 * 13)   b  information about bot linking and userfile sharing
 * 14)   c  commands people use (via msg or dcc)
 * 15)   x  file transfers and file-area commands
 * 16)      r  (if use-console-r enabled) EVERYTHING sent to the bot by the server
 * 17)   o  other: misc info, errors -- IMPORTANT STUFF
 * 18)   w  wallops: msgs between IRCops (be sure to set the bot +w in init-server)
 * 19) There are others, but you probably shouldn't log them, it'd be rather
 * 20) unethical. ;) There are also eight user-defined levels (1-8) which
 * 21) are used by Tcl scripts.
 * 22) Each logfile belongs to a certain channel. Events of type 'k', 'j', and 'p'
 * 23) are logged to whatever channel they happened on. Most other events are
 * 24) currently logged to every channel. You can make a logfile belong to all
 * 25) channels by assigning it to channel "*".
 * 1) Each logfile belongs to a certain channel. Events of type 'k', 'j', and 'p'
 * 2) are logged to whatever channel they happened on. Most other events are
 * 3) currently logged to every channel. You can make a logfile belong to all
 * 4) channels by assigning it to channel "*".

set max-logs 5
 * 1) This is the maximum number of logfiles allowed. This setting can be
 * 2) increased; however, don't decrease it.

set max-logsize 1024
 * 1) This is the maximum size of your logfiles. Set it to 0 to disable.
 * 2) This value is in kilobytes, so '550' would mean cycle logs when it
 * 3) reaches the size of 550 kilobytes.
 * 4) Note that this only works if you have keep-all-logs 0 (OFF).

set quick-logs 0
 * 1) This could be good if you have had problem with the logfile filling
 * 2) your quota/hard disk or if you log +p and publish it to the web and
 * 3) need more up-to-date info.
 * 4) Note that this setting might increase the CPU usage of your bot (on
 * 5) the other hand it will decrease your mem usage).

logfile mco * "logs/eggdrop.log"
 * 1) This creates a logfile named eggdrop.log containing private msgs/ctcps,
 * 2) commands, errors, and misc. info from any channel.


 * 1) This creates a logfile named lamest.log containing joins, parts,
 * 2) netsplits, kicks, bans, mode changes, and public chat on the
 * 3) channel #lamest.
 * 4) logfile jpk #lamest "logs/lamest.log"

set log-time 1
 * 1) Use this feature to timestamp entries in the log file.

set keep-all-logs 0
 * 1) If you want to keep your logfiles forever, turn this setting on. All
 * 2) logfiles will get suffix ".[day, 2 digits][month, 3 letters][year, 4 digits]".
 * 3) Note that your quota/hard-disk might be filled by this, so check your logfiles
 * 4) often and download them.

set logfile-suffix ".%d%b%Y"
 * 1) If keep-all-logs is 1, this setting will define the suffix of the logfiles.
 * 2) The default will result in a suffix like "04May2000". "%Y%m%d" will produce
 * 3) the often used yyyymmdd format. Read the strftime manpages for more options.
 * 4) NOTE: On systems which don't support strftime, the default format will
 * 5) be used _always_.

set switch-logfiles-at 300
 * 1) You can specifiy when eggdrop should switch logfiles and start fresh. You must
 * 2) use military time for this setting. 300 is the default, and describes 00:00.
 * 3) Note that a leading 0 will make Tcl think this is an octal value,
 * 4) something you probably don't want.

set quiet-save 0
 * 1) "Writing user file..." and "Writing channel file..." messages
 * 2) won't be logged anymore if this option is enabled.


 * 1) CONSOLE #####


 * 1) This is the default console mode. It uses the same event flags as the log
 * 2) files do. The console channel is automatically set to your "primary" channel,
 * 3) which is set in the modules section of the config file. Masters can change
 * 4) their console channel and modes with the '.console' command.

set console "mkcobxs"


 * 1) FILES AND DIRECTORIES #####

set userfile "mayday.user"
 * 1) Specify here the filename your userfile should be saved as.

set sort-users 0
 * 1) If you want your userfile to be sorted upon saving, enable this setting.
 * 2) This causes the bot to use bit more CPU when saving the usefile.

set help-path "help/"
 * 1) Specify here where eggdrop should look for help files.
 * 2) Don't modify this setting unless you know what you're doing!

set text-path "text/"
 * 1) Specify here where eggdrop should look for text files. This is
 * 2) used for certain Tcl and DCC commands.

set temp-path "/tmp"
 * 1) Set here a place to store temporary files.

set motd "text/motd"
 * 1) The MOTD (Message Of The day) is displayed when people dcc chat or telnet
 * 2) to the bot. Look at doc/text-substitutions.doc for options.

set telnet-banner "text/banner"
 * 1) This banner will be displayed on telnet connections.


 * 1) BOTNET/DCC/TELNET #####


 * 1) Settings in this section should be unimportant for you until you deal
 * 2) with botnets (multiple eggdrops connected together to maximize efficiency).
 * 3) You should read doc/BOTNET before modifying these settings.


 * 1) If you want to use a different nickname on the botnet than you use on
 * 2) IRC (i.e. if you're on an un-trusted botnet), un-comment the next line
 * 3) and set it to the nick you would like to use.
 * 4) set botnet-nick "LlamaBot"

listen 3456 all
 * 1) This opens a telnet port by which you and other bots can
 * 2) interact with the eggdrop by telneting in.
 * 3) There are more options for the listen command in doc/tcl-commands.doc.
 * 4) Note, if you are running more than one bot on the same machine, you will
 * 5) want to space the telnet ports at LEAST 5 apart. 10 is even better.
 * 6) Valid ports are typically anything between 1025 and 65535 assuming the
 * 7) port is not already in use.
 * 8) If you would like the bot to listen for users and bots in separate ports,
 * 9) use the following format.
 * 10) listen 3333 bots
 * 11) listen 4444 users
 * 12) If you wish to use only one port, use this format:
 * 1) listen 3333 bots
 * 2) listen 4444 users
 * 3) If you wish to use only one port, use this format:
 * 1) If you wish to use only one port, use this format:
 * 1) If you wish to use only one port, use this format:

set remote-boots 2
 * 1) This setting defines whether or not people can boot users on the eggdrop
 * 2) from other bots in your botnet. Valid settings are:
 * 3)    0 - allow *no* outside boots
 * 4)    1 - allow boots from sharebots
 * 5)    2 - allow any boots

set share-unlinks 1
 * 1) This setting prohibits remote bots from telling your eggdrop to unlink from
 * 2) share bots.

set protect-telnet 1
 * 1) This setting will drop telnet connections not matching a known host. It
 * 2) greatly improves protection from IRCOps, but makes it impossible for limbo
 * 3) bots to add hosts or have NEW as a valid login.

set dcc-sanitycheck 0
 * 1) This setting will make the bot ignore DCC chat requests which appear to
 * 2) have bogus information on the grounds that the user may have been trying
 * 3) to make the bot connect to somewhere that will get it into trouble, or
 * 4) that the user has a broken client (like mIRC tends to do), in which case
 * 5) the connect wouldn't work anyway.  It's suggested that you turn this on.

set ident-timeout 5
 * 1) This settings defines a time in seconds that the bot should wait before
 * 2) a dcc chat, telnet, or relay connection times out.

set require-p 0
 * 1) Define here whether or not a +o user still needs the +p flag to dcc the bot.

set stealth-telnets 1
 * 1) If you don't want eggdrop to identify itself as an eggdrop on a telnet connection,
 * 2) set this setting to 1. Eggdrop will display 'Nickname' instead.

set use-telnet-banner 0
 * 1) If you want eggdrop to display a banner when telneting in, set this setting
 * 2) to 1. The telnet banner is set by 'set telnet-banner'.

set connect-timeout 15
 * 1) This settings defines a time in seconds that the bot should wait before
 * 2) a dcc chat, telnet, or relay connection times out.

set dcc-flood-thr 3
 * 1) Specify here the number of lines to accept from a user on the partyline
 * 2) within 10 seconds before they are considered to be flooding and therefore
 * 3) get booted.

set telnet-flood 5:60
 * 1) Define here how many telnet connection attempts in how many seconds from
 * 2) the same host constitute a flood. The correct format is Attempts:Seconds.

set paranoid-telnet-flood 1
 * 1) If you want telnet-flood to apply even to +f users, set this setting to 1.

set resolve-timeout 15
 * 1) Set here the amount of seconds before giving up on hostname/address
 * 2) lookup (you might want to increase this if you are on a slow network).


 * 1) MORE ADVANCED SETTINGS #####

set ignore-time 15
 * 1) Set the time in minutes that temporary ignores should last.

set hourly-updates 00
 * 1) Define here what eggdrop considers 'hourly'. All calls to it, including such
 * 2) things as note notifying or userfile saving are affected by this. For example:
 * 3) set hourly-updates 15
 * 4) The bot will save its userfile 15 minutes past every hour.
 * 1) The bot will save its userfile 15 minutes past every hour.
 * 1) The bot will save its userfile 15 minutes past every hour.


 * 1) Un-comment the next line and set the list of owners of the bot.
 * 2) You NEED to change this setting.
 * 3) set owner "MrLame, MrsLame"

set notify-newusers "$owner"
 * 1) Who should a note be sent to when new users are learned?

set default-flags "hp"
 * 1) Enter the flags that all new users should get by default.
 * 2) See '.help whois' on the partyline for a list of flags and
 * 3) their descriptions.

unbind dcc n tcl *dcc:tcl unbind dcc n set *dcc:set
 * 1) Comment these two lines if you wish to enable the .tcl and .set commands.
 * 2) If you select your owners wisely, you should be okay enabling these.

set must-be-owner 1
 * 1) If you enable this setting, only permanent owners (owner setting) will be
 * 2) able to use .tcl and .set. Moreover, if you want only let permanent owners
 * 3) use .dump, then set this to 2.

set max-dcc 50
 * 1) Set here the maximum number of dcc connections you will allow. You can
 * 2) increase this later, but never decrease it.

set dupwait-timeout 5
 * 1) If your eggdrop rejects bots that actually have already disconnected from
 * 2) another hub, but the disconnect information has not yet spread over the
 * 3) botnet due to lag, use this setting. The bot will wait dupwait-timeout
 * 4) seconds before it checks again and then finally reject the bot.


 * 1) MODULES ##########


 * 1) Below are various settings for the modules available with eggdrop.
 * 2) PLEASE READ AND EDIT THEM CAREFULLY, even if you're an old hand at
 * 3) eggdrop, things change.

set mod-path "modules/"
 * 1) This path specifies the path were eggdrop should look for its modules.
 * 2) If you run the bot from the compilation directory, you will want to set
 * 3) this to "". If you use 'make install' (like all good kiddies do ;), this
 * 4) is a fine default. Otherwise, use your head :)


 * 1) DNS MODULE ####

loadmodule dns
 * 1) This module provides asynchronous dns support. This will avoid long
 * 2) periods where the bot just hangs there, waiting for a hostname to
 * 3) resolve, which will often let it timeout on all other connections.


 * 1) CHANNELS MODULE ####

loadmodule channels
 * 1) This module provides channel related support for the bot. Without it,
 * 2) you won't be able to make the bot join a channel or save channel
 * 3) specific userfile information.

set chanfile "mayday.chan"
 * 1) Enter here the filename where dynamic channel settings are stored.

set ban-time 120
 * 1) Set here how long temporary bans will last (in minutes). If you
 * 2) set this setting to 0, the bot will never remove them.

set exempt-time 60
 * 1) Set here how long temporary exempts will last (in minutes). If you
 * 2) set this setting to 0, the bot will never remove them. The bot will
 * 3) check the exempts every X minutes, but will not remove the exempt if
 * 4) a ban is set on the channel that matches that exempt. Once the ban is
 * 5) removed, then the exempt will be removed the next time the bot checks.
 * 6) Please note that this is an IRCnet feature.

set invite-time 60
 * 1) Set here how long temporary invites will last (in minutes). If you
 * 2) set this setting to 0, the bot will never remove them.
 * 3) The bot will check the invites every X minutes, but will not remove
 * 4) the invite if a channel is set to +i. Once the channel is -i then
 * 5) the invite will be removed the next time the bot checks.
 * 6) Please note that this is an IRCnet feature.

set force-expire 0
 * 1) Set this setting to 1 if you want your bot to expire bans/exempts/invites set
 * 2) by other opped bots on the channel.

set share-greet 0
 * 1) Set this setting to 1 if you want your bot to share user greets with other
 * 2) bots on the channel if sharing user data.

set use-info 1
 * 1) Set this setting to 1 if you want to allow users to store an info line.


 * 1) The following settings are used as default values when you .+chan #chan or .tcl
 * 2) channel add #chan. Look in the section below for explanation of every option.

set global-flood-chan 10:60 set global-flood-deop 3:10 set global-flood-kick 3:10 set global-flood-join 5:60 set global-flood-ctcp 3:60 set global-flood-nick 5:60 set global-aop-delay 5:30 set global-idle-kick 0 set global-chanmode "nt" set global-stopnethack-mode 0 set global-revenge-mode 1

set global-chanset { -autoop        -autovoice -bitch         +cycle +dontkickops   +dynamicbans +dynamicexempts +dynamicinvites -enforcebans   +greet -inactive      -nodesynch -protectfriends +protectops -revenge       -revengebot -secret        -seen +shared        +statuslog +userbans      +userexempts +userinvites   +portcheck +rawweather }


 * 1) Add each static channel you want your bot to sit in using this command.
 * 2) There are many different possible settings you can insert into this
 * 3) command, which are explained below.

channel add #Osijek { chanmode "+nt-likm" idle-kick 0 stopnethack-mode 0 revenge-mode 1 aop-delay 5:30 flood-chan 10:60 flood-deop 3:10 flood-kick 3:10 flood-join 5:60 flood-ctcp 3:60 flood-nick 5:60 }


 * 1) chanmode +/-
 * 2)    This setting makes the bot enforce channel modes. It will always add
 * 3)    the + and remove the - modes.
 * 4) idle-kick 0
 * 5)    This setting will make the bot check every minute for idle
 * 6)    users. Set this to 0 to disable idle check.
 * 7) stopnethack-mode 0
 * 8)    This setting will make the bot de-op anyone who enters the channel
 * 9)    with serverops. There're seven different modes for this settings:
 * 10)       0 turn off,
 * 11)      1 isoptest (allow serverop if registered op)
 * 12)       2 wasoptest (allow serverop if op before split)
 * 13)       3 allow serverop if isop or wasop
 * 14)      4 allow serverop if isop and wasop.
 * 15)      5 If the channel is -bitch, see stopnethack-mode 3
 * 16)        If the channel is +bitch, see stopnethack-mode 1
 * 17)      6 If the channel is -bitch, see stopnethack-mode 2
 * 18)        If the channel is +bitch, see stopnethack-mode 4
 * 19) revenge-mode 1
 * 20)   This settings defines how the bot should punish bad users when
 * 21)   revenging. There are four possible settings:
 * 22)     0 Deop the user.
 * 23)     1 Deop the user and give them the +d flag for the channel.
 * 24)     2 Deop the user, give them the +d flag for the channel, and kick them.
 * 25)     3 Deop the user, give them the +d flag for the channel, kick, and ban them.
 * 26) aop-delay (minimum:maximum)
 * 27) This is used for autoop and autovoice. If an op or voice joins a channel
 * 28) while another op or voice is pending, the bot will attempt to put both
 * 29) modes on one line.
 * 30)   aop-delay 0   No delay is used.
 * 31)   aop-delay X   An X second delay is used.
 * 32)   aop-delay X:Y A random delay between X and Y is used.
 * 33) need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
 * 34)    This setting will make the bot run the script enclosed in brackets
 * 35)    if it does not have ops. This must be shorter than 120 characters.
 * 36)    If you use scripts like getops.tcl or botnetop.tcl, you don't need
 * 37)    to set this setting.
 * 38) need-invite { putserv "PRIVMSG #lamest :let me in!" }
 * 39)    This setting will make the bot run the script enclosed in brackets
 * 40)    if it needs an invite to the channel. This must be shorter than 120
 * 41)    characters. If you use scripts like getops.tcl or botnetop.tcl, you
 * 42)    don't need to set this setting.
 * 43) need-key { putserv "PRIVMSG #lamest :let me in!" }
 * 44)    This setting will make the bot run the script enclosed in brackets
 * 45)    if it needs the key to the channel. This must be shorter than 120
 * 46)    characters. If you use scripts like getops.tcl or botnetop.tcl, you
 * 47)    don't need to set this setting
 * 48) need-unban { putserv "PRIVMSG #lamest :let me in!" }
 * 49)    This setting will make the bot run the script enclosed in brackets
 * 50)    if it needs to be unbanned on the channel. This must be shorter than
 * 51)    120 characters. If you use scripts like getops.tcl or botnetop.tcl,
 * 52)    you don't need to set this setting
 * 53) need-limit { putserv "PRIVMSG #lamest :let me in!" }
 * 54)    This setting will make the bot run the script enclosed in brackets
 * 55)    if it needs the limit to be raised on the channel. This must be
 * 56)    shorter than 120 characters. If you use scripts like getops.tcl or
 * 57)    botnetop.tcl, you don't need to set this setting
 * 58) flood-chan 10:60
 * 59)    Set here how many channel messages in how many seconds from one
 * 60)    host constitutes a flood. Setting this to 0 or 0:0 disables
 * 61)    flood protection for the channel.
 * 62) flood-deop 3:10
 * 63)    Set here how many deops in how many seconds from one host constitutes
 * 64)    a flood. Setting this to 0 or 0:0 disables deop flood protection for
 * 65)    the channel.
 * 66) flood-kick 3:10
 * 67)    Set here how many kicks in how many seconds from one host constitutes
 * 68)    a flood. Setting this to 0 or 0:0 disables kick flood protection for
 * 69)    the channel.
 * 70) flood-join 5:60
 * 71)    Set here how many joins in how many seconds from one host constitutes
 * 72)    a flood. Setting this to 0 or 0:0 disables join flood protection for
 * 73)    the channel.
 * 74) flood-ctcp 3:60
 * 75)    Set here how many channel ctcps in how many seconds from one host
 * 76)    constitutes a flood. Setting this to 0 or 0:0 disables ctcp flood
 * 77)    protection for the channel.
 * 78) flood-nick 5:60
 * 79)    Set here how many nick changes in how many seconds from one host
 * 80)    constitutes a flood. Setting this to 0 or 0:0 disables nick flood
 * 81)    protection for the channel.
 * 1) flood-join 5:60
 * 2)    Set here how many joins in how many seconds from one host constitutes
 * 3)    a flood. Setting this to 0 or 0:0 disables join flood protection for
 * 4)    the channel.
 * 5) flood-ctcp 3:60
 * 6)    Set here how many channel ctcps in how many seconds from one host
 * 7)    constitutes a flood. Setting this to 0 or 0:0 disables ctcp flood
 * 8)    protection for the channel.
 * 9) flood-nick 5:60
 * 10)    Set here how many nick changes in how many seconds from one host
 * 11)    constitutes a flood. Setting this to 0 or 0:0 disables nick flood
 * 12)    protection for the channel.
 * 1)    constitutes a flood. Setting this to 0 or 0:0 disables nick flood
 * 2)    protection for the channel.


 * 1) There are many different options for channels which you can
 * 2) define. They can be enabled or disabled by a plus or minus
 * 3) in front of them.
 * 4) A complete list of all available channel settings:
 * 5) enforcebans
 * 6)    When a ban is set, kick people who are on the channel and match
 * 7)    the ban?
 * 8) dynamicbans
 * 9)    Only activate bans on the channel when necessary? This keeps
 * 10)    the channel's ban list from getting excessively long. The bot
 * 11)    still remembers every ban, but it only activates a ban on the
 * 12)    channel when it sees someone join who matches that ban.
 * 13) userbans
 * 14)    Allow bans to be made by users directly? If turned off, the bot
 * 15)    will require all bans to be made through the bot's console.
 * 16) dynamicexempts
 * 17)    Only activate exempts on the channel when necessary? This keeps
 * 18)    the channel's exempt list from getting excessively long. The bot
 * 19)    still remembers every exempt, but it only activates a exempt on
 * 20)    the channel when it sees a ban set that matches the exempt. The
 * 21)    exempt remains active on the channel for as long as the ban is
 * 22)    still active.
 * 23) userexempts
 * 24)    Allow exempts to be made by users directly? If turned off, the
 * 25)    bot will require all exempts to be made through the bot's console.
 * 26) dynamicinvites
 * 27)    Only activate invites on the channel when necessary? This keeps
 * 28)    the channel's invite list from getting excessively long. The bot
 * 29)    still remembers every invite, but the invites are only activated
 * 30)    when the channel is set to invite only and a user joins after
 * 31)    requesting an invite. Once set, the invite remains until the
 * 32)    channel goes to -i.
 * 33) userinvites
 * 34)    Allow invites to be made by users directly? If turned off, the
 * 35)    bot will require all invites to be made through the bot's console.
 * 36) autoop
 * 37)    Op users with the +o flag as soon as they join the channel?
 * 38)    This is insecure and not recommended.
 * 39) bitch
 * 40)    Only let users with +o) flag be opped on the channel?
 * 41) greet
 * 42)    Say a user's info line when they join the channel?
 * 43) protectops
 * 44)    Re-op a user with the +o flag if they get deopped?
 * 45) protectfriends
 * 46)    Re-op a user with the +f flag if they get deopped?
 * 47) statuslog
 * 48)    Log the channel status line every 5 minutes? This shows the bot's
 * 49)    status on the channel (op, voice, etc.), The channel's modes, and
 * 50)    the number of +m/+o/+v/+n/+b/+e/+I users on the channel. A sample
 * 51)    status line follows:
 * 52)    [01:40] @#lamest (+istn) : [m/1 o/1 v/4 n/7 b/1 e/5 I/7]
 * 53) revenge
 * 54)    Remember people who deop/kick/ban the bot, valid ops, or friends
 * 55)    and punish them? Users with the +f flag are exempt from revenge.
 * 56) revengebot
 * 57)    This is similar to to the 'revenge' option, but it only triggers
 * 58)    if a bot gets deopped, kicked or banned.
 * 59) autovoice
 * 60)    Voice users with the +v flag when they join the channel?
 * 61) secret
 * 62)    Prevent this channel from being listed on the botnet?
 * 63) shared
 * 64)    Share channel-related user info for this channel?
 * 65) cycle
 * 66)    Cycle the channel when it has no ops?
 * 67) dontkickops
 * 68)    Do you want the bot not to be able to kick users who have the +o
 * 69)    flag, letting them kick-flood for instance to protect the channel
 * 70)    against clone attacks.
 * 71) inactive
 * 72)    This prevents the bot from joining the channel (or makes it leave
 * 73)    the channel if it is already there). It can be useful to make the
 * 74)    bot leave a channel without losing its settings, channel-specific
 * 75)    user flags, channel bans, and without affecting sharing.
 * 76) seen
 * 77)    Respond to seen requests in the channel?  The seen module must be
 * 78)    loaded for this to work.
 * 79) nodesynch
 * 80)    Allow non-ops to perform channel modes? This can stop the bot from
 * 81)    fighting with services such as ChanServ, or from kicking IRCops when
 * 82)    setting channel modes without having ops.
 * 1) shared
 * 2)    Share channel-related user info for this channel?
 * 3) cycle
 * 4)    Cycle the channel when it has no ops?
 * 5) dontkickops
 * 6)    Do you want the bot not to be able to kick users who have the +o
 * 7)    flag, letting them kick-flood for instance to protect the channel
 * 8)    against clone attacks.
 * 9) inactive
 * 10)    This prevents the bot from joining the channel (or makes it leave
 * 11)    the channel if it is already there). It can be useful to make the
 * 12)    bot leave a channel without losing its settings, channel-specific
 * 13)    user flags, channel bans, and without affecting sharing.
 * 14) seen
 * 15)    Respond to seen requests in the channel?  The seen module must be
 * 16)    loaded for this to work.
 * 17) nodesynch
 * 18)    Allow non-ops to perform channel modes? This can stop the bot from
 * 19)    fighting with services such as ChanServ, or from kicking IRCops when
 * 20)    setting channel modes without having ops.
 * 1) nodesynch
 * 2)    Allow non-ops to perform channel modes? This can stop the bot from
 * 3)    fighting with services such as ChanServ, or from kicking IRCops when
 * 4)    setting channel modes without having ops.
 * 1)    setting channel modes without having ops.

channel set #Osijek -clearbans channel set #Osijek +enforcebans channel set #Osijek +dynamicbans channel set #Osijek +userbans channel set #Osijek +dynamicexempts channel set #Osijek +userexempts channel set #Osijek +dynamicinvites channel set #Osijek +userinvites channel set #Osijek +greet channel set #Osijek +protectops channel set #Osijek +protectfriends channel set #Osijek -statuslog channel set #Osijek +revenge channel set #Osijek +revengebot channel set #Osijek +autovoice channel set #Osijek +cycle channel set #Osijek +dontkickops channel set #Osijek -autoop channel set #Osijek -bitch channel set #Osijek -secret channel set #Osijek -shared


 * 1) Here is a shorter example:
 * 2)  channel add #botcentral {
 * 3)    chanmode "+mntisl 1"
 * 4)    idle-kick 1
 * }
 * 1)  channel set #botcentral +bitch +enforcebans -greet +revenge
 * 1)  channel set #botcentral +bitch +enforcebans -greet +revenge


 * 1) SERVER MODULE ####

loadmodule server
 * 1) This module provides the core server support. You have to load this
 * 2) if you want your bot to come on IRC. Not loading this is equivalent
 * 3) to the old NO_IRC define.

set net-type 5
 * 1) What is your network?
 * 2)   0 = EFnet (non +e/+I hybrid)
 * 3)   1 = IRCnet
 * 4)   2 = Undernet
 * 5)   3 = DALnet
 * 6)   4 = EFnet +e/+I hybrid
 * 7)   5 = Others


 * 1) Set the nick the bot uses on IRC, and on the botnet
 * 2) unless you specify a separate botnet-nick, here.

set nick "CARNet"


 * 1) Set the alternative nick which the bot uses on IRC if the nick specified
 * 2) by 'set nick' is unavailable. All '?' characters will be replaced by random
 * 3) numbers.

set altnick "_CARNet_"

set realname "Croatian Academic and Research Network"
 * 1) Set what should be displayed in the real-name field for the bot on IRC.

set init-server { putserv "MODE $botnick +i-ws" }
 * 1) Set here a script to run (if any) when first connecting to a server.
 * 2) This is limited to 120 characters.

set default-port 6667
 * 1) Set the default port which should be used if none is specified with
 * 2) '.jump' or in 'set servers'.

set servers { irc.idolnet.org:6667 irc.fpz.hr:6667 irc.ffzg.hr:6667 }
 * 1) This is the bot's server list. The bot will start at the first server listed,
 * 2) and cycle through them whenever it gets disconnected. You need to change these
 * 3) servers to YOUR network's servers.
 * 4) The format is:
 * 5)   server[:port[:password]]
 * 6) Both the port and password fields are optional; however, if you want to set a
 * 7) password you must also set a port. If a port isn't specified it will default to
 * 8) your default-port setting.
 * 1) password you must also set a port. If a port isn't specified it will default to
 * 2) your default-port setting.

set keep-nick 1
 * 1) This setting makes the bot try to get his original nickname back if its
 * 2) primary nickname is already in use.

set strict-host 0
 * 1) Set this to 1 if you don't want your the bot to strip a leading '~'
 * 2) on user@hosts.

set quiet-reject 1
 * 1) This setting makes the bot squelch the error message when rejecting a DCC
 * 2) CHAT or SEND. Normally it tells the DCC user that the CHAT or SEND has
 * 3) been rejected because they don't have access.
 * 4) Please note, sometimes IRC server operators detect bots that way.

set lowercase-ctcp 0
 * 1) If you want your bot to answer lower case ctcp requests (non rfc-
 * 2) compliant), set this setting to 1. mIRC will do this, most other
 * 3) clients will not.

set answer-ctcp 3
 * 1) Set how many ctcps should be answered at once.

set flood-msg 5:60
 * 1) Set here how many msgs in how many seconds from one host constitutes
 * 2) a flood. If you set this to 0:0, msg flood protection will be disabled.

set flood-ctcp 3:60
 * 1) Set here how many ctcps in how many seconds from one host constitutes
 * 2) a flood. If you set this to 0:0, ctcp flood protection will be disabled.

set never-give-up 1
 * 1) This settings makes the bot cycle forever through the server list until
 * 2) it successfully connects to one.

set strict-servernames 0
 * 1) Often, IRC servers call themselves a name other than their actual
 * 2) hostname. If you want eggdrop to replace your entry in the config
 * 3) file with this name, set this to 1. If you set this setting to 0,
 * 4) eggdrop will keep a separate list of what IRC servers call themselves.

set server-cycle-wait 60
 * 1) This setting defines how long eggdrop should wait before moving from one
 * 2) server to another on disconnect. If you set 0 here, eggdrop will not wait
 * 3) at all and will connect instantly. Setting this too low could result in
 * 4) your bot being K:Lined.

set server-timeout 60
 * 1) Set here how long eggdrop should wait for a response when connecting to a
 * 2) server before giving up and moving on to next server.

set servlimit 0
 * 1) If the number of servers on the net gets below this number, the bot
 * 2) will jump to a new server (it will assume it's on the losing end of
 * 3) a netsplit). Set this to 0 to turn off. If your bot is running on
 * 4) any major IRC network, this should probably be turned off.

set check-stoned 1
 * 1) Set this to 1 if eggdrop should check for stoned servers? (where the
 * 2) server connection has died, but eggdrop hasn't been notified yet).

set use-console-r 0
 * 1) This setting allows you the logging of all information received from the
 * 2) server via console mode 'r'.
 * 3) NOTE: This is a large security hole, allowing people to see user passwords.
 * 4) This is now restricted to +n users only. Please choose your owners with
 * 5) care.

set debug-output 0
 * 1) This setting allows you the logging of all information sent to the server
 * 2) via console mode 'v'.
 * 3) NOTE: This is a large security hole, allowing people to see passwords.
 * 4) This is now restricted to +n users only. Please choose your owners with
 * 5) care.

set serverror-quit 1
 * 1) If you want your bot to exit the server if it receives an ERROR message,
 * 2) set this to 1.

set max-queue-msg 300
 * 1) Set here the maximum number of lines to queue to the server. If you're
 * 2) going to dump large chunks of text to people over IRC, you will probably
 * 3) want to raise this. 300 is fine for most people though.

set trigger-on-ignore 0
 * 1) If you want eggdrop to trigger binds for ignored users, set this to 1.

set double-mode 0
 * 1) Allow identical messages in the mode queue?

set double-server 0
 * 1) Allow identical messages in the server queue?

set double-help 0
 * 1) Allow identical messages in the help queue?

set optimize-kicks 1
 * 1) This optimizes the kick queue. It also traces nick changes and parts in
 * 2) the channel and changes the kick queue accordingly. There are three
 * 3) different options for this setting:
 * 4)   0 = Turn it off.
 * 5)   1 = Optimize the kick queue by summarizing kicks.
 * 6)   2 = Trace nick changes and parts on the channel and change the queue
 * 7)       accordingly. For example, bot will not try to kick users who have
 * 8)       already parted the channel.
 * 9) ATTENTION: Setting 2 is very CPU intensive.


 * 1) SERVER MODULE - OTHER NETWORKS (net-type 5) ###


 * 1) This settings defines how umode +r is understood by eggdrop. Some
 * 2) networks use +r to indicate a restricted connection. If this is your
 * 3) case, and you want your bot to leave restricted servers and jump to
 * 4) the next server on its list, then set it to 1.
 * 5) set check-mode-r 1


 * 1) This setting allows you to specify the maximum nick-length supported by
 * 2) your network. The default setting is 9. The maximum supported length by
 * 3) eggdrop is 32.
 * 4) set nick-len 9


 * 1) CTCP MODULE ####

loadmodule ctcp
 * 1) This module provides the normal ctcp replies that you'd expect.
 * 2) Without it loaded, CTCP CHAT will not work. The server module
 * 3) is required for this module to function.

set ctcp-mode 0
 * 1) Set here how the ctcp module should answer ctcps. There are 3 possible
 * 2) operating modes:
 * 3)   0: Normal behavior is used.
 * 4)   1: The bot ignores all ctcps, except for CHAT and PING requests
 * 5)      by users with the +o flag.
 * 6)   2: Normal behavior is used, however the bot will not answer more
 * 7)      than X ctcps in Y seconds (defined by 'set flood-ctcp').

set ctcp-version "Level Seven Digital"
 * 1) There are also several variables to help make your bot less noticeable.
 * 2) They are: ctcp-version, ctcp-finger, and ctcp-userinfo. You can use set to set
 * 3) them to values you'd like.
 * 4) response for CTCP VERSION  (change this to make your bot hard to find)

set ctcp-finger "Level Seven Digital"
 * 1) response for CTCP FINGER  (change this to make your bot hard to find)

set ctcp-userinfo "Level Seven Digital"
 * 1) response for CTCP USERINFO  (change this to make your bot hard to find)


 * 1) IRC MODULE ####

loadmodule irc
 * 1) This module provides basic IRC support for your bot. You have to
 * 2) load this if you want your bot to come on IRC. The server and channels
 * 3) modules must be loaded for this module to function.

set bounce-bans 1
 * 1) Set this to 1 if you want to bounce all server bans.

set bounce-modes 0
 * 1) Set this to 1 if you want to bounce all server modes.

set max-bans 20
 * 1) Set here the maximum number of bans you want the bot to set on a channel.
 * 2) Eggdrop will not place any more bans if this limit is reached. Undernet
 * 3) and IRCnet currently allow 30 bans, EFnet allows 20, and DALnet allows 100.

set max-modes 30
 * 1) There is a global limit for +b/+e/+I modes. This limit is currently set to
 * 2) 30 on IRCu 2.10 servers.

set kick-fun 0
 * 1) Set this to 1 if you want the bot to kick for control character/ctcp
 * 2) avalanches to a channel. Remember that if it does, it won't ban them.
 * 3) This can start kick floods.

set ban-fun 0
 * 1) Set this to 1 if you want the bot to ban for control character/ctcp
 * 2) avalanches to a channel. This can prevent kick floods, but it also can
 * 3) fill the banlist.

set learn-users 1
 * 1) If you want people to be able to add themselves to the bot's userlist
 * 2) with the default userflags (defined above in the config file) via the
 * 3) 'hello' msg command, set this to 1.

set wait-split 600
 * 1) Set here the time (in seconds) to wait for someone to return from
 * 2) a netsplit (i.e. wasop will expire afterwards). Set this to 1500
 * 3) on IRCnet since its nick delay stops after 30 minutes.

set wait-info 180
 * 1) Set here the time (in seconds) that someone must have been off-channel
 * 2) before re-displaying their info line.

set mode-buf-length 200
 * 1) Set this to the maximum number of bytes to send in the arguments
 * 2) of modes sent to the server. Most servers default this to 200.


 * 1) Many IRCops find bots by seeing if they reply to 'hello' in a msg.
 * 2) You can change this to another word by un-commenting the following
 * 3) two lines and changing "myword" to the word wish to use instead of
 * 4) 'hello'. It must be a single word.
 * 5) unbind msg - hello *msg:hello
 * 6) bind msg - myword *msg:hello

unbind msg - ident *msg:ident unbind msg - addhost *msg:addhost
 * 1) Many takeover attempts occur due to lame users blindly /msg ident'ing to
 * 2) the bot and attempting to guess passwords. We now unbind this command by
 * 3) default to discourage them. You can enable this command by un-commenting
 * 4) the following two lines.

set no-chanrec-info 0
 * 1) If you are so lame you want the bot to display peoples info lines, even
 * 2) when you are too lazy to add their chanrecs to a channel, set this to 1.
 * 3) *NOTE* This means *every* user with an info line will have their info
 * 4) line displayed on EVERY channel they join (provided they have been gone
 * 5) longer than wait-info).


 * 1) IRC MODULE - IRCnet SPECIFIC FEATURES (net-type 1) ###


 * 1) Attention: Use these settings *only* if you set 'net-type' to 1!

set bounce-exempts 0
 * 1) Set this to 1 if you want to bounce all server exemptions (+e modes).

set bounce-invites 0
 * 1) Set this to 1 if you want to bounce all server invitations (+I modes).

set max-exempts 20
 * 1) Set here the maximum number of exempts you want eggdrop to set
 * 2) on a channel. Eggdrop will not place any more exempts if this
 * 3) limit is reached.

set max-invites 20
 * 1) Set here the maximum number of invites you want eggdrop  to set
 * 2) on a channel. Eggdrop will not place any more invites if this
 * 3) limit is reached.


 * 1) The following settings should be left commented unless the default values
 * 2) are being overridden. By default, exempts and invites are on for IRCnet,
 * 3) but off for all other large networks. This behavior can be modified with
 * 4) the following 2 flags. If your network doesn't support +e/+I modes then you
 * 5) will be unable to use these features.
 * 6) Do you want to enable exempts?
 * 7) set use-exempts 0
 * 1) set use-exempts 0


 * 1) Do you want to use invites?
 * 2) set use-invites 0

set prevent-mixing 1
 * 1) At the moment, the current IRCnet IRCd version (2.10) doesn't support the mixing
 * 2) of b,o and v modes with e and I modes. This might be changed in the future, so
 * 3) use 1 at the moment for this setting.


 * 1) IRC MODULE - OTHER NETWORKS (net-type 5) ###


 * 1) Attention: Use these settings *only* if you set 'net-type' to 5!


 * 1) If your network supports more users per kick command then 1, you can
 * 2) change this behavior here. Set this to the number of users to kick at
 * 3) once, or set this to 0 for all at once.
 * 4) set kick-method 1


 * 1) Some networks allow you to stack lots of channel modes into one line.
 * 2) They're all guaranteed to support at least 3, so that's the default.
 * 3) If you know your network supports more, you may want to adjust this.
 * 4) set modes-per-line 3


 * 1) Some networks don't include the +l limit and +k or -k key modes
 * 2) in the modes-per-line (see above) limitation. Set include-lk to 0 for
 * 3) these networks.
 * 4) set include-lk 1


 * 1) If your network doesn't use rfc 1459 compliant string matching routines,
 * 2) set this to 0.
 * 3) set rfc-compliant 1


 * 1) TRANSFER MODULE ####


 * 1) The transfer module provides dcc send/get support and userfile transfer
 * 2) support for userfile sharing. Un-comment the next line to load it if you
 * 3) need this functionality.
 * 4) loadmodule transfer

set max-dloads 3
 * 1) Set here the maximum number of simultaneous downloads to allow for
 * 2) each user.

set dcc-block 1024
 * 1) Set here the block size for dcc transfers. ircII uses 512 bytes,
 * 2) but admits that may be too small. 1024 is standard these days.
 * 3) Set this to 0 to use turbo-dcc (recommended).

set copy-to-tmp 1
 * 1) Enable this setting if you want to copy files into the /tmp directory
 * 2) before sending them. This is useful on most systems for file stability,
 * 3) but if your directories are NFS mounted, it's a pain, and you'll want
 * 4) to set this to 0. If you are low on disk space, you may also want to
 * 5) set this to 0.

set xfer-timeout 30
 * 1) Set here the time (in seconds) to wait before an inactive transfer
 * 2) times out.


 * 1) SHARE MODULE ####


 * 1) This module provides userfile sharing support between two directly
 * 2) linked bots. The transfer and channels modules are required for this
 * 3) module to correctly function. Un-comment the following line to load
 * 4) the share module.
 * 5) loadmodule share


 * 1) Settings in this section must be un-commented before setting.


 * 1) When sharing user lists, DON'T ACCEPT global flag changes from other bots?
 * 2) NOTE: The bot will still send changes made on the bot, it just won't accept
 * 3) any global flag changes from other bots.
 * 4) set private-global 0


 * 1) When sharing user lists, if private-global isn't set, which global flag
 * 2) changes from other bots should be ignored?
 * 3) set private-globals "mnot"


 * 1) When sharing user lists, don't accept ANY userfile changes from other
 * 2) bots? Paranoid people should use this feature on their hub bot. This
 * 3) will force all userlist changes to be made via the hub.
 * 4) set private-user 0


 * 1) This setting makes the bot discard its own bot records in favor of
 * 2) the ones sent by the hub.
 * 3) NOTE: No passwords or botflags are shared, only ports and
 * 4) address are added to sharing procedure. This only works with hubs that
 * 5) are v1.5.1 or higher.
 * 6) set override-bots 0


 * 1) COMPRESS MODULE ####


 * 1) This module provides provides support for file compression. This allows the
 * 2) bot to transfer compressed user files and therefore save a significant amount
 * 3) of bandwidth. The share module must be loaded to load this module. Un-comment
 * 4) the following line to the compress module.
 * 5) loadmodule compress

set share-compressed 1
 * 1) Allow compressed sending of user files? The user files are
 * 2) compressed with the compression level defined in `compress-level'.


 * 1) This is the default compression level used.
 * 2) set compress-level 9


 * 1) FILESYSTEM MODULE ####


 * 1) This module provides an area within the bot where users can store
 * 2) files. With this module, the bot is usable as a file server. The
 * 3) transfer module is required for this module to function. Un-comment
 * 4) the following line to load the filesys module.
 * 5) loadmodule filesys

set files-path /home/stud/sstankov/eggdrop1.6.10/filesys"
 * 1) Set here the 'root' directory for the file system.

set incoming-path /home/stud/sstankov/eggdrop1.6.10/filesys/incoming"
 * 1) If you want to allow uploads, set this to the directory uploads
 * 2) should be put into. Set this to "" if you don't want people to
 * 3) upload files to your bot.

set upload-to-pwd 0
 * 1) If you don't want to have a central incoming directory, but instead
 * 2) want uploads to go to the current directory that a user is in, set
 * 3) this setting to 1.

set filedb-path ""
 * 1) Eggdrop creates a '.filedb' file in each subdirectory of your file area
 * 2) to keep track of its own file system information. If you can't do that (for
 * 3) example, if the dcc path isn't owned by you, or you just don't want it to do
 * 4) that) specify a path here where you'd like all of the database files to be
 * 5) stored instead.

set max-file-users 20
 * 1) Set here the maximum number of people that can be in the file area at once.
 * 2) Setting this to 0 makes it effectively infinite.

set max-filesize 1024
 * 1) Set here the maximum allowable file size that will be received (in kb).
 * 2) Setting this to 0 makes it effectively infinite.


 * 1) NOTES MODULE ####

loadmodule notes
 * 1) This module provides support for storing of notes for users from each
 * 2) other. Note sending between currently online users is supported in the
 * 3) core, this is only for storing the notes for later retrieval.

set notefile "mayday.notes"
 * 1) Set here the filename where private notes between users are stored.

set max-notes 50
 * 1) Set here the maximum number of notes to allow to be stored for
 * 2) each user (to prevent flooding).

set note-life 60
 * 1) Set here how long (in days) to store notes before expiring them.

set allow-fwd 0
 * 1) Set this to 1 if you want to allow users to specify a forwarding
 * 2) address for forwarding notes to another account on another bot.

set notify-users 1
 * 1) Set this to 1 if you want the bot to let people know hourly if they
 * 2) have any notes.

set notify-onjoin 1
 * 1) Set this to 1 if you want the bot to let people know on join if they
 * 2) have any notes.


 * 1) Comment out this next line. Otherwise, your bot won't start.
 * 2) die "You didn't edit your config file like you were told, did you?"


 * 1) CONSOLE MODULE ####

loadmodule console
 * 1) This module provides storage of console settings when you exit the
 * 2) bot or type .store on the partyline.

set console-autosave 1
 * 1) Save users console settings automatically? Otherwise, they have
 * 2) to use the .store command.

set force-channel 0
 * 1) If a user doesn't have any console settings saved, which channel
 * 2) do you want them automatically put on?

set info-party 0
 * 1) Enable this setting if a user's global info line should be displayed
 * 2) when they join a botnet channel.


 * 1) SEEN MODULE ####

loadmodule seen
 * 1) This module provides very basic seen commands via msg, on channel or via dcc.
 * 2) This module works only for users in the bot's userlist. If you are looking for
 * 3) a better and more advanced seen module, try the gseen module by G'Quann. You
 * 4) can find it at http://www.visions-of-fantasy.de/gseen.mod/.


 * 1) BLOWFISH MODULE ####

loadmodule blowfish
 * 1) IF YOU DON'T READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
 * 2) Eggdrop encrypts its userfile, so users can have secure passwords.
 * 3) Please note that when you change your encryption method later (i.e.
 * 4) using other modules like a md5 module), you can't use your current
 * 5) userfile anymore. Eggdrop will not start without an encryption module.


 * 1) ASSOC MODULE ####


 * 1) This module provides assoc support, i.e. naming channels on the botnet.
 * 2) You can load it by un-commenting the following line.
 * 3) loadmodule assoc


 * 1) WIRE MODULE ####


 * 1) This module provides all the standard .wire commands via dcc. It is an
 * 2) encrypted partyline communication tool, compatible with wire.tcl. An
 * 3) encryption module must be loaded to use this module. Un-comment the
 * 4) following line to load the wire module.
 * 5) loadmodule wire


 * 1) UPTIME MODULE ####

loadmodule uptime
 * 1) This module reports uptime statistics to http://uptime.eggheads.org.
 * 2) Go look and see what your uptime is! It takes about 9 hours to show up,
 * 3) so if your bot isn't listed, try again later.
 * 4) Information sent to the server includes the bot's uptime, botnet-nick,
 * 5) server, version, and IP address. This information is stored in a temporary
 * 6) logfile for debugging purposes only. The only publicly available information
 * 7) will be the bot's botnet-nick, version and uptime. If you do not wish for this
 * 8) information to be sent, comment out the following line.
 * 1) information to be sent, comment out the following line.


 * 1) SCRIPTS #####


 * 1) This is a good place to load scripts to use with your bot.


 * 1) This line loads script.tcl from the scripts directory inside your eggdrop's
 * 2) directory. All scripts should be put there, although you can place them where
 * 3) you like as long as you can supply a fully qualified path to them.
 * 4) source scripts/script.tcl
 * 1) source scripts/script.tcl

source scripts/alltools.tcl source scripts/action.fix.tcl source scripts/8ball.tcl source scripts/PortCheck2.2.tcl
 * 1) source scripts/egghttp.tcl
 * 1) source scripts/rawweather.tcl

source scripts/compat.tcl
 * 1) Use this script for Tcl and eggdrop downwards compatibility.
 * 2) NOTE: This can also cause problems with some newer scripts.

source scripts/userinfo.tcl loadhelp userinfo.help
 * 1) This script provides many useful informational functions, like setting
 * 2) users' URLs, e-mail address, ICQ numbers, etc. You can modify it to add
 * 3) extra entries