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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23