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

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

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


Revision 1.36 - (show annotations) (download)
Sat Dec 8 18:16:03 2001 UTC (17 years, 10 months ago) by guppy
Branch: MAIN
Changes since 1.35: +3 -2 lines
added BarkerJr's uptime doc

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23