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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23