/[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.34 - (show annotations) (download)
Tue Oct 12 21:25:14 1999 UTC (21 years, 6 months ago) by guppy
Branch: MAIN
Changes since 1.33: +0 -2 lines
come on rc2

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.
242 # Do not enter anything for my-ip or my-hostname.
243 #set nat-ip "127.0.0.1"
244
245 # if you want all dcc file transfers to use 1 particular listening port
246 # (this pretty much limits you to one concurrent file transfer at a time),
247 # either because you're behind a firewall, or for other security reasons,
248 # set it here
249 #set reserved-port 9076
250
251 # temporary ignores will last how many minutes?
252 set ignore-time 15
253
254 # this setting affects what part of the hour the 'hourly' calls occur
255 # on the bot, this includes such things as note notifying,
256 # You can change that here (for example, "15" means to
257 # notify every hour at 15 minutes past the hour)
258 # this now includes when the bot will save its userfile
259 set hourly-updates 00
260
261 # if compiled with owner, the following user(s) will ALWAYS have the
262 # owner (+n) flag (You really should change this default)
263 set owner "MrLame, MrsLame"
264
265 # who should I send a note to when I learn new users?
266 set notify-newusers "$owner"
267
268 # what flags should new users get as a default?
269 # check '.help whois' on the partyline (dcc chat, telnet) for tons of
270 # options.
271 set default-flags "hp"
272
273 # what user-defined fields should be displayed in a '.whois'?
274 # this will only be shown if the user has one of these xtra fields
275 # you might prefer to comment this out and use the userinfo1.0.tcl script
276 # which provides commands for changing all of these.
277 set whois-fields "url birthday"
278
279 # [0/1/2] allow people from other bots (in your bot-net) to boot people off
280 # your bot's party line?
281 # values:
282 # 0 - allow *no* outside boots
283 # 1 - allow boots from sharebots
284 # 2 - allow any boots
285 set remote-boots 2
286
287 # [0/1] if you don't want people to unlink your share bots from remote bots
288 # set this to 0
289 set share-unlinks 1
290
291 # [0/1] die on receiving a SIGHUP?
292 # (if 0, it'll rehash instead of dying)
293 set die-on-sighup 0
294
295 # [0/1] die on receiving a SIGTERM?
296 # (if 0, it'll save userfile instead of dying)
297 set die-on-sigterm 0
298
299 # to enable the 'tcl' and 'set' command (let owners directly execute
300 # Tcl commands)? - a security risk!!
301 # If you select your owners wisely, you should be okay enabling these.
302 # to enable, comment these two lines out
303 # (In previous versions, this was enabled by default in eggdrop.h)
304 unbind dcc n tcl *dcc:tcl
305 unbind dcc n set *dcc:set
306
307 # [0/1/2] only let permanent owners use .tcl/.set if bound? then set it to 1
308 # moreover only let permanent owners use .dump? then set it to 2
309 # (the people must set the $owner variable)
310 set must-be-owner 0
311
312 # comment the following line out to add the 'simul' command (owners can
313 # manipulate other people on the party line).
314 # Please select owners wisely! Use this command ethically!
315 unbind dcc n simul *dcc:simul
316
317 # maximum number of dcc connections you will allow - you can increase this
318 # later, but never decrease it, 50 seems to be enough for everybody
319 set max-dcc 50
320
321 # this setting is so that people can't send fake ports to your bot when
322 # they try to dcc it. irc clients should never use a port below 1024 and
323 # well 65535 is the highest port possible. this setting is used for telnet
324 # too.
325 set dcc-portrange 1024:65535
326
327 # [0/1] add the 'dccsimul' tcl command (needed by certain scripts like
328 # action.fix.tcl)
329 set enable-simul 1
330
331 # [0/1] allow +d & +k users to use commands bound as -|- ?
332 set allow-dk-cmds 1
333
334
335
336 # You MUST remove this line for this config file to work. This has been
337 # added to prevent you from starting up a bot that is not fully configured.
338 # Bots that have not been fully configured may join the wrong IRC network,
339 # the wrong channels, or generally do things that you do not want. Please
340 # make sure that you have double-checked the settings you want.
341 # There's also a similar line lower down, just to make sure you're reading :)
342
343 die "Please edit your config file."
344
345
346
347 ############## MODULES #################
348
349 # below are various settings for the modules available with eggdrop,
350 # PLEASE EDIT THEM CAREFULLY, READ THEM, even if you're an old hand
351 # at eggdrop, lots of things have changed slightly
352
353 # this is the directory to look for the modules in, if you run the
354 # bot in the compilation directories you will want to set this to ""
355 # if you use 'make install' (like all good kiddies do ;) this is a fine
356 # default, otherwise, use your head :)
357 set mod-path "modules/"
358
359
360
361 #### CHANNELS MODULE #####
362
363 # this next module provides channel related support for the bot, without
364 # it, it will just sit on irc, it can respond to msg & ctcp commands, but
365 # that's all
366 loadmodule channels
367
368 # the chanfile: where dynamic channel settings are stored
369 set chanfile "LamestBot.chan"
370
371 # temporary bans will last how many minutes? if set to 0, bot never removes
372 # them.
373 set ban-time 120
374
375 # temporary exemptions (+e modes) will last how many minutes? if set to 0,
376 # bot never removes them. This is an IRCNET feature. The bot will check the
377 # exempts every X minutes, but will not remove the exempt if a ban is set on
378 # the channel that matches that exempt. Once the ban is removed then the
379 # exempt will be removed the next time the bot checks.
380 set exempt-time 60
381
382 # temporary invitations (+I modes) will last how many minutes? if set to
383 # 0, bot never removes them. This is an IRCNET feature. The bot will check the
384 # invites every X minutes, but will not remove them if the channel is +i. Once
385 # the channel is -i then the bot will remove then invite mode next time it
386 # checks this counter
387 set invite-time 60
388
389 # [0/1] expire bans/exempts/invites set by other opped bots on the channel?
390 # set force-expire 0
391
392 # [0/1] share user greets with other bots on the channel if sharing user data?
393 set share-greet 0
394
395 # [0/1] allow users to store an info line?
396 set use-info 1
397
398 # these settings are used as default values when you
399 # .+chan #chan or .tcl channel add #chan
400 # look in the section above for explanation on every option
401
402 set global-flood-chan 10:60
403 set global-flood-deop 3:10
404 set global-flood-kick 3:10
405 set global-flood-join 5:60
406 set global-flood-ctcp 3:60
407
408 set global-chanset {
409 -clearbans -enforcebans
410 +dynamicbans +userbans
411 -autoop -bitch
412 +greet +protectops
413 +statuslog +stopnethack
414 -revenge -secret
415 -autovoice +cycle
416 +dontkickops -wasoptest
417 -inactive -protectfriends
418 +shared -seen
419 +userexempts +dynamicexempts
420 +userinvites +dynamicinvites
421 }
422
423 set global-chanmode "nt"
424
425 # do this for each channel you wish to sit on:
426 # NOTE: for some reason Tcl won't let you put comments inside { } -- so
427 # don't try it, cos it'll mess up your channel definition
428
429 channel add #lamest {
430 chanmode "+nt-likm"
431 idle-kick 0
432 need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
433 need-invite { putserv "PRIVMSG #lamest :let me in!" }
434 need-key { putserv "PRIVMSG #lamest :let me in!" }
435 need-unban { putserv "PRIVMSG #lamest :let me in!" }
436 need-limit { putserv "PRIVMSG #lamest :let me in!" }
437 flood-chan 10:60
438 flood-deop 3:10
439 flood-kick 3:10
440 flood-join 5:60
441 flood-ctcp 3:60
442 }
443
444 # the things inside the { } are CHANNEL OPTIONS -- they can be set within
445 # the "channel add" command, or by using a "channel set" command as in the
446 # examples below. they list all the options you can set for a channel.
447
448 # chanmode
449 # what modes will be enforced? '+' modes will always be kept on, '-' modes
450 # will always be kept off
451 # idle-kick
452 # kick channel members after how many minutes of being idle?
453 # (leave out to disable, or set to 0)
454 # need-op
455 # script to run (if any) when the bot needs to be op'd on this channel
456 # need-invite
457 # script to run (if any) when the bot gets locked out of the channel
458 # because the channel is +i
459 # need-key
460 # script to run (if any) when the bot gets locked out of the channel
461 # because it doesn't have the channel key
462 # need-unban
463 # script to run (if any) when the bot gets banned from this channel
464 # need-limit
465 # script to run (if any) when the bot gets locked out of the channel
466 # because the channel limit is full
467 # flood-chan (number:seconds)
468 # how many channel messages in hom many seconds is a flood
469 # not specifying or using number = 0 will not check chan floods!
470 # flood-ctcp (number:seconds)
471 # how many channel messages in hom many seconds is a flood
472 # not specifying or using number = 0 will not check ctcp floods!
473 # flood-deop (number:seconds)
474 # how many deops in how many seconds is a mass de-op
475 # not specifying or using number = 0 will not check de-op floods!
476 # flood-kick (number:seconds)
477 # how many kicks in how many seconds is a mass kick?
478 # not specifying or using number = 0 will not check mass kicks!
479 # flood-join (number:seconds)
480 # how many joins/nick changes in how many seconds is a join flood?
481 # not specifying or using number = 0 will not check join floods!
482
483
484 # note that "need-op", "need-invite", etc, are limited to 120 characters,
485 # so if you want to so something more complicated, just write a proc,
486 # and make them call your proc.
487
488 # there are also a lot of options that can be turned on or off for each
489 # channel. to turn an option on, put a + in front of it. to turn it off,
490 # put a - in front of it. ie, to have auto-op, put:
491 # +autoop
492 # to turn it off, put:
493 # -autoop
494
495 # clear all channel bans when the bot joins? (ie, force the channel's
496 # ban list to match the bot's internal list)
497 channel set #lamest -clearbans
498
499 # when a ban is set, kick people who are on the channel and match the
500 # new ban? (ie, they were on the channel before the ban)
501 channel set #lamest +enforcebans
502
503 # only activate bans on the channel when necessary? (this keeps the
504 # channel's ban list from getting excessively long. the bot still remem-
505 # bers every ban, but it only activates a ban on the channel when it sees
506 # someone join who matches that ban.)
507 channel set #lamest +dynamicbans
508
509 # allow bans to be made by users directly? (if turned off, the bot will
510 # require all bans to be made through the bot's console)
511 channel set #lamest +userbans
512
513 # only activate exempts on the channel when necessary? (this keeps the
514 # channel's exempt list from getting excessively long. the bot still
515 # remembers every exempt, but it only activates a exempt on the channel
516 # when it sees a ban set matching the exempt. The exempt remains active
517 # on the channel for as long as the ban is still active.
518 channel set #lamest +dynamicexempts
519
520 # allow exempts to be made by users directly? (if turned off, the bot will
521 # require all exempts to be made through the bot's console)
522 channel set #lamest +userexempts
523
524 # only activate invites on the channel when necessary? (this keeps the
525 # channel's invite list from getting excessively long. the bot still
526 # remembers every invite, but the invites are only activated when the
527 # channel is set to invite only and a user joins aftre requesting an
528 # invite. Once set the invite remains until the channel goes to -i
529 channel set #lamest +dynamicinvites
530
531 # allow invites to be made by users directly? (if turned off, the bot will
532 # require all invites to be made through the bot's console)
533 channel set #lamest +userinvites
534
535 # op users with the +o (op) flag as soon as they join the channel?
536 # (hint: this is a BAD IDEA)
537 channel set #lamest -autoop
538
539 # only let users with +o (op) flag be channel ops?
540 channel set #lamest -bitch
541
542 # say a user's info line when they join the channel?
543 channel set #lamest +greet
544
545 # re-op a user with the +o (op) flag if they get deopped?
546 channel set #lamest +protectops
547
548 # re-op a user with the +f (friend) flag if they get deopped?
549 channel set #lamest +protectfriends
550
551 # log the channel status line every 5 minutes? (some people think
552 # it's annoying; i think it's neat)
553 channel set #lamest +statuslog
554
555 # de-op someone that enters the channel with server ops (ie, netsplit
556 # ops) when they didn't have them before the split?
557 channel set #lamest +stopnethack
558
559 # remember people who deop/kick/ban the bot or valid ops, and punish them?
560 # users with +f (friend) flag are exempt from revenge
561 channel set #lamest +revenge
562
563 # voice users with +v (voice) flag when they join the channel?
564 channel set #lamest +autovoice
565
566 # prevent this channel from being listed on the botnet? (for paranoid
567 # people)
568 channel set #lamest -secret
569
570 # share user channel info for this channel?
571 channel set #lamest -shared
572
573 # cycle the channel when it becomes op-less?
574 channel set #lamest +cycle
575
576 # do you want the bot not to be able to kick +o flag users ?
577 # letting them kick-flood for instance, to protect the channel agaisnt
578 # clone attacks
579 channel set #lamest +dontkickops
580
581 # during net-rejoins does a wasop test for +stopnethack (same as +w user
582 # flag, but affects a whole channel)
583 channel set #lamest -wasoptest
584
585 # prevents the bot from joining the channel (or makes it leave the channel
586 # if it is already there).
587 # Can be useful to make the bot leave a channel without loosing it's
588 # settings (flood settings, all these "channel set" settings), user flags
589 # for this channel, bans for this channel, and without affecting any
590 # sharing
591 channel set #lamest -inactive
592
593 # respond to seen requests in the channel? (seen module must be loaded)
594 channel set #lamest -seen
595
596 # here's a shorter example:
597 channel add #botcentral {
598 chanmode "+mntisl 1"
599 idle-kick 1
600 }
601 channel set #botcentral +bitch +clearbans +enforcebans -greet +revenge
602
603 ##### SERVER MODULE #####
604
605 # this provides the core server support (removing this is equivalent to
606 # the old NO_IRC define)
607 loadmodule server
608
609 # [0/1/2/3/4/5] What is your network?
610 # 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
611 # 4 = Efnet +e/+I hybrid, 5 = Others
612 set net-type 0
613
614 ##### variables:
615 # the nick of the bot, that which it uses on IRC, and on the botnet
616 # unless you specify a sperate botnet-nick
617 set nick "Lamestbot"
618
619 # an alternative nick to use if the nick specified by 'set nick' is
620 # unavailable. All '?' characters will be replaced by a random number.
621 set altnick "Llamabot"
622
623 # what to display in the real-name field for the bot
624 set realname "/msg LamestBot hello"
625
626 # script to run (if any) when first connecting to a server
627 set init-server { putserv "MODE $botnick +i-ws" }
628
629 # the server list -- the bot will start at the first server listed, and cycle
630 # through them whenever it's disconnected
631 # (please note: you need to change these servers to YOUR network's servers)
632 set servers {
633 you.need.to.change.this:6667
634 }
635
636 # [0/1] if the bot's nickname is changed (for example, if the intended
637 # nickname is already in use) keep trying to get the nick back?
638 set keep-nick 1
639
640 # [0/1] use /ison instead of /trace to see if our botnick is free or being
641 # used? (note: some irc admins, look for excessive use of /trace)
642 set use-ison 1
643
644 # [0/1] if this is set, a leading '~' on user@hosts WON'T be stripped off
645 set strict-host 0
646
647 # [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
648 # Normally it tells the DCC user that the CHAT or SEND has been rejected
649 # because they don't have access, but sometimes IRC server operators
650 # detect bots that way.
651 set quiet-reject 1
652
653 # [0/1] answer lower case ctcp's (non rfc compliant)
654 # mIRC will do this, most other clients will NOT
655 set lowercase-ctcp 0
656
657 # answer HOW MANY stacked ctcp's at once
658 set answer-ctcp 3
659
660 # setting any of the following with howmany == 0 will turn them off
661 # how many msgs in how many seconds from the same host constitutes a flood?
662 set flood-msg 5:60
663 # how many CTCPs in how many seconds?
664 set flood-ctcp 3:60
665
666 # [0/1] even if all the servers are down, cycle forever and keep trying to
667 # connect?
668 set never-give-up 1
669
670 # [0/1] If this setting is 0 then the eggdrop keeps a seperate list of the names
671 # irc servers call themselves, retaining what you entered in the config file.
672 # setting it to 1 will cause the bot to replace your entry with what
673 # the server actually calls itself
674 set strict-servernames 0
675
676 # if no port is specified on a .jump, which port should I use?
677 set default-port 6667
678
679 # number of seconds to wait between each server connect (0 = no wait)
680 # useful for preventing ircu throttling
681 # setting this too low could make your server admins *very* unhappy
682 set server-cycle-wait 60
683
684 # how many seconds to wait for a response when connecting to a server
685 # before giving up and moving on?
686 set server-timeout 15
687
688 # if the number of servers on the net gets below this number, it will
689 # jump to a new server (ie, it will assume it's on the losing end of a
690 # netsplit) -- set to 0 to turn off
691 # [most irc networks use TS now, so it's to your advantage to turn this off]
692 set servlimit 0
693
694 # [0/1] check for stoned servers? (i.e. Where the server connection has
695 # died, but eggdrop hasn't been notified yet).
696 set check-stoned 1
697
698 # [0/1] enable console mode 'r'? this mode shows every raw message from the
699 # server to owners with console 'r' selected -- will take a bit more
700 # cpu.
701 # NOTE: This is a large security hole, allowing people to see mis-sent
702 # messages to the bot containing passwords
703 # This is now restricted to +n users only. Please choose your owners with care.
704 set use-console-r 0
705
706 # [0/1] enable logging of all information sent *to* a server, via console mode 'v'
707 # NOTE: This is a large security hole, allowing people to see passwords.
708 # This is now restricted to +n users only. Please choose your owners with care.
709 set debug-output 0
710
711 # [0/1] exit if the server sends a ERROR message?
712 set serverror-quit 1
713
714 # maximum number of lines to queue to the server.
715 # if you're going to dump large chunks of text to people over irc, you
716 # will probably want to raise this -- most people are fine at 300 though
717 set max-queue-msg 300
718
719 # [0/1] trigger bindings for ignored users?
720 set trigger-on-ignore 0
721
722 # [0/1] allow a msg being twice in a queue?
723 set double-mode 0
724 set double-server 0
725 set double-help 0
726
727 ##### SERVER MODULE - net-type 5 specific features (other networks) #####
728
729 # [0/1] some IRC Networks use the ircdu's SILENCE command
730 # else it is useless to use this
731 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
732 # Only use this if you set net-type 5
733 #set use-silence 1
734
735 # [0/1] some nets use umode +r to mean a restricted connection. If this is your
736 # case, and you want your bot to leave restricted servers and jump to the
737 # next one on his server list, then set it to 1.
738 # Automatically set to 0 for net-type 0/2/3/4, set to 1 for net-type 1.
739 # Only use this if you set net-type 5
740 #set check-mode-r 1
741
742
743
744 ##### CTCP MODULE #####
745
746 # this provides the normal ctcp replies that you'd expect *RECOMMENDED*
747 loadmodule ctcp
748
749 # several variables exist to better blend your egg in. they are
750 # ctcp-version, ctcp-finger, and ctcp-userinfo. you can use set
751 # to set them to values you like.
752
753 # [0/1/2] 0: normal behavior. 1: bot ignores all CTCPs, except for CTCP
754 # CHATs & PINGs requested by +o flag users. 2: bot doesn't answer more
755 # than C CTCPs in S seconds. C/S are defined by the set flood-ctcp C:S (cf
756 # server module)
757 set ctcp-mode 0
758
759 ##### IRC MODULE #####
760
761 # this module provides ALL NORMAL IRC INTERACTION, if you want the normal
762 # join & maintain channels stuff, this is the module.
763 loadmodule irc
764
765 # [0/1] define this if you want to bounce all server bans
766 set bounce-bans 1
767
768 # [0/1] define this if you want to bounce all the server modes
769 set bounce-modes 0
770
771 # [0/1] Do you want the bot to kick users who set bogus bans?
772 set kick-bogus-bans 1
773
774 # [0/1] Do you want the bot to remove bogus bans?
775 set bounce-bogus-bans 1
776
777 # If there are more than max-bans active bans on a channel, then the
778 # bot won't try to put more bans. Thus it won't flood the irc server.
779 # ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
780 set max-bans 20
781
782 # There is a global limit for +b/+e/+I modes. This limit is set to 30 on
783 # 2.10 irc servers.
784 set max-modes 30
785
786 # [0/1] define this to allow modes from non-op users (ChanServ)
787 set allow-desync 0
788
789 # [0/1] Do you want the bot to kick bogus usernames?
790 # Remember that if it does, as it won't ban them, it can be at the origin
791 # of a nice kick-flood
792 set kick-bogus 0
793
794 # [0/1] Do you want the bot to ban bogus usernames?
795 # Can prevent the above described kick-flood, but can also fill the banlist
796 set ban-bogus 0
797
798 # [0/1] Do you want the bot to kick for control character/ctcp avalanches
799 # to a channel?
800 # Remember that if it does, as it won't ban them, it can be at the origin
801 # of a nice kick-flood
802 set kick-fun 0
803
804 # [0/1] Do you want the bot to ban for control character/ctcp avalanches
805 # to a channel?
806 # Can prevent the above described kick-flood, but can also fill the banlist
807 set ban-fun 0
808
809 # [0/1] let users introduce themselves to the bot via 'hello'?
810 set learn-users 0
811
812 # time (in seconds) to wait for someone to return from a netsplit
813 set wait-split 300
814
815 # time (in seconds) that someone must have been off-channel before
816 # re-displaying their info
817 set wait-info 180
818
819 # this is the maximum number of bytes to send in the arguments to mode's
820 # sent to the server, most servers default this to 200, so it should
821 # be sufficient
822 set mode-buf-length 200
823
824 # many irc ops check for bots that respond to 'hello'. you can change this
825 # to another word by uncommenting the following two lines, and changing
826 # "myword" to the word you want to use instead of 'hello' (it must be a
827 # single word)
828 # novice users are not expected to understand what these two lines do; they
829 # are just here to help you. for more information on 'bind', check the file
830 # 'tcl-commands.doc'
831 #unbind msg - hello *msg:hello
832 #bind msg - myword *msg:hello
833
834 # Many takeover attempts occur due to lame users blindy /msg ident'n to
835 # the bot without checking if the bot is the bot.
836 # We now unbind this command by default to discourage them
837 unbind msg - ident *msg:ident
838 unbind msg - addhost *msg:addhost
839
840 # If you or your users use many different hosts and wants to
841 # be able to add it by /msg'ing you need to remove the
842 # unbind ident line above or bind it to another word.
843 #bind msg - myidentword *msg:ident
844
845 # [0/1] If you are so lame you want the bot to display peoples info lines, even
846 # when you are too lazy to add their chanrecs to a channel, set this to 1
847 # *NOTE* This means *every* user with an info line will have their info
848 # display on EVERY channel they join (provided they have been gone longer than
849 # wait-info)
850 set no-chanrec-info 0
851
852 # [0/1/2/3] Defines how the bot should punish bad users when revenging.
853 # 0 for deop - 1 for deop and +d - 2 for deop, +d and kick - 3 for deop,
854 # chattr +d, kick and ban. Default is 1.
855 set revenge-mode 1
856
857
858 ##### IRC MODULE - net-type 1 specific features (IRCnet) #####
859
860 # Don't modify the following settings if you don't use IRCnet. The defaults following
861 # values are harmless for you.
862
863 # [0/1] define this if you want to bounce all server exemptions (+e modes)
864 # * This is an IRCNET feature
865 set bounce-exempts 0
866
867 # [0/1] define this if you want to bounce all server invitations (+I modes)
868 # * This is an IRCNET feature
869 set bounce-invites 0
870
871 # If there are more than max-exempts active +e modes on a channel, then
872 # the bot won't try to put more exemptions. Thus it won't flood the irc
873 # server. Only 2.10 servers are concerned by these +e modes.
874 # * This is an IRCNET feature
875 set max-exempts 20
876
877 # If there are more than max-invites active +I modes on a channel, then
878 # the bot won't try to put more invitations. Thus it won't flood the irc
879 # server. Only 2.10 irc servers are concerned by these +I modes.
880 # * This is an IRCNET feature
881 set max-invites 20
882
883 # [0/1] Do you want the bot to remove bogus exempts?
884 set bounce-bogus-exempts 0
885
886 # [0/1] Do you want the bot to kick users who set bogus exempts?
887 set kick-bogus-exempts 0
888
889 # [0/1] Do you want the bot to remove bogus invites?
890 set bounce-bogus-invites 0
891
892 # [0/1] Do you want the bot to kick users who set bogus invites?
893 set kick-bogus-invites 0
894
895 # The following lines should be left uncommented unless the default values
896 # are being over-ridden. By default exempts and invites are on for IRCnet
897 # and hybrid EFnet, but off for all other networks. This behaviour can be
898 # modified by the following 2 flags. If you're network doesn't support e/I
899 # modes then you'll be unable to use these features.
900 #
901 # [0/1] Do you want to enable exempts?
902 # set use-exempts 0
903
904 # [0/1] Do you want to use invites?
905 # set use-invites 0
906
907 # [0/1] Prevent mixing normal modes and +I/+e invite modes?
908 # At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
909 # so leave this flag set to 1. The servers will probably change their
910 # behaviour in the future, so you should first check before accepting the
911 # default.
912 set prevent-mixing 1
913
914 ##### IRC MODULE - net-type 5 specific features (other networks) #####
915
916 # kick-method defines how kicks (when enforcing bans) should be made:
917 # 0 = kick all nicks at once in one command
918 # X = kick X users at a time
919 #
920 # Automatically set by net-type:
921 # net-type 0, 2, 3 & 4 sets this to 1
922 # net-type 1 sets this to 4
923 #
924 # If you use net-type 5, you must set this yourself (default is 1)
925 #set kick-method 1
926
927 # some networks allow you to stack lots of channel modes into one
928 # line.
929 # they're all guaranteed to support at least 3, so that's the default,
930 # but if you know your network supports more, you may want to adjust
931 # this value. this value must be less than or equal to 6.
932 # Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
933 # 6 for net-type 2/3.
934 # Only use this if you set net-type 5
935 #set modes-per-line 3
936
937 # [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
938 # exactly what's needed
939 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
940 # Only use this if you set net-type 5
941 #set use-354 0
942
943 # [0/1] use rfc 1459 compliant string matching routines?
944 # All networks apart from Dalnet comply with rfc 1459, so you should only
945 # disable it on Dalnet or networks which use Dalnet's code.
946 #set rfc-compliant 1
947
948
949
950 ##### TRANSFER MODULE #####
951
952 # uncomment this line to load the transfer module, this provides
953 # dcc send/get support and bot userfile transfer support (not sharing)
954 #loadmodule transfer
955
956 ##### variables:
957 # set maximum number of simultaneous downloads to allow for each user
958 set max-dloads 3
959
960 # set the block size for dcc transfers (ircII uses 512 bytes, but admits
961 # that may be too small -- 1024 is standard these days)
962 # set this to 0 to use turbo-dcc (recommended)
963 set dcc-block 1024
964
965 # [0/1] copy files into the /tmp directory before sending them? this is
966 # useful on most systems for file stability. (someone could move a file
967 # around while it's being downloaded, and mess up the transfer.) but if
968 # your directories are NFS mounted, it's a pain, and you'll want to set
969 # this to 0. If you are low on disk space, you may want to set this to 0.
970 set copy-to-tmp 1
971
972 # time (in seconds) that a dcc file transfer can remain inactive
973 # before being timed out
974 set xfer-timeout 30
975
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
1026 ##### FILESYSTEM MODULE #####
1027
1028 # uncomment this line to load the file system module, this provides
1029 # an area withing the bot where you can store files
1030 #loadmodule filesys
1031
1032 # this is the 'root' directory for the file system (set it to "" if you
1033 # don't want a file system)
1034 set files-path "/home/mydir/filesys"
1035
1036 # if you want to allow uploads, set this to the directory uploads should be
1037 # put into
1038 set incoming-path "/home/mydir/filesys/incoming"
1039
1040 # [0/1] alternately, you can set this, and uploads will go to the current
1041 # directory that a user is in
1042 set upload-to-pwd 0
1043
1044 # eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
1045 # to keep track of its own file system info -- if you can't do that (like
1046 # if the dcc path isn't owned by yours) or you just don't want it to do
1047 # that, specify a path here where you'd like all the database files to
1048 # be stored instead (otherwise, just leave it blank)
1049 set filedb-path ""
1050
1051 # set maximum number of people that can be in the file area at once
1052 # (0 to make it effectively infinite)
1053 set max-file-users 20
1054
1055 # maximum allowable file size that will be received, in K
1056 # (default is 1024K = 1M)
1057 set max-filesize 1024
1058
1059
1060
1061 ##### NOTES MODULE #####
1062
1063 # this provides support for storing of notes for users from each other
1064 # notes between currently online users is supported in the core, this is
1065 # only for storing the notes for later retrieval, direct user->user notes
1066 # are built-in
1067 loadmodule notes
1068
1069 # the notefile: where private notes between users are stored
1070 set notefile "LamestBot.notes"
1071
1072 # maximum number of notes to allow to be stored for each user
1073 # (to prevent flooding)
1074 set max-notes 50
1075
1076 # time (in days) to let stored notes live before expiring them
1077 set note-life 60
1078
1079 # [0/1] allow users to specify a forwarding address for forwarding notes
1080 # to another bot
1081 set allow-fwd 0
1082
1083 # [0/1] set this to 1 if you want the bot to let people know hourly if they
1084 # have any notes
1085 set notify-users 1
1086
1087 # [0/1] set this to 1 if you want the bot to let people know on join if they
1088 # have any notes
1089 set notify-onjoin 1
1090
1091 # comment out this next line, otherwise your bot won't start
1092 die "You didn't edit your config file like you were told, did you?"
1093
1094
1095
1096 ##### CONSOLE MODULE #####
1097
1098 # this module provides storage of console settings when you exit the bot
1099 # (or .store)
1100 loadmodule console
1101
1102 ##### variables:
1103 # [0/1] save users console settings automatically? (otherwise they have to use
1104 # .store)
1105 set console-autosave 1
1106
1107 # [0-99999] if a user doesn't have any console settings saved, which channel
1108 # do you want them automatically put on?
1109 set force-channel 0
1110
1111 # [0/1] display a user's global info line when they join a botnet channel?
1112 set info-party 0
1113
1114
1115
1116 ##### WOOBIE MODULE #####
1117
1118 # this serves absolutely no purpose and is for demonstrative
1119 # purposes only
1120 #loadmodule woobie
1121
1122
1123
1124 ##### SEEN MODULE #####
1125
1126 # this module provides seen commands via msg, on channel or via
1127 # dcc, similar to the various scripts
1128 #loadmodule seen
1129
1130
1131 ##### BLOWFISH MODULE #####
1132
1133 ##### IF YOU DONT READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
1134
1135 # Choose your encryption method now, 'cause once you do, it ain't
1136 # changing 'til you get a new userfile, capish? At the moment, there
1137 # is only one encryption option: blowfish
1138
1139 # uncomment this line to load blowfish, the encryption module
1140 # for the bot, it will not start without it loaded and commented out
1141 # to make sure you read the whole config file
1142 # this is checkmodule, because during .restart the module will already
1143 # be loaded
1144 #checkmodule blowfish
1145
1146
1147
1148 ##### ASSOC MODULE #####
1149
1150 # uncomment this line to load assoc support, i.e naming channels on
1151 # the botnet
1152 #loadmodule assoc
1153
1154
1155
1156 ##### WIRE MODULE #####
1157
1158 # this module provides all the standard .wire commands via dcc.
1159 # it's an encrypted partyline communication tool, compatible with wire.tcl
1160 # uncomment this line to load it
1161 #loadmodule wire
1162
1163
1164
1165 ##### SCRIPTS #####
1166
1167 # these are some commonly loaded (and needed) scripts.
1168 source scripts/alltools.tcl
1169 source scripts/action.fix.tcl
1170
1171 #this script provides many usefull minor informational commands
1172 # (like setting users url's, email address, etc) you can modify
1173 # it to add extra entries, you might also want to modify help/userinfo.help
1174 # and help/msg/userinfo.help to change the help files
1175 source scripts/userinfo1.0.tcl
1176 loadhelp userinfo.help
1177

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23