/[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.21 - (show annotations) (download)
Fri Sep 3 16:37:40 1999 UTC (21 years, 7 months ago) by arthur2
Branch: MAIN
Changes since 1.20: +1 -1 lines
eggdrop1.3.29cvs+configpatch2

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23