/[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.17 - (show annotations) (download)
Thu Jan 6 19:46:54 2000 UTC (20 years, 9 months ago) by fabian
Branch: MAIN
Changes since 1.16: +12 -1 lines
userfile_perm 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.16 2000/01/01 19:08:46 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.4.xx/ 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 }
467
468 set global-chanmode "nt"
469
470 # do this for each channel you wish to sit on:
471 # NOTE: for some reason Tcl won't let you put comments inside { } -- so
472 # don't try it, cos it'll mess up your channel definition
473
474 channel add #lamest {
475 chanmode "+nt-likm"
476 idle-kick 0
477 need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
478 need-invite { putserv "PRIVMSG #lamest :let me in!" }
479 need-key { putserv "PRIVMSG #lamest :let me in!" }
480 need-unban { putserv "PRIVMSG #lamest :let me in!" }
481 need-limit { putserv "PRIVMSG #lamest :let me in!" }
482 flood-chan 10:60
483 flood-deop 3:10
484 flood-kick 3:10
485 flood-join 5:60
486 flood-ctcp 3:60
487 }
488
489 # the things inside the { } are CHANNEL OPTIONS -- they can be set within
490 # the "channel add" command, or by using a "channel set" command as in the
491 # examples below. they list all the options you can set for a channel.
492
493 # chanmode
494 # what modes will be enforced? '+' modes will always be kept on, '-' modes
495 # will always be kept off
496 # idle-kick
497 # kick channel members after how many minutes of being idle?
498 # (leave out to disable, or set to 0)
499 # need-op
500 # script to run (if any) when the bot needs to be op'd on this channel
501 # need-invite
502 # script to run (if any) when the bot gets locked out of the channel
503 # because the channel is +i
504 # need-key
505 # script to run (if any) when the bot gets locked out of the channel
506 # because it doesn't have the channel key
507 # need-unban
508 # script to run (if any) when the bot gets banned from this channel
509 # need-limit
510 # script to run (if any) when the bot gets locked out of the channel
511 # because the channel limit is full
512 # flood-chan (number:seconds)
513 # how many channel messages in hom many seconds is a flood
514 # not specifying or using number = 0 will not check chan floods!
515 # flood-ctcp (number:seconds)
516 # how many channel messages in hom many seconds is a flood
517 # not specifying or using number = 0 will not check ctcp floods!
518 # flood-deop (number:seconds)
519 # how many deops in how many seconds is a mass de-op
520 # not specifying or using number = 0 will not check de-op floods!
521 # flood-kick (number:seconds)
522 # how many kicks in how many seconds is a mass kick?
523 # not specifying or using number = 0 will not check mass kicks!
524 # flood-join (number:seconds)
525 # how many joins/nick changes in how many seconds is a join flood?
526 # not specifying or using number = 0 will not check join floods!
527
528 # note that "need-op", "need-invite", etc, are limited to 120 characters,
529 # so if you want to so something more complicated, just write a proc,
530 # and make them call your proc.
531
532 # there are also a lot of options that can be turned on or off for each
533 # channel. to turn an option on, put a + in front of it. to turn it off,
534 # put a - in front of it. ie, to have auto-op, put:
535 # +autoop
536 # to turn it off, put:
537 # -autoop
538
539 # clear all channel bans when the bot joins? (ie, force the channel's
540 # ban list to match the bot's internal list)
541 channel set #lamest -clearbans
542
543 # when a ban is set, kick people who are on the channel and match the
544 # new ban? (ie, they were on the channel before the ban)
545 channel set #lamest +enforcebans
546
547 # only activate bans on the channel when necessary? (this keeps the
548 # channel's ban list from getting excessively long. the bot still remem-
549 # bers every ban, but it only activates a ban on the channel when it sees
550 # someone join who matches that ban.)
551 channel set #lamest +dynamicbans
552
553 # allow bans to be made by users directly? (if turned off, the bot will
554 # require all bans to be made through the bot's console)
555 channel set #lamest +userbans
556
557 # only activate exempts on the channel when necessary? (this keeps the
558 # channel's exempt list from getting excessively long. the bot still
559 # remembers every exempt, but it only activates a exempt on the channel
560 # when it sees a ban set matching the exempt. The exempt remains active
561 # on the channel for as long as the ban is still active.
562 channel set #lamest +dynamicexempts
563
564 # allow exempts to be made by users directly? (if turned off, the bot will
565 # require all exempts to be made through the bot's console)
566 channel set #lamest +userexempts
567
568 # only activate invites on the channel when necessary? (this keeps the
569 # channel's invite list from getting excessively long. the bot still
570 # remembers every invite, but the invites are only activated when the
571 # channel is set to invite only and a user joins aftre requesting an
572 # invite. Once set the invite remains until the channel goes to -i
573 channel set #lamest +dynamicinvites
574
575 # allow invites to be made by users directly? (if turned off, the bot will
576 # require all invites to be made through the bot's console)
577 channel set #lamest +userinvites
578
579 # op users with the +o (op) flag as soon as they join the channel?
580 # (hint: this is a BAD IDEA)
581 channel set #lamest -autoop
582
583 # only let users with +o (op) flag be channel ops?
584 channel set #lamest -bitch
585
586 # say a user's info line when they join the channel?
587 channel set #lamest +greet
588
589 # re-op a user with the +o (op) flag if they get deopped?
590 channel set #lamest +protectops
591
592 # re-op a user with the +f (friend) flag if they get deopped?
593 channel set #lamest +protectfriends
594
595 # log the channel status line every 5 minutes? (some people think
596 # it's annoying; i think it's neat)
597 channel set #lamest +statuslog
598
599 # de-op someone that enters the channel with server ops (ie, netsplit
600 # ops) when they didn't have them before the split?
601 channel set #lamest +stopnethack
602
603 # remember people who deop/kick/ban the bot or valid ops, and punish them?
604 # users with +f (friend) flag are exempt from revenge
605 channel set #lamest +revenge
606
607 # voice users with +v (voice) flag when they join the channel?
608 channel set #lamest +autovoice
609
610 # prevent this channel from being listed on the botnet? (for paranoid
611 # people)
612 channel set #lamest -secret
613
614 # share user channel info for this channel?
615 channel set #lamest -shared
616
617 # cycle the channel when it becomes op-less?
618 channel set #lamest +cycle
619
620 # do you want the bot not to be able to kick +o flag users ?
621 # letting them kick-flood for instance, to protect the channel agaisnt
622 # clone attacks
623 channel set #lamest +dontkickops
624
625 # during net-rejoins does a wasop test for +stopnethack (same as +w user
626 # flag, but affects a whole channel)
627 channel set #lamest -wasoptest
628
629 # prevents the bot from joining the channel (or makes it leave the channel
630 # if it is already there).
631 # Can be useful to make the bot leave a channel without loosing it's
632 # settings (flood settings, all these "channel set" settings), user flags
633 # for this channel, bans for this channel, and without affecting any
634 # sharing
635 channel set #lamest -inactive
636
637 # respond to seen requests in the channel? (seen module must be loaded)
638 channel set #lamest -seen
639
640 # allow non-ops to perform channel modes? (Stops bot from
641 # fighting with services such as ChanServ)
642 channel set #lamest +nodesynch
643
644 # here's a shorter example:
645 channel add #botcentral {
646 chanmode "+mntisl 1"
647 idle-kick 1
648 }
649 channel set #botcentral +bitch +clearbans +enforcebans -greet +revenge
650
651
652 ##### SERVER MODULE #####
653
654 # this provides the core server support (removing this is equivalent to
655 # the old NO_IRC define)
656 loadmodule server
657
658 # [0/1/2/3/4/5] What is your network?
659 # 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
660 # 4 = Efnet +e/+I hybrid, 5 = Others
661 set net-type 0
662
663 ##### variables:
664 # the nick of the bot, that which it uses on IRC, and on the botnet
665 # unless you specify a sperate botnet-nick
666 set nick "Lamestbot"
667
668 # an alternative nick to use if the nick specified by 'set nick' is
669 # unavailable. All '?' characters will be replaced by a random number.
670 set altnick "Llamabot"
671
672 # what to display in the real-name field for the bot
673 set realname "/msg LamestBot hello"
674
675 # script to run (if any) when first connecting to a server
676 set init-server { putserv "MODE $botnick +i-ws" }
677
678 # the server list -- the bot will start at the first server listed, and cycle
679 # through them whenever it's disconnected
680 # (please note: you need to change these servers to YOUR network's servers)
681 set servers {
682 you.need.to.change.this:6667
683 }
684
685 # [0/1] if the bot's nickname is changed (for example, if the intended
686 # nickname is already in use) keep trying to get the nick back?
687 set keep-nick 1
688
689 # [0/1] use /ison instead of /trace to see if our botnick is free or being
690 # used? (note: some irc admins, look for excessive use of /trace)
691 set use-ison 1
692
693 # [0/1] if this is set, a leading '~' on user@hosts WON'T be stripped off
694 set strict-host 0
695
696 # [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
697 # Normally it tells the DCC user that the CHAT or SEND has been rejected
698 # because they don't have access, but sometimes IRC server operators
699 # detect bots that way.
700 set quiet-reject 1
701
702 # [0/1] answer lower case ctcp's (non rfc compliant)
703 # mIRC will do this, most other clients will NOT
704 set lowercase-ctcp 0
705
706 # answer HOW MANY stacked ctcp's at once
707 set answer-ctcp 3
708
709 # setting any of the following with howmany == 0 will turn them off
710 # how many msgs in how many seconds from the same host constitutes a flood?
711 set flood-msg 5:60
712 # how many CTCPs in how many seconds?
713 set flood-ctcp 3:60
714
715 # [0/1] even if all the servers are down, cycle forever and keep trying to
716 # connect?
717 set never-give-up 1
718
719 # [0/1] If this setting is 0 then the eggdrop keeps a seperate list of the names
720 # irc servers call themselves, retaining what you entered in the config file.
721 # setting it to 1 will cause the bot to replace your entry with what
722 # the server actually calls itself
723 set strict-servernames 0
724
725 # if no port is specified on a .jump, which port should I use?
726 set default-port 6667
727
728 # number of seconds to wait between each server connect (0 = no wait)
729 # useful for preventing ircu throttling
730 # setting this too low could make your server admins *very* unhappy
731 set server-cycle-wait 60
732
733 # how many seconds to wait for a response when connecting to a server
734 # before giving up and moving on?
735 set server-timeout 15
736
737 # if the number of servers on the net gets below this number, it will
738 # jump to a new server (ie, it will assume it's on the losing end of a
739 # netsplit) -- set to 0 to turn off
740 # [most irc networks use TS now, so it's to your advantage to turn this off]
741 set servlimit 0
742
743 # [0/1] check for stoned servers? (i.e. Where the server connection has
744 # died, but eggdrop hasn't been notified yet).
745 set check-stoned 1
746
747 # [0/1] enable console mode 'r'? this mode shows every raw message from the
748 # server to owners with console 'r' selected -- will take a bit more
749 # cpu.
750 # NOTE: This is a large security hole, allowing people to see mis-sent
751 # messages to the bot containing passwords
752 # This is now restricted to +n users only. Please choose your owners with care.
753 set use-console-r 0
754
755 # [0/1] enable logging of all information sent *to* a server, via console mode 'v'
756 # NOTE: This is a large security hole, allowing people to see passwords.
757 # This is now restricted to +n users only. Please choose your owners with care.
758 set debug-output 0
759
760 # [0/1] exit if the server sends a ERROR message?
761 set serverror-quit 1
762
763 # maximum number of lines to queue to the server.
764 # if you're going to dump large chunks of text to people over irc, you
765 # will probably want to raise this -- most people are fine at 300 though
766 set max-queue-msg 300
767
768 # [0/1] trigger bindings for ignored users?
769 set trigger-on-ignore 0
770
771 # [0/1] allow a msg being twice in a queue?
772 set double-mode 0
773 set double-server 0
774 set double-help 0
775
776 ##### SERVER MODULE - net-type 5 specific features (other networks) #####
777
778 # [0/1] some IRC Networks use the ircdu's SILENCE command
779 # else it is useless to use this
780 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
781 # Only use this if you set net-type 5
782 #set use-silence 1
783
784 # [0/1] some nets use umode +r to mean a restricted connection. If this is your
785 # case, and you want your bot to leave restricted servers and jump to the
786 # next one on his server list, then set it to 1.
787 # Automatically set to 0 for net-type 0/2/3/4, set to 1 for net-type 1.
788 # Only use this if you set net-type 5
789 #set check-mode-r 1
790
791 # This variable sets the maximum nick length allowed on the network. Most
792 # only support 9. The maximum supported by eggdrop is 32.
793 #set nick-len 9
794
795 ##### CTCP MODULE #####
796
797 # this provides the normal ctcp replies that you'd expect *RECOMMENDED*
798 loadmodule ctcp
799
800 # several variables exist to better blend your egg in. they are
801 # ctcp-version, ctcp-finger, and ctcp-userinfo. you can use set
802 # to set them to values you like.
803
804 # [0/1/2] 0: normal behavior. 1: bot ignores all CTCPs, except for CTCP
805 # CHATs & PINGs requested by +o flag users. 2: bot doesn't answer more
806 # than C CTCPs in S seconds. C/S are defined by the set flood-ctcp C:S (cf
807 # server module)
808 set ctcp-mode 0
809
810
811 ##### IRC MODULE #####
812
813 # this module provides ALL NORMAL IRC INTERACTION, if you want the normal
814 # join & maintain channels stuff, this is the module.
815 loadmodule irc
816
817 # [0/1] define this if you want to bounce all server bans
818 set bounce-bans 1
819
820 # [0/1] define this if you want to bounce all the server modes
821 set bounce-modes 0
822
823 # [0/1] Do you want the bot to kick users who set bogus bans?
824 set kick-bogus-bans 1
825
826 # [0/1] Do you want the bot to remove bogus bans?
827 set bounce-bogus-bans 1
828
829 # If there are more than max-bans active bans on a channel, then the
830 # bot won't try to put more bans. Thus it won't flood the irc server.
831 # ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
832 set max-bans 20
833
834 # There is a global limit for +b/+e/+I modes. This limit is set to 30 on
835 # 2.10 irc servers.
836 set max-modes 30
837
838 # [0/1] Do you want the bot to kick bogus usernames?
839 # Remember that if it does, as it won't ban them, it can be at the origin
840 # of a nice kick-flood
841 set kick-bogus 0
842
843 # [0/1] Do you want the bot to ban bogus usernames?
844 # Can prevent the above described kick-flood, but can also fill the banlist
845 set ban-bogus 0
846
847 # [0/1] Do you want the bot to kick for control character/ctcp avalanches
848 # to a channel?
849 # Remember that if it does, as it won't ban them, it can be at the origin
850 # of a nice kick-flood
851 set kick-fun 0
852
853 # [0/1] Do you want the bot to ban for control character/ctcp avalanches
854 # to a channel?
855 # Can prevent the above described kick-flood, but can also fill the banlist
856 set ban-fun 0
857
858 # [0/1] let users introduce themselves to the bot via 'hello'?
859 set learn-users 0
860
861 # time (in seconds) to wait for someone to return from a netsplit
862 set wait-split 600
863
864 # time (in seconds) that someone must have been off-channel before
865 # re-displaying their info
866 set wait-info 180
867
868 # this is the maximum number of bytes to send in the arguments to mode's
869 # sent to the server, most servers default this to 200, so it should
870 # be sufficient
871 set mode-buf-length 200
872
873 # many irc ops check for bots that respond to 'hello'. you can change this
874 # to another word by uncommenting the following two lines, and changing
875 # "myword" to the word you want to use instead of 'hello' (it must be a
876 # single word)
877 # novice users are not expected to understand what these two lines do; they
878 # are just here to help you. for more information on 'bind', check the file
879 # 'tcl-commands.doc'
880 #unbind msg - hello *msg:hello
881 #bind msg - myword *msg:hello
882
883 # Many takeover attempts occur due to lame users blindy /msg ident'n to
884 # the bot without checking if the bot is the bot.
885 # We now unbind this command by default to discourage them
886 unbind msg - ident *msg:ident
887 unbind msg - addhost *msg:addhost
888
889 # If you or your users use many different hosts and wants to
890 # be able to add it by /msg'ing you need to remove the
891 # unbind ident line above or bind it to another word.
892 #bind msg - myidentword *msg:ident
893
894 # [0/1] If you are so lame you want the bot to display peoples info lines, even
895 # when you are too lazy to add their chanrecs to a channel, set this to 1
896 # *NOTE* This means *every* user with an info line will have their info
897 # display on EVERY channel they join (provided they have been gone longer than
898 # wait-info)
899 set no-chanrec-info 0
900
901 # [0/1/2/3] Defines how the bot should punish bad users when revenging.
902 # 0 for deop - 1 for deop and +d - 2 for deop, +d and kick - 3 for deop,
903 # chattr +d, kick and ban. Default is 1.
904 set revenge-mode 1
905
906 ##### IRC MODULE - net-type 1 specific features (IRCnet) #####
907
908 # Don't modify the following settings if you don't use IRCnet. The defaults following
909 # values are harmless for you.
910
911 # [0/1] define this if you want to bounce all server exemptions (+e modes)
912 # * This is an IRCNET feature
913 set bounce-exempts 0
914
915 # [0/1] define this if you want to bounce all server invitations (+I modes)
916 # * This is an IRCNET feature
917 set bounce-invites 0
918
919 # If there are more than max-exempts active +e modes on a channel, then
920 # the bot won't try to put more exemptions. Thus it won't flood the irc
921 # server. Only 2.10 servers are concerned by these +e modes.
922 # * This is an IRCNET feature
923 set max-exempts 20
924
925 # If there are more than max-invites active +I modes on a channel, then
926 # the bot won't try to put more invitations. Thus it won't flood the irc
927 # server. Only 2.10 irc servers are concerned by these +I modes.
928 # * This is an IRCNET feature
929 set max-invites 20
930
931 # [0/1] Do you want the bot to remove bogus exempts?
932 set bounce-bogus-exempts 0
933
934 # [0/1] Do you want the bot to kick users who set bogus exempts?
935 set kick-bogus-exempts 0
936
937 # [0/1] Do you want the bot to remove bogus invites?
938 set bounce-bogus-invites 0
939
940 # [0/1] Do you want the bot to kick users who set bogus invites?
941 set kick-bogus-invites 0
942
943 # The following lines should be left uncommented unless the default values
944 # are being over-ridden. By default exempts and invites are on for IRCnet
945 # and hybrid EFnet, but off for all other networks. This behaviour can be
946 # modified by the following 2 flags. If you're network doesn't support e/I
947 # modes then you'll be unable to use these features.
948 #
949 # [0/1] Do you want to enable exempts?
950 # set use-exempts 0
951
952 # [0/1] Do you want to use invites?
953 # set use-invites 0
954
955 # [0/1] Prevent mixing normal modes and +I/+e invite modes?
956 # At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
957 # so leave this flag set to 1. The servers will probably change their
958 # behaviour in the future, so you should first check before accepting the
959 # default.
960 set prevent-mixing 1
961
962 ##### IRC MODULE - net-type 5 specific features (other networks) #####
963
964 # kick-method defines how kicks (when enforcing bans) should be made:
965 # 0 = kick all nicks at once in one command
966 # X = kick X users at a time
967 #
968 # Automatically set by net-type:
969 # net-type 0, 2, 3 & 4 sets this to 1
970 # net-type 1 sets this to 4
971 #
972 # If you use net-type 5, you must set this yourself (default is 1)
973 #set kick-method 1
974
975 # some networks allow you to stack lots of channel modes into one
976 # line.
977 # they're all guaranteed to support at least 3, so that's the default,
978 # but if you know your network supports more, you may want to adjust
979 # this value. this value must be less than or equal to 6.
980 # Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
981 # 6 for net-type 2/3.
982 # Only use this if you set net-type 5
983 #set modes-per-line 3
984
985 # [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
986 # exactly what's needed
987 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
988 # Only use this if you set net-type 5
989 #set use-354 0
990
991 # [0/1] use rfc 1459 compliant string matching routines?
992 # All networks apart from Dalnet comply with rfc 1459, so you should only
993 # disable it on Dalnet or networks which use Dalnet's code.
994 #set rfc-compliant 1
995
996
997 ##### TRANSFER MODULE #####
998
999 # uncomment this line to load the transfer module, this provides
1000 # dcc send/get support and bot userfile transfer support (not sharing)
1001 #loadmodule transfer
1002
1003 ##### variables:
1004 # set maximum number of simultaneous downloads to allow for each user
1005 set max-dloads 3
1006
1007 # set the block size for dcc transfers (ircII uses 512 bytes, but admits
1008 # that may be too small -- 1024 is standard these days)
1009 # set this to 0 to use turbo-dcc (recommended)
1010 set dcc-block 1024
1011
1012 # [0/1] copy files into the /tmp directory before sending them? this is
1013 # useful on most systems for file stability. (someone could move a file
1014 # around while it's being downloaded, and mess up the transfer.) but if
1015 # your directories are NFS mounted, it's a pain, and you'll want to set
1016 # this to 0. If you are low on disk space, you may want to set this to 0.
1017 set copy-to-tmp 1
1018
1019 # time (in seconds) that a dcc file transfer can remain inactive
1020 # before being timed out
1021 set xfer-timeout 30
1022
1023
1024 ##### SHARE MODULE #####
1025
1026 # this provides the userfile sharing support
1027 # (this requires the channels & transfer modules)
1028 #loadmodule share
1029
1030 ##### variables:
1031 # [0/1] When two bots get disconnected this flag allows them to create
1032 # a resync buffer which saves all changes done to the userfile during
1033 # the disconnect. So, when they reconnect, they will not have to transfer
1034 # the complete user file, but instead, just send the resync buffer.
1035 # If you have problems with this feature please tell us. Take a look at
1036 # doc/BUG-REPORT first though.
1037 #set allow-resync 0
1038
1039 # this specifies how long to hold another bots resync data for before
1040 # flushing it
1041 #set resync-time 900
1042
1043 # [0/1] when sharing user lists, ignore +n modes from other bots?
1044 #
1045 # PLEASE NOTE!
1046 #
1047 # With the addition of private-globals, private-owner is now redundant,
1048 # and therefore deprecated. It may be removed soon. Put the global
1049 # owner flag in private-globals for the same effect.
1050 #
1051 # NOTE: every slave will need to have 'set owner ...' or
1052 # they will lose their owners when they download the user list
1053 #set private-owner 0
1054
1055 # [0/1] when sharing user lists, DONT ACCEPT global flag changes from other bots?
1056 # NOTE: the bot will still send changes made on the bot, it just wont accept
1057 # any global flag changes from other bots
1058 #set private-global 0
1059
1060 # when sharing user lists, if private-global isn't set, which global flag
1061 # changes from other bots should be ignored ?
1062 #set private-globals "mnot"
1063
1064 # [0/1] when sharing user lists, DON'T ACCEPT any userfile changes from other
1065 # bots?
1066 # NOTE: paranoid people should use this feature on their hub bot - this
1067 # will force all +host/+user/chpass/etc. changes to be made via the hub
1068 #set private-user 0
1069
1070 # [0/1] this setting makes the bot discard it's own bot records in favor of
1071 # the ones sent by the hub. Note: This only works with hubs that are v1.5.1
1072 # _or higher_.
1073 #set override-bots 0
1074
1075
1076 ##### FILESYSTEM MODULE #####
1077
1078 # uncomment this line to load the file system module, this provides
1079 # an area withing the bot where you can store files
1080 #loadmodule filesys
1081
1082 # this is the 'root' directory for the file system (set it to "" if you
1083 # don't want a file system)
1084 set files-path "/home/mydir/filesys"
1085
1086 # if you want to allow uploads, set this to the directory uploads should be
1087 # put into
1088 set incoming-path "/home/mydir/filesys/incoming"
1089
1090 # [0/1] alternately, you can set this, and uploads will go to the current
1091 # directory that a user is in
1092 set upload-to-pwd 0
1093
1094 # eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
1095 # to keep track of its own file system info -- if you can't do that (like
1096 # if the dcc path isn't owned by yours) or you just don't want it to do
1097 # that, specify a path here where you'd like all the database files to
1098 # be stored instead (otherwise, just leave it blank)
1099 set filedb-path ""
1100
1101 # set maximum number of people that can be in the file area at once
1102 # (0 to make it effectively infinite)
1103 set max-file-users 20
1104
1105 # maximum allowable file size that will be received, in K
1106 # (default is 1024K = 1M)
1107 set max-filesize 1024
1108
1109
1110 ##### NOTES MODULE #####
1111
1112 # this provides support for storing of notes for users from each other
1113 # notes between currently online users is supported in the core, this is
1114 # only for storing the notes for later retrieval, direct user->user notes
1115 # are built-in
1116 loadmodule notes
1117
1118 # the notefile: where private notes between users are stored
1119 set notefile "LamestBot.notes"
1120
1121 # maximum number of notes to allow to be stored for each user
1122 # (to prevent flooding)
1123 set max-notes 50
1124
1125 # time (in days) to let stored notes live before expiring them
1126 set note-life 60
1127
1128 # [0/1] allow users to specify a forwarding address for forwarding notes
1129 # to another bot
1130 set allow-fwd 0
1131
1132 # [0/1] set this to 1 if you want the bot to let people know hourly if they
1133 # have any notes
1134 set notify-users 1
1135
1136 # [0/1] set this to 1 if you want the bot to let people know on join if they
1137 # have any notes
1138 set notify-onjoin 1
1139
1140 # comment out this next line, otherwise your bot won't start
1141 die "You didn't edit your config file like you were told, did you?"
1142
1143
1144 ##### CONSOLE MODULE #####
1145
1146 # this module provides storage of console settings when you exit the bot
1147 # (or .store)
1148 loadmodule console
1149
1150 ##### variables:
1151 # [0/1] save users console settings automatically? (otherwise they have to use
1152 # .store)
1153 set console-autosave 1
1154
1155 # [0-99999] if a user doesn't have any console settings saved, which channel
1156 # do you want them automatically put on?
1157 set force-channel 0
1158
1159 # [0/1] display a user's global info line when they join a botnet channel?
1160 set info-party 0
1161
1162
1163 ##### WOOBIE MODULE #####
1164
1165 # this serves absolutely no purpose and is for demonstrative
1166 # purposes only
1167 #loadmodule woobie
1168
1169
1170 ##### SEEN MODULE #####
1171
1172 # this module provides seen commands via msg, on channel or via
1173 # dcc, similar to the various scripts
1174 #loadmodule seen
1175
1176
1177 ##### BLOWFISH MODULE #####
1178
1179 ##### IF YOU DONT READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
1180
1181 # Choose your encryption method now, 'cause once you do, it ain't
1182 # changing 'til you get a new userfile, capish? At the moment, there
1183 # is only one encryption option: blowfish
1184
1185 # uncomment this line to load blowfish, the encryption module
1186 # for the bot, it will not start without it loaded and commented out
1187 # to make sure you read the whole config file
1188 # this is checkmodule, because during .restart the module will already
1189 # be loaded
1190 #checkmodule blowfish
1191
1192
1193 ##### ASSOC MODULE #####
1194
1195 # uncomment this line to load assoc support, i.e naming channels on
1196 # the botnet
1197 #loadmodule assoc
1198
1199
1200 ##### WIRE MODULE #####
1201
1202 # this module provides all the standard .wire commands via dcc.
1203 # it's an encrypted partyline communication tool, compatible with wire.tcl
1204 # uncomment this line to load it
1205 #loadmodule wire
1206
1207
1208 ##### SCRIPTS #####
1209
1210 # these are some commonly loaded (and needed) scripts.
1211 source scripts/alltools.tcl
1212 source scripts/action.fix.tcl
1213
1214 # This script provides many usefull minor informational commands
1215 # (like setting users url's, email address, etc). You can modify
1216 # it to add extra entries, you might also want to modify help/userinfo.help
1217 # and help/msg/userinfo.help to change the help files.
1218 source scripts/userinfo1.0.tcl
1219 loadhelp userinfo.help

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23