/[cvs]/eggdrop1.4/eggdrop.conf.dist
ViewVC logotype

Contents of /eggdrop1.4/eggdrop.conf.dist

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


Revision 1.37 - (show annotations) (download)
Tue Nov 9 21:16:13 1999 UTC (21 years, 5 months ago) by guppy
Branch: MAIN
Changes since 1.36: +16 -16 lines
eggdrop1.4 test

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23