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

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

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


Revision 1.26 - (show annotations) (download)
Wed Mar 22 00:33:57 2000 UTC (19 years ago) by fabian
Branch: MAIN
CVS Tags: HEAD
Changes since 1.25: +1 -1 lines
FILE REMOVED
Wiktor's settingsdoc patch

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23