/[cvs]/eggdrop-alpha/eggdrop.complete.conf
ViewVC logotype

Contents of /eggdrop-alpha/eggdrop.complete.conf

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (show annotations) (download)
Mon Jan 22 04:36:48 2001 UTC (19 years, 4 months ago) by tothwolf
Branch: MAIN
Branch point for: eggdrop
Initial revision

1 #! /path/to/executable/eggdrop
2 # ^- set that to the directory eggdrop is in ie "#! /home/lamest/egg/eggdrop"
3 #
4 # $Id: eggdrop.complete.conf,v 1.25 2000/11/29 03:10:23 guppy Exp $
5 #
6 # this config file includes all possible options you can
7 # use to configure your bot properly.
8 # be sure that you know what you are doing!
9 #
10 # more detailed descriptions of all those settings can be found in
11 # doc/settings/
12
13
14 ##### GENERAL STUFF #####
15
16 # the username the bot uses, this is only used if identd isn't working
17 # on the machine the bot is running on.
18 set username "lamest"
19
20 # who's running this bot?
21 set admin "Lamer <email: lamer@lamest.lame.org>"
22
23 # what IRC network are you on? this is just info to share with others on
24 # your botnet, for human curiosity only.
25 set network "I.didnt.edit.my.config.file.net"
26
27 # what timezone is your bot in?
28 # The timezone string specifies the name of the timezone and
29 # must be three or more alphabetic characters.
30 # ex. Central European Time(UTC+1) could be "CET"
31 set timezone "EST"
32
33 # offset specifies the time value to be added to the local time
34 # to get Coordinated Universal Time (UTC aka GMT).
35 # The offset is positive if the local timezone is west of the
36 # Prime Meridian and negative if it is east.
37 # The value(hours) must be between 0 and 24
38 # ex. if the timezone is UTC+1 the offset is -1
39 set offset "5"
40
41 # If you dont want to use the timezone setting for scripting
42 # purpose only but instead everywhere possible (new) then
43 # uncomment the next line.
44 #set env(TZ) "$timezone $offset"
45
46 # if you're using virtual hosting (your machine has more than 1 IP), you
47 # may want to specify the particular IP to bind to. you can specify
48 # either by hostname or by IP. you may also want to set the hostname
49 # here if eggdrop has trouble detecting it when it starts up. (it will
50 # let you know if it has trouble -- trust me.)
51 #set my-hostname "virtual.host.com"
52 #set my-ip "99.99.0.0"
53
54 # if you want to have your eggdrop messages displayed in another language
55 # change the below command to match your preferences. An alternative would
56 # be to set the environment variabel EGG_LANG to that value.
57 #addlang "english"
58
59
60 ##### LOG FILES #####
61
62 # you can specify how many log files you can have upto. at midnight every
63 # day, the old log files are renamed and a new log file begins. by default,
64 # the old one is called "(logfilename).yesterday", and any logfiles before
65 # yesterday are erased.
66
67 # events are logged by certain categories -- this way you can specify
68 # exactly what kind of events you want sent to various logfiles. the
69 # events are:
70 # m private msgs/ctcps to the bot
71 # k kicks, bans, mode changes on the channel
72 # j joins, parts, netsplits on the channel
73 # p public chatter on the channel
74 # s server connects/disconnects/notices
75 # b information about bot linking and userfile sharing
76 # c commands people use (via msg or dcc)
77 # x file transfers and file-area commands
78 # r (if use-console-r defined) EVERYTHING sent to the bot by the server
79 # o other: misc info, errors -- IMPORTANT STUFF
80 # w wallops: msgs between IRCops (be sure to set the bot +w in init-server)
81 # There are others, but you probably shouldnt log them, it'd be rather
82 # unethical ;)
83
84 # maximum number of logfiles to allow - this can be increased if needed
85 # (don't decrease this)
86 set max-logs 5
87
88 # maximum size of your logfiles, set this to 0 to disable.
89 # this only works if you have keep-all-logs 0 (OFF)
90 # this value is in KiloBytes, so '550' would mean cycle logs when
91 # it reaches the size of 550 KiloBytes.
92 set max-logsize 0
93
94 # write the logfiles and check the size every minute
95 # (if max-logsize is enabled) instead of every 5minutes as before.
96 # This could be good if you have had problem with the
97 # logfile filling your quota or hdd or if you log +p
98 # and publish it on the web and wants more uptodate info.
99 # If you are concerned with resources keep the default setting 0.
100 # (although I haven't noticed anything)
101 set quick-logs 0
102
103 # each logfile also belongs to a certain channel. events of type 'k', 'j',
104 # and 'p' are logged to whatever channel they happened on. most other
105 # events are currently logged to every channel. you can make a logfile
106 # belong to all channels by assigning it to channel "*". there are also
107 # five user-defined levels ('1'..'5') which are used by Tcl scripts.
108
109 # in 'eggdrop.log' put private msgs/ctcps, commands, misc info, and
110 # errors from any channel:
111 logfile mco * "logs/eggdrop.log"
112 # in 'lame.log' put joins, parts, kicks, bans, and mode changes from #lamest:
113 logfile jk #lamest "logs/lamest.log"
114
115 # [0/1] timestamp entries in the log file? (generally a good idea)
116 set log-time 1
117
118 # [0/1] keep logfiles for more than 48 hours -- instead of being called
119 # "(logfilename).yesterday", the log files are named by the current date,
120 # and kept around forever (eventually your directory might get full, so
121 # be careful with this!)
122 set keep-all-logs 0
123
124 # if keep-all-logs is 1, this setting will define the suffix of the logfiles.
125 # The default will result in a suffix like "04May2000". "%Y%m%d" will produce
126 # the often used yyyymmdd format. Read the strtime manpages for more options.
127 # NOTE: On systems which don't support strftime, the default format will
128 # be used _always_.
129 set logfile-suffix ".%d%b%Y"
130
131 # once a day the logfiles are switched out and started fresh --
132 # this specifies when that should happen (in military time)
133 # [note that a leading 0 will make Tcl think this is an octal value,
134 # something you probably don't want.]
135 set switch-logfiles-at 300
136
137 # [0/1] enable quiet saves? "Writing user file..." and "Writing channel file ..."
138 # will not be logged if this option is enabled.
139 set quiet-save 0
140
141 # this is the default console mode -- what masters will see automatically
142 # when they dcc chat with the bot (masters can alter their own console
143 # flags once they connect, though) -- it uses the same event flags as
144 # the log files
145 # (note that the console channel is automatically set to your "primary"
146 # channel -- the one you defined first in this file. masters can change
147 # their console channel with the '.console' command, however.)
148 set console "mkcobxs"
149
150
151 ##### FILES AND DIRECTORIES #####
152
153 # the userfile: where user records are stored
154 set userfile "LamestBot.user"
155
156 # [0/1] do you want the userlist to be sorted when saving
157 set sort-users 0
158
159 # where the help files can be found (and there are plenty)
160 set help-path "help/"
161
162 # a good place to temporarily store files (ie: /tmp)
163 set temp-path "/tmp"
164
165 # the MOTD is displayed when people dcc chat to the bot.
166 # type '.help set motd' in DCC CHAT for tons of motd options.
167 set motd "text/motd"
168
169 # holds the banner displayed on telnet connections
170 set telnet-banner "text/banner"
171
172 # Specifies what permissions the user, channel and notes files should be set
173 # to. The octal values are the same as for the chmod system command.
174 #
175 # u g o u g o u g o
176 # 0600 rw------- 0400 r-------- 0200 -w------- u - user
177 # 0660 rw-rw---- 0440 r--r----- 0220 -w--w---- g - group
178 # 0666 rw-rw-rw- 0444 r--r--r-- 0222 -w--w--w- o - others
179 #
180 # Most users will want to leave the permissions set to 0600, to ensure
181 # maximum security.
182 set userfile-perm 0600
183
184 ##### BOTNET #####
185
186 # you probably shouldn't deal with this until reading 'botnet.doc' or
187 # something. you need to know what you're doing.
188
189 # if you want to use a different nickname on the botnet than you use on
190 # IRC, set it here:
191 #set botnet-nick "LlamaBot"
192
193 # what telnet port should this bot answer?
194 # NOTE: if you are running more than one bot on the same machine, you will
195 # want to space the telnet ports at LEAST 5 apart... 10 is even better
196 # if you would rather have one port for the botnet, and one for normal
197 # users, you will want something like this instead:
198 #listen 3333 bots
199 #listen 4444 users
200 # NOTE: there are more options listed for the listen command in
201 # doc/tcl-commands.doc
202 listen 3333 all
203
204 # [0/1] This setting will drop telnet connections not matching a known host
205 # It greatly improves protection from IRCOPs, but makes it impossible
206 # for NOIRC bots to add hosts or have NEW as a valid login
207 set protect-telnet 0
208
209 # [0/1] This setting will make the bot ignore DCC chat requests which appear to
210 # have bogus information on the grounds that the user may have been trying
211 # to make the bot connect to somewhere that will get it into trouble, or
212 # that the user has a broken client (like mIRC tends to do), in which case
213 # the connect wouldn't work anyway. It's suggested that you turn this on.
214 set dcc-sanitycheck 0
215
216 # and a timeout value for ident lookups would help (seconds)
217 set ident-timeout 5
218
219 # [0/1] users with the +o (global or channel op) flag will still need the +p
220 # (party line) flag to join the dcc chat party line?
221 set require-p 0
222
223 # [0/1] allow people to telnet in, type 'NEW', and become a new user?
224 # (If you set this to 1, you must set protect-telnet 0)
225 set open-telnets 0
226
227 # [0/1] Display 'Nickname.' instead of identifying ourselves when people
228 # telnet in. Set to 1 to only display Nickname.
229 # (useful if someone portscans your machine, they wont know we're here)
230 set stealth-telnets 0
231
232 # [0/1] Display a banner when people telnet in.
233 set use-telnet-banner 0
234
235 # how long (in seconds) should i wait for a connect (dcc chat, telnet,
236 # relay, etc) before it times out?
237 set connect-timeout 15
238
239 # number of messages / lines from a user on the partyline (dcc, telnet) before
240 # they are considered to be flooding (and therefore get booted)
241 set dcc-flood-thr 3
242
243 # how many telnet connection attempt in how many seconds from the same
244 # host constitutes a flood?
245 set telnet-flood 5:60
246
247 # [0/1] apply telnet flood protection for everyone?
248 # set this to 0 if you want to exempt +f users from telnet flood protection
249 set paranoid-telnet-flood 1
250
251 # how long should I wait (seconds) before giving up on hostname/address
252 # lookup? (you might want to increase this if you are on a slow network).
253 set resolve-timeout 15
254
255
256 ##### MORE ADVANCED STUFF #####
257
258 # are you behind a firewall? uncomment this and specify your socks host
259 #set firewall "proxy:178"
260 # or, for a Sun "telnet passthru" firewall, set it this way
261 # (does anyone besides Sun use this?)
262 #set firewall "!sun-barr.ebay:3666"
263
264 # if you have a NAT firewall (you box has an IP in one of the following
265 # ranges: 192.168.0.0-192.168.255.255, 172.16.0.0-172.31.255.255,
266 # 10.0.0.0-10.255.255.255 and your firewall transparently changes your
267 # address to a unique address for your box.) or you have IP masquerading
268 # between you and the rest of the world, and /dcc chat,/ctcp chat or
269 # userfile shareing aren't working. Enter your outside IP here.
270 # Do not enter anything for my-ip or my-hostname.
271 #set nat-ip "127.0.0.1"
272
273 # if you want all dcc file transfers to use 1 particular listening port
274 # (this pretty much limits you to one concurrent file transfer at a time),
275 # either because you're behind a firewall, or for other security reasons,
276 # set it here
277 #set reserved-port 9076
278
279 # temporary ignores will last how many minutes?
280 set ignore-time 15
281
282 # this setting affects what part of the hour the 'hourly' calls occur
283 # on the bot, this includes such things as note notifying,
284 # You can change that here (for example, "15" means to
285 # notify every hour at 15 minutes past the hour)
286 # this now includes when the bot will save its userfile
287 set hourly-updates 00
288
289 # if compiled with owner, the following user(s) will ALWAYS have the
290 # owner (+n) flag (You really should change this default)
291 set owner "MrLame, MrsLame"
292
293 # who should I send a note to when I learn new users?
294 set notify-newusers "$owner"
295
296 # what flags should new users get as a default?
297 # check '.help whois' on the partyline (dcc chat, telnet) for tons of
298 # options.
299 set default-flags "hp"
300
301 # what user-defined fields should be displayed in a '.whois'?
302 # this will only be shown if the user has one of these xtra fields
303 # you might prefer to comment this out and use the userinfo1.0.tcl script
304 # which provides commands for changing all of these.
305 set whois-fields "url birthday"
306
307 # [0/1/2] allow people from other bots (in your bot-net) to boot people off
308 # your bot's party line?
309 # values:
310 # 0 - allow *no* outside boots
311 # 1 - allow boots from sharebots
312 # 2 - allow any boots
313 set remote-boots 2
314
315 # [0/1] if you don't want people to unlink your share bots from remote bots
316 # set this to 0
317 set share-unlinks 1
318
319 # [0/1] die on receiving a SIGHUP?
320 # (if 0, it'll rehash instead of dying)
321 set die-on-sighup 0
322
323 # [0/1] die on receiving a SIGTERM?
324 # (if 0, it'll save userfile instead of dying)
325 set die-on-sigterm 0
326
327 # to enable the 'tcl' and 'set' command (let owners directly execute
328 # Tcl commands)? - a security risk!!
329 # If you select your owners wisely, you should be okay enabling these.
330 # to enable, comment these two lines out
331 # (In previous versions, this was enabled by default in eggdrop.h)
332 unbind dcc n tcl *dcc:tcl
333 unbind dcc n set *dcc:set
334
335 # [0/1/2] only let permanent owners use .tcl/.set if bound? then set it to 1
336 # moreover only let permanent owners use .dump? then set it to 2
337 # (the people must set the $owner variable)
338 set must-be-owner 0
339
340 # comment the following line out to add the 'simul' command (owners can
341 # manipulate other people on the party line).
342 # Please select owners wisely! Use this command ethically!
343 unbind dcc n simul *dcc:simul
344
345 # maximum number of dcc connections you will allow - you can increase this
346 # later, but never decrease it, 50 seems to be enough for everybody
347 set max-dcc 50
348
349 # this setting is so that people can't send fake ports to your bot when
350 # they try to dcc it. irc clients should never use a port below 1024 and
351 # well 65535 is the highest port possible. this setting is used for telnet
352 # too.
353 set dcc-portrange 1024:65535
354
355 # [0/1] add the 'dccsimul' tcl command (needed by certain scripts like
356 # action.fix.tcl)
357 set enable-simul 1
358
359 # [0/1] allow +d & +k users to use commands bound as -|- ?
360 set allow-dk-cmds 1
361
362 # If a bot connects which already seems to be connected, I wait
363 # dupwait-timeout seconds before I check again and then finally reject
364 # the bot. This is useful to stop hubs from rejecting bots that actually
365 # have already disconnected from another hub, but the disconnect information
366 # has not yet spread over the botnet due to lag.
367 set dupwait-timeout 5
368
369
370
371 # You MUST remove this line for this config file to work. This has been
372 # added to prevent you from starting up a bot that is not fully configured.
373 # Bots that have not been fully configured may join the wrong IRC network,
374 # the wrong channels, or generally do things that you do not want. Please
375 # make sure that you have double-checked the settings you want.
376 # There's also a similar line lower down, just to make sure you're reading :)
377
378 die "Please edit your config file."
379
380
381
382 ########## MODULES ##########
383
384 # below are various settings for the modules available with eggdrop,
385 # PLEASE EDIT THEM CAREFULLY, READ THEM, even if you're an old hand
386 # at eggdrop, lots of things have changed slightly
387
388 # this is the directory to look for the modules in, if you run the
389 # bot in the compilation directories you will want to set this to ""
390 # if you use 'make install' (like all good kiddies do ;) this is a fine
391 # default, otherwise, use your head :)
392 set mod-path "modules/"
393
394
395 #### DNS MODULE #####
396
397 # this module provides asynchronous dns support. This will avoid long
398 # periods where the bot just hangs there, waiting for a hostname to
399 # resolve, which often let it timeout on all other connections.
400 loadmodule dns
401
402 ##### CHANNELS MODULE #####
403
404 # this next module provides channel related support for the bot, without
405 # it, it will just sit on irc, it can respond to msg & ctcp commands, but
406 # that's all
407 loadmodule channels
408
409 # the chanfile: where dynamic channel settings are stored
410 set chanfile "LamestBot.chan"
411
412 # temporary bans will last how many minutes? if set to 0, bot never removes
413 # them.
414 set ban-time 120
415
416 # temporary exemptions (+e modes) will last how many minutes? if set to 0,
417 # bot never removes them. This is an IRCNET feature. The bot will check the
418 # exempts every X minutes, but will not remove the exempt if a ban is set on
419 # the channel that matches that exempt. Once the ban is removed then the
420 # exempt will be removed the next time the bot checks.
421 set exempt-time 60
422
423 # temporary invitations (+I modes) will last how many minutes? if set to
424 # 0, bot never removes them. This is an IRCNET feature. The bot will check the
425 # invites every X minutes, but will not remove them if the channel is +i. Once
426 # the channel is -i then the bot will remove then invite mode next time it
427 # checks this counter
428 set invite-time 60
429
430 # [0/1] expire bans/exempts/invites set by other opped bots on the channel?
431 # set force-expire 0
432
433 # [0/1] share user greets with other bots on the channel if sharing user data?
434 set share-greet 0
435
436 # [0/1] allow users to store an info line?
437 set use-info 1
438
439 # these settings are used as default values when you
440 # .+chan #chan or .tcl channel add #chan
441 # look in the section above for explanation on every option
442
443 set global-flood-chan 10:60
444 set global-flood-deop 3:10
445 set global-flood-kick 3:10
446 set global-flood-join 5:60
447 set global-flood-ctcp 3:60
448 set global-flood-nick 5:60
449
450 set global-aop-delay 5:30
451
452 set global-idle-kick 0
453 set global-chanmode "nt"
454 set global-stopnethack-mode 0
455 set global-revenge-mode 1
456
457 set global-chanset {
458 -autoop -autovoice
459 -bitch +cycle
460 +dontkickops +dynamicbans
461 +dynamicexempts +dynamicinvites
462 -enforcebans +greet
463 -inactive -nodesynch
464 -protectfriends +protectops
465 -revenge -revengebot
466 -secret -seen
467 +shared +statuslog
468 +userbans +userexempts
469 +userinvites
470 }
471
472 # do this for each channel you wish to sit on:
473 # NOTE: for some reason Tcl won't let you put comments inside { } -- so
474 # don't try it, cos it'll mess up your channel definition
475
476 channel add #lamest {
477 chanmode "+nt-likm"
478 idle-kick 0
479 stopnethack-mode 0
480 revenge-mode 1
481 aop-delay 5:30
482 need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
483 need-invite { putserv "PRIVMSG #lamest :let me in!" }
484 need-key { putserv "PRIVMSG #lamest :let me in!" }
485 need-unban { putserv "PRIVMSG #lamest :let me in!" }
486 need-limit { putserv "PRIVMSG #lamest :let me in!" }
487 flood-chan 10:60
488 flood-deop 3:10
489 flood-kick 3:10
490 flood-join 5:60
491 flood-ctcp 3:60
492 flood-nick 5:60
493 }
494
495 # the things inside the { } are CHANNEL OPTIONS -- they can be set within
496 # the "channel add" command, or by using a "channel set" command as in the
497 # examples below. they list all the options you can set for a channel.
498
499 # chanmode
500 # what modes will be enforced? '+' modes will always be kept on, '-' modes
501 # will always be kept off
502 # idle-kick
503 # kick channel members after how many minutes of being idle?
504 # (leave out to disable, or set to 0)
505
506 # stopnethack-mode
507 # de-op anyone who enters the channel with serverops
508 # 0 turn off,
509 # 1 isoptest (allow serverop if registered op),
510 # 2 wasoptest (allow serverop if op before split)
511 # 3 allow serverop if isop or wasop
512 # 4 allow serverop if isop and wasop
513 # 5 if channel -bitch: see stopnethack-mode 3
514 # if channel +bitch: see stopnethack-mode 1
515 # 6 if channel -bitch: see stopnethack-mode 2
516 # if channel +bitch: see stopnethack-mode 4
517
518 # revenge-mode
519 # defines how the bot should punish bad users when revenging.
520 # default is 1.
521 # 0 for deop
522 # 1 for deop and +d
523 # 2 for deop, +d and kick
524 # 3 for deop, chattr +d, kick and ban
525
526 # aop-delay (minimum:maximum)
527 # for autoop and autovoice
528 # aop-delay 0 no autoopdelay
529 # aop-delay x or aop-delay x:x x sec. autoopdelay
530 # aop-delay x:y random delay
531 # if a autoopped user joined during a other delayed autoop is pending,
532 # the bot will sent both autoop based on the last-joined-user-delay-time,
533 # probable in only one line.
534
535 # need-op
536 # script to run (if any) when the bot needs to be op'd on this channel
537 # need-invite
538 # script to run (if any) when the bot gets locked out of the channel
539 # because the channel is +i
540 # need-key
541 # script to run (if any) when the bot gets locked out of the channel
542 # because it doesn't have the channel key
543 # need-unban
544 # script to run (if any) when the bot gets banned from this channel
545 # need-limit
546 # script to run (if any) when the bot gets locked out of the channel
547 # because the channel limit is full
548 # flood-chan (number:seconds)
549 # how many channel messages in hom many seconds is a flood
550 # not specifying or using number = 0 will not check chan floods!
551 # flood-ctcp (number:seconds)
552 # how many channel messages in hom many seconds is a flood
553 # not specifying or using number = 0 will not check ctcp floods!
554 # flood-deop (number:seconds)
555 # how many deops in how many seconds is a mass de-op
556 # not specifying or using number = 0 will not check de-op floods!
557 # flood-kick (number:seconds)
558 # how many kicks in how many seconds is a mass kick?
559 # not specifying or using number = 0 will not check mass kicks!
560 # flood-join (number:seconds)
561 # how many joins/nick changes in how many seconds is a join flood?
562 # not specifying or using number = 0 will not check join floods!
563
564 # note that "need-op", "need-invite", etc, are limited to 120 characters,
565 # so if you want to so something more complicated, just write a proc,
566 # and make them call your proc.
567
568 # there are also a lot of options that can be turned on or off for each
569 # channel. to turn an option on, put a + in front of it. to turn it off,
570 # put a - in front of it. ie, to have auto-op, put:
571 # +autoop
572 # to turn it off, put:
573 # -autoop
574
575 # when a ban is set, kick people who are on the channel and match the
576 # new ban? (ie, they were on the channel before the ban)
577 channel set #lamest +enforcebans
578
579 # only activate bans on the channel when necessary? (this keeps the
580 # channel's ban list from getting excessively long. the bot still remem-
581 # bers every ban, but it only activates a ban on the channel when it sees
582 # someone join who matches that ban.)
583 channel set #lamest +dynamicbans
584
585 # allow bans to be made by users directly? (if turned off, the bot will
586 # require all bans to be made through the bot's console)
587 channel set #lamest +userbans
588
589 # only activate exempts on the channel when necessary? (this keeps the
590 # channel's exempt list from getting excessively long. the bot still
591 # remembers every exempt, but it only activates a exempt on the channel
592 # when it sees a ban set matching the exempt. The exempt remains active
593 # on the channel for as long as the ban is still active.
594 channel set #lamest +dynamicexempts
595
596 # allow exempts to be made by users directly? (if turned off, the bot will
597 # require all exempts to be made through the bot's console)
598 channel set #lamest +userexempts
599
600 # only activate invites on the channel when necessary? (this keeps the
601 # channel's invite list from getting excessively long. the bot still
602 # remembers every invite, but the invites are only activated when the
603 # channel is set to invite only and a user joins aftre requesting an
604 # invite. Once set the invite remains until the channel goes to -i
605 channel set #lamest +dynamicinvites
606
607 # allow invites to be made by users directly? (if turned off, the bot will
608 # require all invites to be made through the bot's console)
609 channel set #lamest +userinvites
610
611 # op users with the +o (op) flag as soon as they join the channel?
612 # (hint: this is a BAD IDEA)
613 channel set #lamest -autoop
614
615 # only let users with +o (op) flag be channel ops?
616 channel set #lamest -bitch
617
618 # say a user's info line when they join the channel?
619 channel set #lamest +greet
620
621 # re-op a user with the +o (op) flag if they get deopped?
622 channel set #lamest +protectops
623
624 # re-op a user with the +f (friend) flag if they get deopped?
625 channel set #lamest +protectfriends
626
627 # log the channel status line every 5 minutes? (some people think
628 # it's annoying; i think it's neat)
629 channel set #lamest +statuslog
630
631 # remember people who deop/kick/ban bots, valid ops or friends, and punish them?
632 # users with +f (friend) flag are exempt from revenge
633 channel set #lamest +revenge
634
635 # this works similar to revenge, but it triggers only for valid bots and
636 # allows the deop or kick of an op or friend
637 channel set #lamest +revengebot
638
639 # voice users with +v (voice) flag when they join the channel?
640 channel set #lamest +autovoice
641
642 # prevent this channel from being listed on the botnet? (for paranoid
643 # people)
644 channel set #lamest -secret
645
646 # share user channel info for this channel?
647 channel set #lamest -shared
648
649 # cycle the channel when it becomes op-less?
650 channel set #lamest +cycle
651
652 # do you want the bot not to be able to kick +o flag users ?
653 # letting them kick-flood for instance, to protect the channel agaisnt
654 # clone attacks
655 channel set #lamest +dontkickops
656
657 # prevents the bot from joining the channel (or makes it leave the channel
658 # if it is already there).
659 # Can be useful to make the bot leave a channel without loosing it's
660 # settings (flood settings, all these "channel set" settings), user flags
661 # for this channel, bans for this channel, and without affecting any
662 # sharing
663 channel set #lamest -inactive
664
665 # respond to seen requests in the channel? (seen module must be loaded)
666 channel set #lamest -seen
667
668 # allow non-ops to perform channel modes? (Stops bot from
669 # fighting with services such as ChanServ)
670 channel set #lamest +nodesynch
671
672 # here's a shorter example:
673 channel add #botcentral {
674 chanmode "+mntisl 1"
675 idle-kick 1
676 }
677 channel set #botcentral +bitch +enforcebans -greet +revenge
678
679
680 ##### SERVER MODULE #####
681
682 # this provides the core server support (removing this is equivalent to
683 # the old NO_IRC define)
684 loadmodule server
685
686 # [0/1/2/3/4/5] What is your network?
687 # 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
688 # 4 = Efnet +e/+I hybrid, 5 = Others
689 set net-type 0
690
691 ##### variables:
692 # the nick of the bot, that which it uses on IRC, and on the botnet
693 # unless you specify a sperate botnet-nick
694 set nick "Lamestbot"
695
696 # an alternative nick to use if the nick specified by 'set nick' is
697 # unavailable. All '?' characters will be replaced by a random number.
698 set altnick "Llamabot"
699
700 # what to display in the real-name field for the bot
701 set realname "/msg LamestBot hello"
702
703 # script to run (if any) when first connecting to a server
704 set init-server { putserv "MODE $botnick +i-ws" }
705
706 # if no port is specified on a .jump, which port should I use?
707 set default-port 6667
708
709 # the server list -- the bot will start at the first server listed, and cycle
710 # through them whenever it's disconnected
711 # (please note: you need to change these servers to YOUR network's servers)
712 set servers {
713 you.need.to.change.this:6667
714 }
715
716 # [0/1] if the bot's nickname is changed (for example, if the intended
717 # nickname is already in use) keep trying to get the nick back?
718 set keep-nick 1
719
720 # [0/1] use /ison instead of /trace to see if our botnick is free or being
721 # used? (note: some irc admins, look for excessive use of /trace)
722 set use-ison 1
723
724 # [0/1] if this is set, a leading '~' on user@hosts WON'T be stripped off
725 set strict-host 0
726
727 # [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
728 # Normally it tells the DCC user that the CHAT or SEND has been rejected
729 # because they don't have access, but sometimes IRC server operators
730 # detect bots that way.
731 set quiet-reject 1
732
733 # [0/1] answer lower case ctcp's (non rfc compliant)
734 # mIRC will do this, most other clients will NOT
735 set lowercase-ctcp 0
736
737 # answer HOW MANY stacked ctcp's at once
738 set answer-ctcp 3
739
740 # setting any of the following with howmany == 0 will turn them off
741 # how many msgs in how many seconds from the same host constitutes a flood?
742 set flood-msg 5:60
743 # how many CTCPs in how many seconds?
744 set flood-ctcp 3:60
745
746 # [0/1] even if all the servers are down, cycle forever and keep trying to
747 # connect?
748 set never-give-up 1
749
750 # [0/1] If this setting is 0 then the eggdrop keeps a seperate list of the names
751 # irc servers call themselves, retaining what you entered in the config file.
752 # setting it to 1 will cause the bot to replace your entry with what
753 # the server actually calls itself
754 set strict-servernames 0
755
756 # number of seconds to wait between each server connect (0 = no wait)
757 # useful for preventing ircu throttling
758 # setting this too low could make your server admins *very* unhappy
759 set server-cycle-wait 60
760
761 # how many seconds to wait for a response when connecting to a server
762 # before giving up and moving on?
763 set server-timeout 15
764
765 # if the number of servers on the net gets below this number, it will
766 # jump to a new server (ie, it will assume it's on the losing end of a
767 # netsplit) -- set to 0 to turn off
768 # [most irc networks use TS or ND now, so it's to your advantage to turn
769 # this off]
770 set servlimit 0
771
772 # [0/1] check for stoned servers? (i.e. Where the server connection has
773 # died, but eggdrop hasn't been notified yet).
774 set check-stoned 1
775
776 # [0/1] enable console mode 'r'? this mode shows every raw message from the
777 # server to owners with console 'r' selected -- will take a bit more
778 # cpu.
779 # NOTE: This is a large security hole, allowing people to see mis-sent
780 # messages to the bot containing passwords
781 # This is now restricted to +n users only. Please choose your owners with care.
782 set use-console-r 0
783
784 # [0/1] enable logging of all information sent *to* a server, via console mode 'v'
785 # NOTE: This is a large security hole, allowing people to see passwords.
786 # This is now restricted to +n users only. Please choose your owners with care.
787 set debug-output 0
788
789 # [0/1] exit if the server sends a ERROR message?
790 set serverror-quit 1
791
792 # maximum number of lines to queue to the server.
793 # if you're going to dump large chunks of text to people over irc, you
794 # will probably want to raise this -- most people are fine at 300 though
795 set max-queue-msg 300
796
797 # [0/1] trigger bindings for ignored users?
798 set trigger-on-ignore 0
799
800 # [0/1] allow a msg being twice in a queue?
801 set double-mode 0
802 set double-server 0
803 set double-help 0
804
805 # [0/1/2] do you want the bot to optimize the kicking queues? Set to 2 if you
806 # want the bot to change queues if somebody parts or changes nickname.
807 # ATTENTION: Setting 2 is very CPU intensive
808 set optimize-kicks 1
809
810
811
812 ##### SERVER MODULE - net-type 5 specific features (other networks) #####
813
814 # [0/1] some nets use umode +r to mean a restricted connection. If this is your
815 # case, and you want your bot to leave restricted servers and jump to the
816 # next one on his server list, then set it to 1.
817 # Automatically set to 0 for net-type 0/2/3/4, set to 1 for net-type 1.
818 # Only use this if you set net-type 5
819 #set check-mode-r 1
820
821 # This variable sets the maximum nick length allowed on the network. Most
822 # only support 9. The maximum supported by eggdrop is 32.
823 #set nick-len 9
824
825 ##### CTCP MODULE #####
826
827 # this provides the normal ctcp replies that you'd expect *RECOMMENDED*
828 loadmodule ctcp
829
830 # several variables exist to better blend your egg in. they are
831 # ctcp-version, ctcp-finger, and ctcp-userinfo. you can use set
832 # to set them to values you like.
833
834 # [0/1/2] 0: normal behavior. 1: bot ignores all CTCPs, except for CTCP
835 # CHATs & PINGs requested by +o flag users. 2: bot doesn't answer more
836 # than C CTCPs in S seconds. C/S are defined by the set flood-ctcp C:S (cf
837 # server module)
838 set ctcp-mode 0
839
840
841 ##### IRC MODULE #####
842
843 # this module provides ALL NORMAL IRC INTERACTION, if you want the normal
844 # join & maintain channels stuff, this is the module.
845 loadmodule irc
846
847 # [0/1] define this if you want to bounce all server bans
848 set bounce-bans 1
849
850 # [0/1] define this if you want to bounce all the server modes
851 set bounce-modes 0
852
853 # If there are more than max-bans active bans on a channel, then the
854 # bot won't try to put more bans. Thus it won't flood the irc server.
855 # ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
856 set max-bans 20
857
858 # There is a global limit for +b/+e/+I modes. This limit is set to 30 on
859 # 2.10 irc servers.
860 set max-modes 30
861
862 # [0/1] Do you want the bot to kick for control character/ctcp avalanches
863 # to a channel?
864 # Remember that if it does, as it won't ban them, it can be at the origin
865 # of a nice kick-flood
866 set kick-fun 0
867
868 # [0/1] Do you want the bot to ban for control character/ctcp avalanches
869 # to a channel?
870 # Can prevent the above described kick-flood, but can also fill the banlist
871 set ban-fun 0
872
873 # [0/1] let users introduce themselves to the bot via 'hello'?
874 set learn-users 0
875
876 # time (in seconds) to wait for someone to return from a netsplit
877 set wait-split 600
878
879 # time (in seconds) that someone must have been off-channel before
880 # re-displaying their info
881 set wait-info 180
882
883 # this is the maximum number of bytes to send in the arguments to mode's
884 # sent to the server, most servers default this to 200, so it should
885 # be sufficient
886 set mode-buf-length 200
887
888 # many irc ops check for bots that respond to 'hello'. you can change this
889 # to another word by uncommenting the following two lines, and changing
890 # "myword" to the word you want to use instead of 'hello' (it must be a
891 # single word)
892 # novice users are not expected to understand what these two lines do; they
893 # are just here to help you. for more information on 'bind', check the file
894 # 'tcl-commands.doc'
895 #unbind msg - hello *msg:hello
896 #bind msg - myword *msg:hello
897
898 # Many takeover attempts occur due to lame users blindy /msg ident'n to
899 # the bot without checking if the bot is the bot.
900 # We now unbind this command by default to discourage them
901 unbind msg - ident *msg:ident
902 unbind msg - addhost *msg:addhost
903
904 # If you or your users use many different hosts and wants to
905 # be able to add it by /msg'ing you need to remove the
906 # unbind ident line above or bind it to another word.
907 #bind msg - myidentword *msg:ident
908
909 # [0/1] If you are so lame you want the bot to display peoples info lines, even
910 # when you are too lazy to add their chanrecs to a channel, set this to 1
911 # *NOTE* This means *every* user with an info line will have their info
912 # display on EVERY channel they join (provided they have been gone longer than
913 # wait-info)
914 set no-chanrec-info 0
915
916 ##### IRC MODULE - net-type 1 specific features (IRCnet) #####
917
918 # Don't modify the following settings if you don't use IRCnet. The defaults following
919 # values are harmless for you.
920
921 # [0/1] define this if you want to bounce all server exemptions (+e modes)
922 # * This is an IRCNET feature
923 set bounce-exempts 0
924
925 # [0/1] define this if you want to bounce all server invitations (+I modes)
926 # * This is an IRCNET feature
927 set bounce-invites 0
928
929 # If there are more than max-exempts active +e modes on a channel, then
930 # the bot won't try to put more exemptions. Thus it won't flood the irc
931 # server. Only 2.10 servers are concerned by these +e modes.
932 # * This is an IRCNET feature
933 set max-exempts 20
934
935 # If there are more than max-invites active +I modes on a channel, then
936 # the bot won't try to put more invitations. Thus it won't flood the irc
937 # server. Only 2.10 irc servers are concerned by these +I modes.
938 # * This is an IRCNET feature
939 set max-invites 20
940
941 # The following lines should be left uncommented unless the default values
942 # are being over-ridden. By default exempts and invites are on for IRCnet
943 # and hybrid EFnet, but off for all other networks. This behaviour can be
944 # modified by the following 2 flags. If you're network doesn't support e/I
945 # modes then you'll be unable to use these features.
946 #
947 # [0/1] Do you want to enable exempts?
948 # set use-exempts 0
949
950 # [0/1] Do you want to use invites?
951 # set use-invites 0
952
953 # [0/1] Prevent mixing normal modes and +I/+e invite modes?
954 # At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
955 # so leave this flag set to 1. The servers will probably change their
956 # behaviour in the future, so you should first check before accepting the
957 # default.
958 set prevent-mixing 1
959
960 ##### IRC MODULE - net-type 5 specific features (other networks) #####
961
962 # kick-method defines how kicks (when enforcing bans) should be made:
963 # 0 = kick all nicks at once in one command
964 # X = kick X users at a time
965 #
966 # Automatically set by net-type:
967 # net-type 0, 2, 3 & 4 sets this to 1
968 # net-type 1 sets this to 4
969 #
970 # If you use net-type 5, you must set this yourself (default is 1)
971 #set kick-method 1
972
973 # some networks allow you to stack lots of channel modes into one
974 # line.
975 # they're all guaranteed to support at least 3, so that's the default,
976 # but if you know your network supports more, you may want to adjust
977 # this value. this value must be less than or equal to 6.
978 # Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
979 # 6 for net-type 2/3.
980 # Only use this if you set net-type 5
981 #set modes-per-line 3
982
983 # [0/1] Some networks don't include the +l limit and +k or -k key modes
984 # in the modes-per-line (see above) limitation. Set include-lk to 0 for
985 # those networks.
986 # Automatically set to 1 for net-type 1/2/3, set to 0 for net-type 0/4.
987 # Only use this if you set net-type 5.
988 #set include-lk 1
989
990 # [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
991 # exactly what's needed
992 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
993 # Only use this if you set net-type 5
994 #set use-354 0
995
996 # [0/1] use rfc 1459 compliant string matching routines?
997 # All networks apart from Dalnet comply with rfc 1459, so you should only
998 # disable it on Dalnet or networks which use Dalnet's code.
999 #set rfc-compliant 1
1000
1001
1002 ##### TRANSFER MODULE #####
1003
1004 # uncomment this line to load the transfer module, this provides
1005 # dcc send/get support and bot userfile transfer support (not sharing)
1006 #loadmodule transfer
1007
1008 ##### variables:
1009 # set maximum number of simultaneous downloads to allow for each user
1010 set max-dloads 3
1011
1012 # set the block size for dcc transfers (ircII uses 512 bytes, but admits
1013 # that may be too small -- 1024 is standard these days)
1014 # set this to 0 to use turbo-dcc (recommended)
1015 set dcc-block 1024
1016
1017 # [0/1] copy files into the /tmp directory before sending them? this is
1018 # useful on most systems for file stability. (someone could move a file
1019 # around while it's being downloaded, and mess up the transfer.) but if
1020 # your directories are NFS mounted, it's a pain, and you'll want to set
1021 # this to 0. If you are low on disk space, you may want to set this to 0.
1022 set copy-to-tmp 1
1023
1024 # time (in seconds) that a dcc file transfer can remain inactive
1025 # before being timed out
1026 set xfer-timeout 30
1027
1028
1029 ##### SHARE MODULE #####
1030
1031 # this provides the userfile sharing support
1032 # (this requires the channels & transfer modules)
1033 #loadmodule share
1034
1035 ##### variables:
1036 # [0/1] When two bots get disconnected this flag allows them to create
1037 # a resync buffer which saves all changes done to the userfile during
1038 # the disconnect. So, when they reconnect, they will not have to transfer
1039 # the complete user file, but instead, just send the resync buffer.
1040 # If you have problems with this feature please tell us. Take a look at
1041 # doc/BUG-REPORT first though.
1042 #set allow-resync 0
1043
1044 # this specifies how long to hold another bots resync data for before
1045 # flushing it
1046 #set resync-time 900
1047
1048 # [0/1] when sharing user lists, DONT ACCEPT global flag changes from other bots?
1049 # NOTE: the bot will still send changes made on the bot, it just wont accept
1050 # any global flag changes from other bots
1051 #set private-global 0
1052
1053 # when sharing user lists, if private-global isn't set, which global flag
1054 # changes from other bots should be ignored ?
1055 #set private-globals "mnot"
1056
1057 # [0/1] when sharing user lists, DON'T ACCEPT any userfile changes from other
1058 # bots?
1059 # NOTE: paranoid people should use this feature on their hub bot - this
1060 # will force all +host/+user/chpass/etc. changes to be made via the hub
1061 #set private-user 0
1062
1063 # [0/1] this setting makes the bot discard it's own bot records in favor of
1064 # the ones sent by the hub. Note: This only works with hubs that are v1.5.1
1065 # _or higher_.
1066 #set override-bots 0
1067
1068
1069 ##### COMPRESS MODULE #####
1070
1071 # The compress module provides support for file compression. This allows the
1072 # bot to transfer compressed user files and therefore save a significant
1073 # amount of bandwidth, especially on very active hubs.
1074 #loadmodule compress
1075
1076 # [0/1] allow compressed sending of user files. The user files
1077 # are compressed with the compression level defined in `compress-level'.
1078 #set share-compressed 1
1079
1080 # [0-9] default compression level used.
1081 #set compress-level 9
1082
1083
1084 ##### FILESYSTEM MODULE #####
1085
1086 # uncomment this line to load the file system module, this provides
1087 # an area withing the bot where you can store files
1088 #loadmodule filesys
1089
1090 # this is the 'root' directory for the file system (set it to "" if you
1091 # don't want a file system)
1092 set files-path "/home/mydir/filesys"
1093
1094 # if you want to allow uploads, set this to the directory uploads should be
1095 # put into
1096 set incoming-path "/home/mydir/filesys/incoming"
1097
1098 # [0/1] alternately, you can set this, and uploads will go to the current
1099 # directory that a user is in
1100 set upload-to-pwd 0
1101
1102 # eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
1103 # to keep track of its own file system info -- if you can't do that (like
1104 # if the dcc path isn't owned by yours) or you just don't want it to do
1105 # that, specify a path here where you'd like all the database files to
1106 # be stored instead (otherwise, just leave it blank)
1107 set filedb-path ""
1108
1109 # set maximum number of people that can be in the file area at once
1110 # (0 to make it effectively infinite)
1111 set max-file-users 20
1112
1113 # maximum allowable file size that will be received, in K
1114 # (default is 1024K = 1M). 0 makes it effectively infinite.
1115 set max-filesize 1024
1116
1117
1118 ##### NOTES MODULE #####
1119
1120 # this provides support for storing of notes for users from each other
1121 # notes between currently online users is supported in the core, this is
1122 # only for storing the notes for later retrieval, direct user->user notes
1123 # are built-in
1124 loadmodule notes
1125
1126 # the notefile: where private notes between users are stored
1127 set notefile "LamestBot.notes"
1128
1129 # maximum number of notes to allow to be stored for each user
1130 # (to prevent flooding)
1131 set max-notes 50
1132
1133 # time (in days) to let stored notes live before expiring them
1134 set note-life 60
1135
1136 # [0/1] allow users to specify a forwarding address for forwarding notes
1137 # to another bot
1138 set allow-fwd 0
1139
1140 # [0/1] set this to 1 if you want the bot to let people know hourly if they
1141 # have any notes
1142 set notify-users 1
1143
1144 # [0/1] set this to 1 if you want the bot to let people know on join if they
1145 # have any notes
1146 set notify-onjoin 1
1147
1148 # comment out this next line, otherwise your bot won't start
1149 die "You didn't edit your config file like you were told, did you?"
1150
1151
1152 ##### CONSOLE MODULE #####
1153
1154 # this module provides storage of console settings when you exit the bot
1155 # (or .store)
1156 loadmodule console
1157
1158 ##### variables:
1159 # [0/1] save users console settings automatically? (otherwise they have to use
1160 # .store)
1161 set console-autosave 1
1162
1163 # [0-99999] if a user doesn't have any console settings saved, which channel
1164 # do you want them automatically put on?
1165 set force-channel 0
1166
1167 # [0/1] display a user's global info line when they join a botnet channel?
1168 set info-party 0
1169
1170
1171 ##### WOOBIE MODULE #####
1172
1173 # this serves absolutely no purpose and is for demonstrative
1174 # purposes only
1175 #loadmodule woobie
1176
1177
1178 ##### SEEN MODULE #####
1179
1180 # this module provides seen commands via msg, on channel or via
1181 # dcc, similar to the various scripts
1182 #loadmodule seen
1183
1184
1185 ##### BLOWFISH MODULE #####
1186
1187 ##### IF YOU DONT READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
1188
1189 # Choose your encryption method now, 'cause once you do, it ain't
1190 # changing 'til you get a new userfile, capish? At the moment, there
1191 # is only one encryption option: blowfish
1192
1193 # uncomment this line to load blowfish, the encryption module
1194 # for the bot, it will not start without it loaded and commented out
1195 # to make sure you read the whole config file
1196 # this is checkmodule, because during .restart the module will already
1197 # be loaded
1198 #checkmodule blowfish
1199
1200
1201 ##### ASSOC MODULE #####
1202
1203 # uncomment this line to load assoc support, i.e naming channels on
1204 # the botnet
1205 #loadmodule assoc
1206
1207
1208 ##### WIRE MODULE #####
1209
1210 # this module provides all the standard .wire commands via dcc.
1211 # it's an encrypted partyline communication tool, compatible with wire.tcl
1212 # uncomment this line to load it
1213 #loadmodule wire
1214
1215
1216 ##### SCRIPTS #####
1217
1218 # these are some commonly loaded (and needed) scripts.
1219 source scripts/alltools.tcl
1220 source scripts/action.fix.tcl
1221
1222 # use this for tcl and eggdrop downwards compatibility
1223 source scripts/compat.tcl
1224
1225 # This script provides many useful minor informational commands
1226 # (like setting users url's, email address, etc). You can modify
1227 # it to add extra entries, you might also want to modify help/userinfo.help
1228 # and help/msg/userinfo.help to change the help files.
1229 source scripts/userinfo.tcl
1230 loadhelp userinfo.help

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23