/[cvs]/eggdrop-alpha/eggdrop.complete.conf
ViewVC logotype

Contents of /eggdrop-alpha/eggdrop.complete.conf

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


Revision 1.5 - (show annotations) (download)
Wed Jul 18 06:20:55 2001 UTC (17 years, 5 months ago) by tothwolf
Branch: MAIN
CVS Tags: HEAD
Changes since 1.4: +57 -53 lines
sync with 1.6.6-CVS-995399486

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23