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

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

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


Revision 1.2 - (show annotations) (download)
Sat Oct 9 15:46:33 1999 UTC (21 years ago) by fabian
Branch: MAIN
Changes since 1.1: +30 -11 lines
all changes to the 1.3 tree merged with 1.4

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23