/[cvs]/eggdrop1.6/eggdrop.conf.dist
ViewVC logotype

Contents of /eggdrop1.6/eggdrop.conf.dist

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.18 - (show annotations) (download)
Sun Jan 9 14:36:53 2000 UTC (20 years, 9 months ago) by fabian
Branch: MAIN
Changes since 1.17: +5 -3 lines
Johoho's config patch

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23