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

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

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


Revision 1.1 - (show annotations) (download)
Wed Mar 22 00:33:57 2000 UTC (19 years, 7 months ago) by fabian
Branch: MAIN
Wiktor's settingsdoc patch

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23