/[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.5 - (show annotations) (download)
Thu Jun 24 20:41:06 1999 UTC (20 years, 11 months ago) by segfault
Branch: MAIN
Changes since 1.4: +3 -2 lines
Small fixes to bugs in Fabian's telnet-banner patch

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23