/[cvs]/eggdrop1.9/eggdrop.complete.conf
ViewVC logotype

Contents of /eggdrop1.9/eggdrop.complete.conf

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


Revision 1.13 - (show annotations) (download)
Sun Aug 20 12:27:15 2000 UTC (19 years, 1 month ago) by johoho
Branch: MAIN
CVS Tags: eggdrop105040
Changes since 1.12: +6 -2 lines
documentation update

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.12 2000/08/03 21:51:32 fabian 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-idle-kick 0
451
452 set global-chanset {
453 -clearbans -enforcebans
454 +dynamicbans +userbans
455 -autoop -bitch
456 +greet +protectops
457 +statuslog -revenge
458 -secret -autovoice
459 +cycle +dontkickops
460 -inactive -protectfriends
461 +shared -seen
462 +userexempts +dynamicexempts
463 +userinvites +dynamicinvites
464 -nodesynch
465 }
466
467 set global-chanmode "nt"
468
469 set global-stopnethack-mode 0
470
471 # do this for each channel you wish to sit on:
472 # NOTE: for some reason Tcl won't let you put comments inside { } -- so
473 # don't try it, cos it'll mess up your channel definition
474
475 channel add #lamest {
476 chanmode "+nt-likm"
477 idle-kick 0
478 stopnethack-mode 0
479 need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
480 need-invite { putserv "PRIVMSG #lamest :let me in!" }
481 need-key { putserv "PRIVMSG #lamest :let me in!" }
482 need-unban { putserv "PRIVMSG #lamest :let me in!" }
483 need-limit { putserv "PRIVMSG #lamest :let me in!" }
484 flood-chan 10:60
485 flood-deop 3:10
486 flood-kick 3:10
487 flood-join 5:60
488 flood-ctcp 3:60
489 flood-nick 5:60
490 }
491
492 # the things inside the { } are CHANNEL OPTIONS -- they can be set within
493 # the "channel add" command, or by using a "channel set" command as in the
494 # examples below. they list all the options you can set for a channel.
495
496 # chanmode
497 # what modes will be enforced? '+' modes will always be kept on, '-' modes
498 # will always be kept off
499 # idle-kick
500 # kick channel members after how many minutes of being idle?
501 # (leave out to disable, or set to 0)
502
503 # stopnethack-mode
504 # de-op anyone who enters the channel with serverops
505 # 0 turn off,
506 # 1 isoptest (allow serverop if registered op),
507 # 2 wasoptest (allow serverop if op before split)
508 # 3 allow serverop if isop or wasop
509 # 4 allow serverop if isop and wasop
510 # 5 if channel -bitch: see stopnethack-mode 3
511 # if channel +bitch: see stopnethack-mode 1
512 # 6 if channel -bitch: see stopnethack-mode 2
513 # if channel +bitch: see stopnethack-mode 4
514
515 # need-op
516 # script to run (if any) when the bot needs to be op'd on this channel
517 # need-invite
518 # script to run (if any) when the bot gets locked out of the channel
519 # because the channel is +i
520 # need-key
521 # script to run (if any) when the bot gets locked out of the channel
522 # because it doesn't have the channel key
523 # need-unban
524 # script to run (if any) when the bot gets banned from this channel
525 # need-limit
526 # script to run (if any) when the bot gets locked out of the channel
527 # because the channel limit is full
528 # flood-chan (number:seconds)
529 # how many channel messages in hom many seconds is a flood
530 # not specifying or using number = 0 will not check chan floods!
531 # flood-ctcp (number:seconds)
532 # how many channel messages in hom many seconds is a flood
533 # not specifying or using number = 0 will not check ctcp floods!
534 # flood-deop (number:seconds)
535 # how many deops in how many seconds is a mass de-op
536 # not specifying or using number = 0 will not check de-op floods!
537 # flood-kick (number:seconds)
538 # how many kicks in how many seconds is a mass kick?
539 # not specifying or using number = 0 will not check mass kicks!
540 # flood-join (number:seconds)
541 # how many joins/nick changes in how many seconds is a join flood?
542 # not specifying or using number = 0 will not check join floods!
543
544 # note that "need-op", "need-invite", etc, are limited to 120 characters,
545 # so if you want to so something more complicated, just write a proc,
546 # and make them call your proc.
547
548 # there are also a lot of options that can be turned on or off for each
549 # channel. to turn an option on, put a + in front of it. to turn it off,
550 # put a - in front of it. ie, to have auto-op, put:
551 # +autoop
552 # to turn it off, put:
553 # -autoop
554
555 # clear all channel bans when the bot joins? (ie, force the channel's
556 # ban list to match the bot's internal list)
557 channel set #lamest -clearbans
558
559 # when a ban is set, kick people who are on the channel and match the
560 # new ban? (ie, they were on the channel before the ban)
561 channel set #lamest +enforcebans
562
563 # only activate bans on the channel when necessary? (this keeps the
564 # channel's ban list from getting excessively long. the bot still remem-
565 # bers every ban, but it only activates a ban on the channel when it sees
566 # someone join who matches that ban.)
567 channel set #lamest +dynamicbans
568
569 # allow bans to be made by users directly? (if turned off, the bot will
570 # require all bans to be made through the bot's console)
571 channel set #lamest +userbans
572
573 # only activate exempts on the channel when necessary? (this keeps the
574 # channel's exempt list from getting excessively long. the bot still
575 # remembers every exempt, but it only activates a exempt on the channel
576 # when it sees a ban set matching the exempt. The exempt remains active
577 # on the channel for as long as the ban is still active.
578 channel set #lamest +dynamicexempts
579
580 # allow exempts to be made by users directly? (if turned off, the bot will
581 # require all exempts to be made through the bot's console)
582 channel set #lamest +userexempts
583
584 # only activate invites on the channel when necessary? (this keeps the
585 # channel's invite list from getting excessively long. the bot still
586 # remembers every invite, but the invites are only activated when the
587 # channel is set to invite only and a user joins aftre requesting an
588 # invite. Once set the invite remains until the channel goes to -i
589 channel set #lamest +dynamicinvites
590
591 # allow invites to be made by users directly? (if turned off, the bot will
592 # require all invites to be made through the bot's console)
593 channel set #lamest +userinvites
594
595 # op users with the +o (op) flag as soon as they join the channel?
596 # (hint: this is a BAD IDEA)
597 channel set #lamest -autoop
598
599 # only let users with +o (op) flag be channel ops?
600 channel set #lamest -bitch
601
602 # say a user's info line when they join the channel?
603 channel set #lamest +greet
604
605 # re-op a user with the +o (op) flag if they get deopped?
606 channel set #lamest +protectops
607
608 # re-op a user with the +f (friend) flag if they get deopped?
609 channel set #lamest +protectfriends
610
611 # log the channel status line every 5 minutes? (some people think
612 # it's annoying; i think it's neat)
613 channel set #lamest +statuslog
614
615 # remember people who deop/kick/ban bots, valid ops or friends, and punish them?
616 # users with +f (friend) flag are exempt from revenge
617 channel set #lamest +revenge
618
619 # this works similar to revenge, but it triggers only for valid bots and
620 # allows the deop or kick of an op or friend
621 channel set #lamest +revengebot
622
623 # voice users with +v (voice) flag when they join the channel?
624 channel set #lamest +autovoice
625
626 # prevent this channel from being listed on the botnet? (for paranoid
627 # people)
628 channel set #lamest -secret
629
630 # share user channel info for this channel?
631 channel set #lamest -shared
632
633 # cycle the channel when it becomes op-less?
634 channel set #lamest +cycle
635
636 # do you want the bot not to be able to kick +o flag users ?
637 # letting them kick-flood for instance, to protect the channel agaisnt
638 # clone attacks
639 channel set #lamest +dontkickops
640
641 # prevents the bot from joining the channel (or makes it leave the channel
642 # if it is already there).
643 # Can be useful to make the bot leave a channel without loosing it's
644 # settings (flood settings, all these "channel set" settings), user flags
645 # for this channel, bans for this channel, and without affecting any
646 # sharing
647 channel set #lamest -inactive
648
649 # respond to seen requests in the channel? (seen module must be loaded)
650 channel set #lamest -seen
651
652 # allow non-ops to perform channel modes? (Stops bot from
653 # fighting with services such as ChanServ)
654 channel set #lamest +nodesynch
655
656 # here's a shorter example:
657 channel add #botcentral {
658 chanmode "+mntisl 1"
659 idle-kick 1
660 }
661 channel set #botcentral +bitch +clearbans +enforcebans -greet +revenge
662
663
664 ##### SERVER MODULE #####
665
666 # this provides the core server support (removing this is equivalent to
667 # the old NO_IRC define)
668 loadmodule server
669
670 # [0/1/2/3/4/5] What is your network?
671 # 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
672 # 4 = Efnet +e/+I hybrid, 5 = Others
673 set net-type 0
674
675 ##### variables:
676 # the nick of the bot, that which it uses on IRC, and on the botnet
677 # unless you specify a sperate botnet-nick
678 set nick "Lamestbot"
679
680 # an alternative nick to use if the nick specified by 'set nick' is
681 # unavailable. All '?' characters will be replaced by a random number.
682 set altnick "Llamabot"
683
684 # what to display in the real-name field for the bot
685 set realname "/msg LamestBot hello"
686
687 # script to run (if any) when first connecting to a server
688 set init-server { putserv "MODE $botnick +i-ws" }
689
690 # the server list -- the bot will start at the first server listed, and cycle
691 # through them whenever it's disconnected
692 # (please note: you need to change these servers to YOUR network's servers)
693 set servers {
694 you.need.to.change.this:6667
695 }
696
697 # [0/1] if the bot's nickname is changed (for example, if the intended
698 # nickname is already in use) keep trying to get the nick back?
699 set keep-nick 1
700
701 # [0/1] use /ison instead of /trace to see if our botnick is free or being
702 # used? (note: some irc admins, look for excessive use of /trace)
703 set use-ison 1
704
705 # [0/1] if this is set, a leading '~' on user@hosts WON'T be stripped off
706 set strict-host 0
707
708 # [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
709 # Normally it tells the DCC user that the CHAT or SEND has been rejected
710 # because they don't have access, but sometimes IRC server operators
711 # detect bots that way.
712 set quiet-reject 1
713
714 # [0/1] answer lower case ctcp's (non rfc compliant)
715 # mIRC will do this, most other clients will NOT
716 set lowercase-ctcp 0
717
718 # answer HOW MANY stacked ctcp's at once
719 set answer-ctcp 3
720
721 # setting any of the following with howmany == 0 will turn them off
722 # how many msgs in how many seconds from the same host constitutes a flood?
723 set flood-msg 5:60
724 # how many CTCPs in how many seconds?
725 set flood-ctcp 3:60
726
727 # [0/1] even if all the servers are down, cycle forever and keep trying to
728 # connect?
729 set never-give-up 1
730
731 # [0/1] If this setting is 0 then the eggdrop keeps a seperate list of the names
732 # irc servers call themselves, retaining what you entered in the config file.
733 # setting it to 1 will cause the bot to replace your entry with what
734 # the server actually calls itself
735 set strict-servernames 0
736
737 # if no port is specified on a .jump, which port should I use?
738 set default-port 6667
739
740 # number of seconds to wait between each server connect (0 = no wait)
741 # useful for preventing ircu throttling
742 # setting this too low could make your server admins *very* unhappy
743 set server-cycle-wait 60
744
745 # how many seconds to wait for a response when connecting to a server
746 # before giving up and moving on?
747 set server-timeout 15
748
749 # if the number of servers on the net gets below this number, it will
750 # jump to a new server (ie, it will assume it's on the losing end of a
751 # netsplit) -- set to 0 to turn off
752 # [most irc networks use TS or ND now, so it's to your advantage to turn
753 # this off]
754 set servlimit 0
755
756 # [0/1] check for stoned servers? (i.e. Where the server connection has
757 # died, but eggdrop hasn't been notified yet).
758 set check-stoned 1
759
760 # [0/1] enable console mode 'r'? this mode shows every raw message from the
761 # server to owners with console 'r' selected -- will take a bit more
762 # cpu.
763 # NOTE: This is a large security hole, allowing people to see mis-sent
764 # messages to the bot containing passwords
765 # This is now restricted to +n users only. Please choose your owners with care.
766 set use-console-r 0
767
768 # [0/1] enable logging of all information sent *to* a server, via console mode 'v'
769 # NOTE: This is a large security hole, allowing people to see passwords.
770 # This is now restricted to +n users only. Please choose your owners with care.
771 set debug-output 0
772
773 # [0/1] exit if the server sends a ERROR message?
774 set serverror-quit 1
775
776 # maximum number of lines to queue to the server.
777 # if you're going to dump large chunks of text to people over irc, you
778 # will probably want to raise this -- most people are fine at 300 though
779 set max-queue-msg 300
780
781 # [0/1] trigger bindings for ignored users?
782 set trigger-on-ignore 0
783
784 # [0/1] allow a msg being twice in a queue?
785 set double-mode 0
786 set double-server 0
787 set double-help 0
788
789 # [0/1/2] enable lag check? Set to 2 if you want the bot to change queues if
790 # somebody parts or changes nickname.
791 # ATTENTION: Setting 2 is very CPU intensive
792 set use-lagcheck 1
793
794 # [0/1/2] do you want the bot to optimize the kicking queues? Set to 2 if you
795 # want the bot to change queues if somebody parts or changes nickname.
796 # Note, setting 2 is not need if you set us-lagcheck to 2.
797 # ATTENTION: Setting 2 is very CPU intensive
798 set optimize-kicks 1
799
800
801
802 ##### SERVER MODULE - net-type 5 specific features (other networks) #####
803
804 # [0/1] some nets use umode +r to mean a restricted connection. If this is your
805 # case, and you want your bot to leave restricted servers and jump to the
806 # next one on his server list, then set it to 1.
807 # Automatically set to 0 for net-type 0/2/3/4, set to 1 for net-type 1.
808 # Only use this if you set net-type 5
809 #set check-mode-r 1
810
811 # This variable sets the maximum nick length allowed on the network. Most
812 # only support 9. The maximum supported by eggdrop is 32.
813 #set nick-len 9
814
815 ##### CTCP MODULE #####
816
817 # this provides the normal ctcp replies that you'd expect *RECOMMENDED*
818 loadmodule ctcp
819
820 # several variables exist to better blend your egg in. they are
821 # ctcp-version, ctcp-finger, and ctcp-userinfo. you can use set
822 # to set them to values you like.
823
824 # [0/1/2] 0: normal behavior. 1: bot ignores all CTCPs, except for CTCP
825 # CHATs & PINGs requested by +o flag users. 2: bot doesn't answer more
826 # than C CTCPs in S seconds. C/S are defined by the set flood-ctcp C:S (cf
827 # server module)
828 set ctcp-mode 0
829
830
831 ##### IRC MODULE #####
832
833 # this module provides ALL NORMAL IRC INTERACTION, if you want the normal
834 # join & maintain channels stuff, this is the module.
835 loadmodule irc
836
837 # [0/1] define this if you want to bounce all server bans
838 set bounce-bans 1
839
840 # [0/1] define this if you want to bounce all the server modes
841 set bounce-modes 0
842
843 # If there are more than max-bans active bans on a channel, then the
844 # bot won't try to put more bans. Thus it won't flood the irc server.
845 # ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
846 set max-bans 20
847
848 # There is a global limit for +b/+e/+I modes. This limit is set to 30 on
849 # 2.10 irc servers.
850 set max-modes 30
851
852 # [0/1] Do you want the bot to kick for control character/ctcp avalanches
853 # to a channel?
854 # Remember that if it does, as it won't ban them, it can be at the origin
855 # of a nice kick-flood
856 set kick-fun 0
857
858 # [0/1] Do you want the bot to ban for control character/ctcp avalanches
859 # to a channel?
860 # Can prevent the above described kick-flood, but can also fill the banlist
861 set ban-fun 0
862
863 # [0/1] let users introduce themselves to the bot via 'hello'?
864 set learn-users 0
865
866 # time (in seconds) to wait for someone to return from a netsplit
867 set wait-split 600
868
869 # time (in seconds) that someone must have been off-channel before
870 # re-displaying their info
871 set wait-info 180
872
873 # this is the maximum number of bytes to send in the arguments to mode's
874 # sent to the server, most servers default this to 200, so it should
875 # be sufficient
876 set mode-buf-length 200
877
878 # many irc ops check for bots that respond to 'hello'. you can change this
879 # to another word by uncommenting the following two lines, and changing
880 # "myword" to the word you want to use instead of 'hello' (it must be a
881 # single word)
882 # novice users are not expected to understand what these two lines do; they
883 # are just here to help you. for more information on 'bind', check the file
884 # 'tcl-commands.doc'
885 #unbind msg - hello *msg:hello
886 #bind msg - myword *msg:hello
887
888 # Many takeover attempts occur due to lame users blindy /msg ident'n to
889 # the bot without checking if the bot is the bot.
890 # We now unbind this command by default to discourage them
891 unbind msg - ident *msg:ident
892 unbind msg - addhost *msg:addhost
893
894 # If you or your users use many different hosts and wants to
895 # be able to add it by /msg'ing you need to remove the
896 # unbind ident line above or bind it to another word.
897 #bind msg - myidentword *msg:ident
898
899 # [0/1] If you are so lame you want the bot to display peoples info lines, even
900 # when you are too lazy to add their chanrecs to a channel, set this to 1
901 # *NOTE* This means *every* user with an info line will have their info
902 # display on EVERY channel they join (provided they have been gone longer than
903 # wait-info)
904 set no-chanrec-info 0
905
906 # [0/1/2/3] Defines how the bot should punish bad users when revenging.
907 # 0 for deop - 1 for deop and +d - 2 for deop, +d and kick - 3 for deop,
908 # chattr +d, kick and ban. Default is 1.
909 set revenge-mode 1
910
911 ##### IRC MODULE - net-type 1 specific features (IRCnet) #####
912
913 # Don't modify the following settings if you don't use IRCnet. The defaults following
914 # values are harmless for you.
915
916 # [0/1] define this if you want to bounce all server exemptions (+e modes)
917 # * This is an IRCNET feature
918 set bounce-exempts 0
919
920 # [0/1] define this if you want to bounce all server invitations (+I modes)
921 # * This is an IRCNET feature
922 set bounce-invites 0
923
924 # If there are more than max-exempts active +e modes on a channel, then
925 # the bot won't try to put more exemptions. Thus it won't flood the irc
926 # server. Only 2.10 servers are concerned by these +e modes.
927 # * This is an IRCNET feature
928 set max-exempts 20
929
930 # If there are more than max-invites active +I modes on a channel, then
931 # the bot won't try to put more invitations. Thus it won't flood the irc
932 # server. Only 2.10 irc servers are concerned by these +I modes.
933 # * This is an IRCNET feature
934 set max-invites 20
935
936 # The following lines should be left uncommented unless the default values
937 # are being over-ridden. By default exempts and invites are on for IRCnet
938 # and hybrid EFnet, but off for all other networks. This behaviour can be
939 # modified by the following 2 flags. If you're network doesn't support e/I
940 # modes then you'll be unable to use these features.
941 #
942 # [0/1] Do you want to enable exempts?
943 # set use-exempts 0
944
945 # [0/1] Do you want to use invites?
946 # set use-invites 0
947
948 # [0/1] Prevent mixing normal modes and +I/+e invite modes?
949 # At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
950 # so leave this flag set to 1. The servers will probably change their
951 # behaviour in the future, so you should first check before accepting the
952 # default.
953 set prevent-mixing 1
954
955 ##### IRC MODULE - net-type 5 specific features (other networks) #####
956
957 # kick-method defines how kicks (when enforcing bans) should be made:
958 # 0 = kick all nicks at once in one command
959 # X = kick X users at a time
960 #
961 # Automatically set by net-type:
962 # net-type 0, 2, 3 & 4 sets this to 1
963 # net-type 1 sets this to 4
964 #
965 # If you use net-type 5, you must set this yourself (default is 1)
966 #set kick-method 1
967
968 # some networks allow you to stack lots of channel modes into one
969 # line.
970 # they're all guaranteed to support at least 3, so that's the default,
971 # but if you know your network supports more, you may want to adjust
972 # this value. this value must be less than or equal to 6.
973 # Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
974 # 6 for net-type 2/3.
975 # Only use this if you set net-type 5
976 #set modes-per-line 3
977
978 # [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
979 # exactly what's needed
980 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
981 # Only use this if you set net-type 5
982 #set use-354 0
983
984 # [0/1] use rfc 1459 compliant string matching routines?
985 # All networks apart from Dalnet comply with rfc 1459, so you should only
986 # disable it on Dalnet or networks which use Dalnet's code.
987 #set rfc-compliant 1
988
989
990 ##### TRANSFER MODULE #####
991
992 # uncomment this line to load the transfer module, this provides
993 # dcc send/get support and bot userfile transfer support (not sharing)
994 #loadmodule transfer
995
996 ##### variables:
997 # set maximum number of simultaneous downloads to allow for each user
998 set max-dloads 3
999
1000 # set the block size for dcc transfers (ircII uses 512 bytes, but admits
1001 # that may be too small -- 1024 is standard these days)
1002 # set this to 0 to use turbo-dcc (recommended)
1003 set dcc-block 1024
1004
1005 # [0/1] copy files into the /tmp directory before sending them? this is
1006 # useful on most systems for file stability. (someone could move a file
1007 # around while it's being downloaded, and mess up the transfer.) but if
1008 # your directories are NFS mounted, it's a pain, and you'll want to set
1009 # this to 0. If you are low on disk space, you may want to set this to 0.
1010 set copy-to-tmp 1
1011
1012 # time (in seconds) that a dcc file transfer can remain inactive
1013 # before being timed out
1014 set xfer-timeout 30
1015
1016
1017 ##### SHARE MODULE #####
1018
1019 # this provides the userfile sharing support
1020 # (this requires the channels & transfer modules)
1021 #loadmodule share
1022
1023 ##### variables:
1024 # [0/1] When two bots get disconnected this flag allows them to create
1025 # a resync buffer which saves all changes done to the userfile during
1026 # the disconnect. So, when they reconnect, they will not have to transfer
1027 # the complete user file, but instead, just send the resync buffer.
1028 # If you have problems with this feature please tell us. Take a look at
1029 # doc/BUG-REPORT first though.
1030 #set allow-resync 0
1031
1032 # this specifies how long to hold another bots resync data for before
1033 # flushing it
1034 #set resync-time 900
1035
1036 # [0/1] when sharing user lists, DONT ACCEPT global flag changes from other bots?
1037 # NOTE: the bot will still send changes made on the bot, it just wont accept
1038 # any global flag changes from other bots
1039 #set private-global 0
1040
1041 # when sharing user lists, if private-global isn't set, which global flag
1042 # changes from other bots should be ignored ?
1043 #set private-globals "mnot"
1044
1045 # [0/1] when sharing user lists, DON'T ACCEPT any userfile changes from other
1046 # bots?
1047 # NOTE: paranoid people should use this feature on their hub bot - this
1048 # will force all +host/+user/chpass/etc. changes to be made via the hub
1049 #set private-user 0
1050
1051 # [0/1] this setting makes the bot discard it's own bot records in favor of
1052 # the ones sent by the hub. Note: This only works with hubs that are v1.5.1
1053 # _or higher_.
1054 #set override-bots 0
1055
1056
1057 ##### COMPRESS MODULE #####
1058
1059 # The compress module provides support for file compression. This allows the
1060 # bot to transfer compressed user files and therefore save a significant
1061 # amount of bandwidth, especially on very active hubs.
1062 #loadmodule compress
1063
1064 # [0/1] allow compressed sending of user files. The user files
1065 # are compressed with the compression level defined in `compress-level'.
1066 #set share-compressed 1
1067
1068 # [0-9] default compression level used.
1069 #set compress-level 9
1070
1071
1072 ##### FILESYSTEM MODULE #####
1073
1074 # uncomment this line to load the file system module, this provides
1075 # an area withing the bot where you can store files
1076 #loadmodule filesys
1077
1078 # this is the 'root' directory for the file system (set it to "" if you
1079 # don't want a file system)
1080 set files-path "/home/mydir/filesys"
1081
1082 # if you want to allow uploads, set this to the directory uploads should be
1083 # put into
1084 set incoming-path "/home/mydir/filesys/incoming"
1085
1086 # [0/1] alternately, you can set this, and uploads will go to the current
1087 # directory that a user is in
1088 set upload-to-pwd 0
1089
1090 # eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
1091 # to keep track of its own file system info -- if you can't do that (like
1092 # if the dcc path isn't owned by yours) or you just don't want it to do
1093 # that, specify a path here where you'd like all the database files to
1094 # be stored instead (otherwise, just leave it blank)
1095 set filedb-path ""
1096
1097 # set maximum number of people that can be in the file area at once
1098 # (0 to make it effectively infinite)
1099 set max-file-users 20
1100
1101 # maximum allowable file size that will be received, in K
1102 # (default is 1024K = 1M). 0 makes it effectively infinite.
1103 set max-filesize 1024
1104
1105
1106 ##### NOTES MODULE #####
1107
1108 # this provides support for storing of notes for users from each other
1109 # notes between currently online users is supported in the core, this is
1110 # only for storing the notes for later retrieval, direct user->user notes
1111 # are built-in
1112 loadmodule notes
1113
1114 # the notefile: where private notes between users are stored
1115 set notefile "LamestBot.notes"
1116
1117 # maximum number of notes to allow to be stored for each user
1118 # (to prevent flooding)
1119 set max-notes 50
1120
1121 # time (in days) to let stored notes live before expiring them
1122 set note-life 60
1123
1124 # [0/1] allow users to specify a forwarding address for forwarding notes
1125 # to another bot
1126 set allow-fwd 0
1127
1128 # [0/1] set this to 1 if you want the bot to let people know hourly if they
1129 # have any notes
1130 set notify-users 1
1131
1132 # [0/1] set this to 1 if you want the bot to let people know on join if they
1133 # have any notes
1134 set notify-onjoin 1
1135
1136 # comment out this next line, otherwise your bot won't start
1137 die "You didn't edit your config file like you were told, did you?"
1138
1139
1140 ##### CONSOLE MODULE #####
1141
1142 # this module provides storage of console settings when you exit the bot
1143 # (or .store)
1144 loadmodule console
1145
1146 ##### variables:
1147 # [0/1] save users console settings automatically? (otherwise they have to use
1148 # .store)
1149 set console-autosave 1
1150
1151 # [0-99999] if a user doesn't have any console settings saved, which channel
1152 # do you want them automatically put on?
1153 set force-channel 0
1154
1155 # [0/1] display a user's global info line when they join a botnet channel?
1156 set info-party 0
1157
1158
1159 ##### WOOBIE MODULE #####
1160
1161 # this serves absolutely no purpose and is for demonstrative
1162 # purposes only
1163 #loadmodule woobie
1164
1165
1166 ##### SEEN MODULE #####
1167
1168 # this module provides seen commands via msg, on channel or via
1169 # dcc, similar to the various scripts
1170 #loadmodule seen
1171
1172
1173 ##### BLOWFISH MODULE #####
1174
1175 ##### IF YOU DONT READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
1176
1177 # Choose your encryption method now, 'cause once you do, it ain't
1178 # changing 'til you get a new userfile, capish? At the moment, there
1179 # is only one encryption option: blowfish
1180
1181 # uncomment this line to load blowfish, the encryption module
1182 # for the bot, it will not start without it loaded and commented out
1183 # to make sure you read the whole config file
1184 # this is checkmodule, because during .restart the module will already
1185 # be loaded
1186 #checkmodule blowfish
1187
1188
1189 ##### ASSOC MODULE #####
1190
1191 # uncomment this line to load assoc support, i.e naming channels on
1192 # the botnet
1193 #loadmodule assoc
1194
1195
1196 ##### WIRE MODULE #####
1197
1198 # this module provides all the standard .wire commands via dcc.
1199 # it's an encrypted partyline communication tool, compatible with wire.tcl
1200 # uncomment this line to load it
1201 #loadmodule wire
1202
1203
1204 ##### SCRIPTS #####
1205
1206 # these are some commonly loaded (and needed) scripts.
1207 source scripts/alltools.tcl
1208 source scripts/action.fix.tcl
1209
1210 # use this for tcl and eggdrop downwards compatibility
1211 source scripts/compat.tcl
1212
1213 # This script provides many useful minor informational commands
1214 # (like setting users url's, email address, etc). You can modify
1215 # it to add extra entries, you might also want to modify help/userinfo.help
1216 # and help/msg/userinfo.help to change the help files.
1217 source scripts/userinfo.tcl
1218 loadhelp userinfo.help

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23