/[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.5 - (show annotations) (download)
Sat May 13 14:46:45 2000 UTC (19 years, 5 months ago) by johoho
Branch: MAIN
Changes since 1.4: +1 -13 lines
removed private-owner

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23