*** lamestbot.orig	Tue Dec 31 04:35:25 1996
--- lamestbot	Sat Feb 22 22:29:42 1997
***************
*** 1,10 ****
! #!/path/to/eggdrop
  #
  # This is a sample configuration file for your bot.  You will definitely
  # want to edit this, to set up your bot.  Right now it creates a bot called
! # "LamestBot" which sits on channel #lamest.
  #
  # The most vital things are listed at the top of this file, with the more
  # complicated or obscure options further down.  So you don't necessarily
  # need to edit this whole thing, although it might be a good idea if you
  # want your bot to be hard to spot, and to work exactly the way you want
--- 1,10 ----
! #!/usr/local/bin/eggdrop
  #
  # This is a sample configuration file for your bot.  You will definitely
  # want to edit this, to set up your bot.  Right now it creates a bot called
! # "FBSDbot" which sits on channel #illiterate.
  #
  # The most vital things are listed at the top of this file, with the more
  # complicated or obscure options further down.  So you don't necessarily
  # need to edit this whole thing, although it might be a good idea if you
  # want your bot to be hard to spot, and to work exactly the way you want
***************
*** 14,36 ****
  
  #####  GENERAL STUFF  #####
  
  
  # the stuff people will see in /whois
! set nick "Lamestbot"
! set altnick "Llamabot"      ;# if the nick you want is in use
! set username "lamest"       ;# does not work if you have ident running!
! set realname "/msg LamestBot hello"
  
  # who's running this bot?
! set admin "Lamer <email: lamer@lame.connected.com>"
  
  # response for CTCP VERSION  (change this to make your bot hard to find)
! set ctcp-version "ircII 2.6 SunOS 4.1.3 :ircii 2.6: almost there..."
  
  # response for CTCP FINGER  (change this to make your bot hard to find)
! set ctcp-finger "Lamestbot (root@home), idle 0 seconds"
  
  # response for CTCP USERINFO  (change this to make your bot hard to find)
  set ctcp-userinfo "<None Supplied>"
  
  # [0/1] let users introduce themselves to the bot via 'hello'?
--- 14,36 ----
  
  #####  GENERAL STUFF  #####
  
  
  # the stuff people will see in /whois
! set nick "FBSDbot"
! set altnick "FBSDegg"            ;# if the nick you want is in use
! set username "Illiterate Tester" ;# does not work if you have ident running!
! set realname "/msg $nick hello"
  
  # who's running this bot?
! set admin "Illiterate Botmaster <$env(USER)@[info hostname]>"
  
  # response for CTCP VERSION  (change this to make your bot hard to find)
! set ctcp-version "eggdrop version 1.0o"
  
  # response for CTCP FINGER  (change this to make your bot hard to find)
! set ctcp-finger "FBSDBOT  ($env(USER)@[info hostname], idle 0 seconds"
  
  # response for CTCP USERINFO  (change this to make your bot hard to find)
  set ctcp-userinfo "<None Supplied>"
  
  # [0/1] let users introduce themselves to the bot via 'hello'?
***************
*** 45,55 ****
  # 'tcl-commands.doc'
  #unbind msg - hello *hello
  #bind msg - myword *hello
  
  # the server list -- the bot will start at the first server listed, and cycle
! # through them whenever it's disconnected
  # (please note: these examples are not real servers)
  set servers {
    newyork.happyirc.net:6667
    sanjose.happyirc.net:6667
    seattle.happyirc.net:6667
--- 45,60 ----
  # 'tcl-commands.doc'
  #unbind msg - hello *hello
  #bind msg - myword *hello
  
  # the server list -- the bot will start at the first server listed, and cycle
! # through them whenever it's disconnected.  DO check the MOTD for any server
! # you list below.  It is exrremely unwise to set yourself up to be G-lined
! # or K-lined for running bots connecting to an IRC server on which they are
! # forbidden.  Doing so will not only get bots banned from your host (or 
! # entire net) but regular users, as well.
! #
  # (please note: these examples are not real servers)
  set servers {
    newyork.happyirc.net:6667
    sanjose.happyirc.net:6667
    seattle.happyirc.net:6667
***************
*** 61,77 ****
  # connect?
  set never-give-up 0
  
  # how many seconds to wait for a response when connecting to a server
  # before giving up and moving on?
! set server-timeout 15
  
  # if the number of servers on the net gets below this number, it will
  # jump to a new server (ie, it will assume it's on the losing end of a
  # netsplit) -- set to 0 to turn off
  # [most irc networks use TS now, so it's to your advantage to turn this off]
! set servlimit 0
  
  # [0/1] if the bot's nickname is changed (for example, if the intended
  # nickname is already in use) keep trying to get the nick back?
  set keep-nick 1
  
--- 66,82 ----
  # connect?
  set never-give-up 0
  
  # how many seconds to wait for a response when connecting to a server
  # before giving up and moving on?
! set server-timeout 30
  
  # if the number of servers on the net gets below this number, it will
  # jump to a new server (ie, it will assume it's on the losing end of a
  # netsplit) -- set to 0 to turn off
  # [most irc networks use TS now, so it's to your advantage to turn this off]
! set servlimit 1
  
  # [0/1] if the bot's nickname is changed (for example, if the intended
  # nickname is already in use) keep trying to get the nick back?
  set keep-nick 1
  
***************
*** 81,95 ****
  
  # do this for each channel you wish to sit on:
  # NOTE: for some reason Tcl won't let you put comments inside { } -- so
  #   don't try it, cos it'll mess up your channel definition
  
! channel add #lamest {
    chanmode "+nt-likm"
    idle-kick 15
!   need-op { putserv "PRIVMSG #lamest :op me please!" }
!   need-invite { putserv "PRIVMSG #lamest :let me in!" }
  }
  
  # the things inside the { } are CHANNEL OPTIONS -- they can be set within
  # the "channel add" command, or by using a "channel set" command as in the
  # examples below.  they list all the options you can set for a channel.
--- 86,100 ----
  
  # do this for each channel you wish to sit on:
  # NOTE: for some reason Tcl won't let you put comments inside { } -- so
  #   don't try it, cos it'll mess up your channel definition
  
! channel add #illiterate {
    chanmode "+nt-likm"
    idle-kick 15
!   need-op { putserv "PRIVMSG #illiterate :op me please!" }
!   need-invite { putserv "PRIVMSG #illiterate :let me in!" }
  }
  
  # the things inside the { } are CHANNEL OPTIONS -- they can be set within
  # the "channel add" command, or by using a "channel set" command as in the
  # examples below.  they list all the options you can set for a channel.
***************
*** 117,178 ****
  # to turn it off, put:
  #   -autoop
  
  #   clear all channel bans when the bot joins?  (ie, force the channel's
  #   ban list to match the bot's internal list)
! channel set #lamest -clearbans
  
  #   when a ban is set, kick people who are on the channel and match the
  #   new ban?  (ie, they were on the channel before the ban)
! channel set #lamest +enforcebans
  
  #   only activate bans on the channel when necessary?  (this keeps the
  #   channel's ban list from getting excessively long.  the bot still remem-
  #   bers every ban, but it only activates a ban on the channel when it sees
  #   someone join who matches that ban.)
! channel set #lamest +dynamicbans
  
  #   allow bans to be made by users directly?  (if turned off, the bot will
  #   require all bans to be made through the bot's console)
! channel set #lamest +userbans
  
  #   op users with the +o (op) flag as soon as they join the channel?
  #   (hint: this is a BAD IDEA)
! channel set #lamest +autoop
  
  #   only let users with +o (op) flag be channel ops?
! channel set #lamest -bitch
  
  #   say a user's info line when she joins the channel?
! channel set #lamest +greet
  
  #   re-op a user with the +o (op) flag if they get deopped?
! channel set #lamest +protectops
  
  #   log the channel status line every 5 minutes? (some people think
  #   it's annoying; i think it's neat)
! channel set #lamest +statuslog
  
  #   de-op someone that enters the channel with server ops (ie, netsplit
  #   ops) when they didn't have them before the split?
! channel set #lamest +stopnethack
  
  #   remember people who harm the bot, and punish them later?
  #   users with +f (friend) flag are exempt from revenge
! channel set #lamest +revenge
! 
! #   prevent this channel from being listed on the botnet?  (for paranoid
! #   people)
! channel set #lamest -secret
  
  
  # here's a shorter example:
! channel add #botcentral {
!   chanmode "+mntisl 1"
!   idle-kick 1
! }
! channel set #botcentral +bitch +clearbans +enforcebans -greet +revenge
  
  
  # [0/1] allow users to store an info line?
  set use-info 1
  
--- 122,180 ----
  # to turn it off, put:
  #   -autoop
  
  #   clear all channel bans when the bot joins?  (ie, force the channel's
  #   ban list to match the bot's internal list)
! channel set #illiterate -clearbans
  
  #   when a ban is set, kick people who are on the channel and match the
  #   new ban?  (ie, they were on the channel before the ban)
! channel set #illiterate +enforcebans
  
  #   only activate bans on the channel when necessary?  (this keeps the
  #   channel's ban list from getting excessively long.  the bot still remem-
  #   bers every ban, but it only activates a ban on the channel when it sees
  #   someone join who matches that ban.)
! channel set #illiterate +dynamicbans
  
  #   allow bans to be made by users directly?  (if turned off, the bot will
  #   require all bans to be made through the bot's console)
! channel set #illiterate +userbans
  
  #   op users with the +o (op) flag as soon as they join the channel?
  #   (hint: this is a BAD IDEA)
! channel set #illiterate +autoop
  
  #   only let users with +o (op) flag be channel ops?
! channel set #illiterate -bitch
  
  #   say a user's info line when she joins the channel?
! channel set #illiterate +greet
  
  #   re-op a user with the +o (op) flag if they get deopped?
! channel set #illiterate +protectops
  
  #   log the channel status line every 5 minutes? (some people think
  #   it's annoying; i think it's neat)
! channel set #illiterate +statuslog
  
  #   de-op someone that enters the channel with server ops (ie, netsplit
  #   ops) when they didn't have them before the split?
! channel set #illiterate +stopnethack
  
  #   remember people who harm the bot, and punish them later?
  #   users with +f (friend) flag are exempt from revenge
! channel set #illiterate +revenge
  
  
  # here's a shorter example:
! #
! #	channel add #botcentral {
! #	  chanmode "+mntisl 1"
! #	  idle-kick 1
! #	}
! #	channel set #botcentral +bitch +clearbans +enforcebans -greet +revenge
  
  
  # [0/1] allow users to store an info line?
  set use-info 1
  
***************
*** 207,233 ****
  # belong to all channels by assigning it to channel "*".  there are also
  # five user-defined levels ('1'..'5') which are used by Tcl scripts.
  
  # in 'eggdrop.log' put msgs, commands, and errors from any channel:
  logfile mkco * "eggdrop.log"
! # in 'lame.log' put joins, parts, and mode changes from #lame:
! logfile jk #lame "lame.log"
  
  # [0/1] timestamp entries in the log file? (generally a good idea)
  set log-time 1
  
  # [0/1] keep logfiles for more than 48 hours -- instead of being called
  # "(logfilename).yesterday", the log files are named by the current date,
  # and kept around forever (eventually your directory might get full, so
  # be careful with this!)
! set keep-all-logs 0
  
  # once a day the logfiles are switched out and started fresh --
  # this specifies when that should happen (in military time)
  # [note that a leading 0 will make Tcl think this is an octal value,
  # something you probably don't want.]
! set switch-logfiles-at 300
  
  # this is the default console mode -- what masters will see automatically
  # when they dcc chat with the bot (masters can alter their own console
  # flags once they connect, though) -- it uses the same event flags as
  # the log files
--- 209,235 ----
  # belong to all channels by assigning it to channel "*".  there are also
  # five user-defined levels ('1'..'5') which are used by Tcl scripts.
  
  # in 'eggdrop.log' put msgs, commands, and errors from any channel:
  logfile mkco * "eggdrop.log"
! # in 'lamer.log' put joins, parts, and mode changes from #illiterate:
! logfile jk #illiterate "lamer.log"
  
  # [0/1] timestamp entries in the log file? (generally a good idea)
  set log-time 1
  
  # [0/1] keep logfiles for more than 48 hours -- instead of being called
  # "(logfilename).yesterday", the log files are named by the current date,
  # and kept around forever (eventually your directory might get full, so
  # be careful with this!)
! set keep-all-logs 1
  
  # once a day the logfiles are switched out and started fresh --
  # this specifies when that should happen (in military time)
  # [note that a leading 0 will make Tcl think this is an octal value,
  # something you probably don't want.]
! set switch-logfiles-at 250
  
  # this is the default console mode -- what masters will see automatically
  # when they dcc chat with the bot (masters can alter their own console
  # flags once they connect, though) -- it uses the same event flags as
  # the log files
***************
*** 239,252 ****
  
  #####  FILES AND DIRECTORIES  #####
  
  
  # the userfile: where user records are stored
! set userfile "LamestBot.user"
  
  # the notefile: where private notes between users are stored
! set notefile "LamestBot.notes"
  
  # helpdir: where the help files can be found (and there are plenty)
  set helpdir "help/"
  
  # textdir: where miscellaneous info files are
--- 241,254 ----
  
  #####  FILES AND DIRECTORIES  #####
  
  
  # the userfile: where user records are stored
! set userfile "FBSDbot.users"
  
  # the notefile: where private notes between users are stored
! set notefile "FBSDbot.notes"
  
  # helpdir: where the help files can be found (and there are plenty)
  set helpdir "help/"
  
  # textdir: where miscellaneous info files are
***************
*** 265,279 ****
  # the file transfer area works via dcc chat.  you can turn the file system
  # off by not defining the 'dcc-path' below.
  
  # this is the 'root' directory for the file system (set it to "" if you
  # don't want a file system)
! set dcc-path "/home/mydir/dcc"
  
  # if you want to allow uploads, set this to the directory uploads should be
  # put into
! set dcc-incoming "/home/mydir/dcc/incoming"
  
  # [0/1] alternately, you can set this, and uploads will go to the current
  # directory that a user is in
  set upload-to-cd 0
  
--- 267,281 ----
  # the file transfer area works via dcc chat.  you can turn the file system
  # off by not defining the 'dcc-path' below.
  
  # this is the 'root' directory for the file system (set it to "" if you
  # don't want a file system)
! set dcc-path "$env(HOME)/dcc"
  
  # if you want to allow uploads, set this to the directory uploads should be
  # put into
! set dcc-incoming "$env(HOME)/dcc/incoming"
  
  # [0/1] alternately, you can set this, and uploads will go to the current
  # directory that a user is in
  set upload-to-cd 0
  
***************
*** 299,309 ****
  # (default is 1024K = 1M)
  set dcc-maxsize 1024
  
  # [0/1] users with +o (op) flag will still need to have the +x (file system)
  # flag to have access to the file system?
! set require-x 0
  
  # [0/1] copy files into the /tmp directory before sending them?  this is
  # useful on most systems for file stability.  (someone could move a file
  # around while it's being downloaded, and mess up the transfer.)  but if
  # your directories are NFS mounted, it's a pain, and you'll want to set
--- 301,311 ----
  # (default is 1024K = 1M)
  set dcc-maxsize 1024
  
  # [0/1] users with +o (op) flag will still need to have the +x (file system)
  # flag to have access to the file system?
! set require-x 1
  
  # [0/1] copy files into the /tmp directory before sending them?  this is
  # useful on most systems for file stability.  (someone could move a file
  # around while it's being downloaded, and mess up the transfer.)  but if
  # your directories are NFS mounted, it's a pain, and you'll want to set
***************
*** 334,344 ****
  # something.  you need to know what you're doing.
  
  # what telnet port should this bot answer?
  # NOTE: if you are running more than one bot on the same machine, you will
  #   want to space the telnet ports at LEAST 5 apart... 10 is even better
! set telnet 3333
  
  # [0/1] only let bots connect via the telnet port?  (if not, then users
  # can telnet in to enter the party line just like a DCC chat)
  set telnet-bots-only 0
  
--- 336,348 ----
  # something.  you need to know what you're doing.
  
  # what telnet port should this bot answer?
  # NOTE: if you are running more than one bot on the same machine, you will
  #   want to space the telnet ports at LEAST 5 apart... 10 is even better
! # The default port in the "lamest bot" script is 3333 which is an IANA
! # assigned number for the service for dec-notes.
! set telnet 20333
  
  # [0/1] only let bots connect via the telnet port?  (if not, then users
  # can telnet in to enter the party line just like a DCC chat)
  set telnet-bots-only 0
  
***************
*** 348,365 ****
  # [0/1] allow other bots userfiles to overwrite yours?
  set passive 0
  
  # [0/1] users with the +o (op) flag will still need the +p (party line) flag
  # to join the dcc chat party line?
! set require-p 0
  
  # [0/1] allow people to telnet in, type 'NEW', and become a new user?
  set open-telnets 0
  
  # how long (in seconds) should i wait for a connect (dcc chat, telnet,
  # relay, etc) before it times out?
! set connect-timeout 15
  
  
  #####  MORE ADVANCED STUFF  #####
  
  
--- 352,369 ----
  # [0/1] allow other bots userfiles to overwrite yours?
  set passive 0
  
  # [0/1] users with the +o (op) flag will still need the +p (party line) flag
  # to join the dcc chat party line?
! set require-p 1
  
  # [0/1] allow people to telnet in, type 'NEW', and become a new user?
  set open-telnets 0
  
  # how long (in seconds) should i wait for a connect (dcc chat, telnet,
  # relay, etc) before it times out?
! set connect-timeout 25
  
  
  #####  MORE ADVANCED STUFF  #####
  
  
***************
*** 410,423 ****
  # send a note to anybody when I learn new users?
  set notify-newusers "HQ"
  
  # if compiled with owner, the following user(s) will ALWAYS have the
  # owner (+n) flag
! set owner "MrLame, MrsLame"
  
  # what flags should new users get as a default?
! set default-flags "px"
  
  # 'ntalk' and the like are no longer directly supported.  this will save
  # ntalk users from embarrassment:
  bind filt - "///*" no_ntalk
  proc no_ntalk {idx text} {
--- 414,427 ----
  # send a note to anybody when I learn new users?
  set notify-newusers "HQ"
  
  # if compiled with owner, the following user(s) will ALWAYS have the
  # owner (+n) flag
! set owner "Ignoramous"
  
  # what flags should new users get as a default?
! set default-flags "p"
  
  # 'ntalk' and the like are no longer directly supported.  this will save
  # ntalk users from embarrassment:
  bind filt - "///*" no_ntalk
  proc no_ntalk {idx text} {
