/[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.12 - (show annotations) (download)
Sun Aug 20 12:27:15 2000 UTC (19 years, 1 month ago) by johoho
Branch: MAIN
CVS Tags: eggdrop105040
Changes since 1.11: +6 -2 lines
documentation update

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.11 2000/08/03 21:51:32 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 "04May2000". "%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-idle-kick 0
385
386 set global-chanset {
387 -clearbans -enforcebans
388 +dynamicbans +userbans
389 -autoop -bitch
390 +greet +protectops
391 +statuslog -revenge
392 -secret -autovoice
393 +cycle +dontkickops
394 -inactive -protectfriends
395 +shared -seen
396 +userexempts +dynamicexempts
397 +userinvites +dynamicinvites
398 -nodesynch
399 }
400
401 set global-chanmode "nt"
402
403 set global-stopnethack-mode 0
404
405 # do this for each channel you wish to sit on:
406 # NOTE: for some reason Tcl won't let you put comments inside { } -- so
407 # don't try it, cos it'll mess up your channel definition
408
409 channel add #lamest {
410 chanmode "+nt-likm"
411 idle-kick 0
412 stopnethack-mode 0
413 need-op { putserv "PRIVMSG #lamest :op me cos i'm lame!" }
414 need-invite { putserv "PRIVMSG #lamest :let me in!" }
415 need-key { putserv "PRIVMSG #lamest :let me in!" }
416 need-unban { putserv "PRIVMSG #lamest :let me in!" }
417 need-limit { putserv "PRIVMSG #lamest :let me in!" }
418 flood-chan 10:60
419 flood-deop 3:10
420 flood-kick 3:10
421 flood-join 5:60
422 flood-ctcp 3:60
423 flood-nick 5:60
424 }
425
426 # the things inside the { } are CHANNEL OPTIONS -- they can be set within
427 # the "channel add" command, or by using a "channel set" command as in the
428 # examples below. they list all the options you can set for a channel.
429
430 # chanmode
431 # what modes will be enforced? '+' modes will always be kept on, '-' modes
432 # will always be kept off
433 # idle-kick
434 # kick channel members after how many minutes of being idle?
435 # (leave out to disable, or set to 0)
436
437 # stopnethack-mode
438 # de-op anyone who enters the channel with serverops
439 # 0 turn off,
440 # 1 isoptest (allow serverop if registered op),
441 # 2 wasoptest (allow serverop if op before split)
442 # 3 allow serverop if isop or wasop
443 # 4 allow serverop if isop and wasop
444 # 5 if channel -bitch: see stopnethack-mode 3
445 # if channel +bitch: see stopnethack-mode 1
446 # 6 if channel -bitch: see stopnethack-mode 2
447 # if channel +bitch: see stopnethack-mode 4
448
449 # need-op
450 # script to run (if any) when the bot needs to be op'd on this channel
451 # need-invite
452 # script to run (if any) when the bot gets locked out of the channel
453 # because the channel is +i
454 # need-key
455 # script to run (if any) when the bot gets locked out of the channel
456 # because it doesn't have the channel key
457 # need-unban
458 # script to run (if any) when the bot gets banned from this channel
459 # need-limit
460 # script to run (if any) when the bot gets locked out of the channel
461 # because the channel limit is full
462 # flood-chan (number:seconds)
463 # how many channel messages in how many seconds is a flood
464 # not specifying or using number = 0 will not check chan floods!
465 # flood-ctcp (number:seconds)
466 # how many channel messages in how many seconds is a flood
467 # not specifying or using number = 0 will not check ctcp floods!
468 # flood-deop (number:seconds)
469 # how many deops in how many seconds is a mass de-op
470 # not specifying or using number = 0 will not check de-op floods!
471 # flood-kick (number:seconds)
472 # how many kicks in how many seconds is a mass kick?
473 # not specifying or using number = 0 will not check mass kicks!
474 # flood-join (number:seconds)
475 # how many joins/nick changes in how many seconds is a join flood?
476 # not specifying or using number = 0 will not check join floods!
477
478 # note that "need-op", "need-invite", etc, are limited to 120 characters,
479 # so if you want to so something more complicated, just write a proc,
480 # and make them call your proc.
481
482 # there are also a lot of options that can be turned on or off for each
483 # channel. to turn an option on, put a + in front of it. to turn it off,
484 # put a - in front of it. i.e., to have auto-op, put:
485 # +autoop
486 # to turn it off, put:
487 # -autoop
488
489 # clear all channel bans when the bot joins? (i.e., force the channel's
490 # ban list to match the bot's internal list)
491 channel set #lamest -clearbans
492
493 # when a ban is set, kick people who are on the channel and match the
494 # new ban? (i.e., they were on the channel before the ban)
495 channel set #lamest +enforcebans
496
497 # Only activate bans on the channel when necessary? (This keeps the
498 # channel's ban list from getting excessively long.
499 # The bot still remembers every ban, but it only activates a ban on
500 # the channel when it sees someone join who matches that ban.)
501 channel set #lamest +dynamicbans
502
503 # allow bans to be made by users directly? (if turned off, the bot will
504 # require all bans to be made through the bot's console)
505 channel set #lamest +userbans
506
507 # only activate exempts on the channel when necessary? (this keeps the
508 # channel's exempt list from getting excessively long. the bot still
509 # remembers every exempt, but it only activates a exempt on the channel
510 # when it sees a ban set matching the exempt. The exempt remains active
511 # on the channel for as long as the ban is still active.
512 channel set #lamest +dynamicexempts
513
514 # allow exempts to be made by users directly? (if turned off, the bot will
515 # require all exempts to be made through the bot's console)
516 channel set #lamest +userexempts
517
518 # only activate invites on the channel when necessary? (this keeps the
519 # channel's invite list from getting excessively long. the bot still
520 # remembers every invite, but the invites are only activated when the
521 # channel is set to invite only and a user joins after requesting an
522 # invite. Once set the invite remains until the channel goes to -i
523 channel set #lamest +dynamicinvites
524
525 # allow invites to be made by users directly? (if turned off, the bot will
526 # require all invites to be made through the bot's console)
527 channel set #lamest +userinvites
528
529 # op users with the +o (op) flag as soon as they join the channel?
530 # (hint: this is a BAD IDEA)
531 channel set #lamest -autoop
532
533 # only let users with +o (op) flag be channel ops?
534 channel set #lamest -bitch
535
536 # say a user's info line when they join the channel?
537 channel set #lamest +greet
538
539 # re-op a user with the +o (op) flag if they get deopped?
540 channel set #lamest +protectops
541
542 # re-op a user with the +f (friend) flag if they get deopped?
543 channel set #lamest +protectfriends
544
545 # log the channel status line every 5 minutes? (some people think
546 # it's annoying; I think it's neat)
547 channel set #lamest +statuslog
548
549 # remember people who deop/kick/ban bots, valid ops or friends, and punish them?
550 # users with +f (friend) flag are exempt from revenge
551 channel set #lamest +revenge
552
553 # this works similar to revenge, but it triggers only for valid bots and
554 # allows the deop or kick of an op
555 channel set #lamest +revengebot
556
557 # voice users with +v (voice) flag when they join the channel?
558 channel set #lamest +autovoice
559
560 # prevent this channel from being listed on the botnet? (for paranoid
561 # people)
562 channel set #lamest -secret
563
564 # share user channel info for this channel?
565 channel set #lamest -shared
566
567 # cycle the channel when it becomes op-less?
568 channel set #lamest +cycle
569
570 # do you want the bot not to be able to kick +o flag users ?
571 # letting them kick-flood for instance, to protect the channel against
572 # clone attacks
573 channel set #lamest +dontkickops
574
575 # prevents the bot from joining the channel (or makes it leave the channel
576 # if it is already there).
577 # Can be useful to make the bot leave a channel without loosing it's
578 # settings (flood settings, all these "channel set" settings), user flags
579 # for this channel, bans for this channel, and without affecting any
580 # sharing
581 channel set #lamest -inactive
582
583 # respond to seen requests in the channel? (seen module must be loaded)
584 channel set #lamest -seen
585
586 # allow non-ops to perform channel modes? (Stops bot from
587 # fighting with services such as ChanServ)
588 channel set #lamest +nodesynch
589
590
591 ##### SERVER MODULE #####
592
593 # this provides the core server support (removing this is equivalent to
594 # the old NO_IRC define)
595 loadmodule server
596
597 # [0/1/2/3/4/5] What is your network?
598 # 0 = Efnet (non +e/+I hybrid), 1 = IRCnet, 2 = Undernet, 3 = Dalnet,
599 # 4 = Efnet +e/+I hybrid, 5 = Others
600 set net-type 0
601
602 ##### variables:
603 # the nick of the bot, that which it uses on IRC, and on the botnet
604 # unless you specify a separate botnet-nick
605 set nick "Lamestbot"
606
607 # an alternative nick to use if the nick specified by 'set nick' is
608 # unavailable. All '?' characters will be replaced by a random number.
609 set altnick "Llamabot"
610
611 # what to display in the real-name field for the bot
612 set realname "/msg LamestBot hello"
613
614 # script to run (if any) when first connecting to a server
615 set init-server { putserv "MODE $botnick +i-ws" }
616
617 # the server list -- the bot will start at the first server listed, and cycle
618 # through them whenever it's disconnected
619 # (please note: you need to change these servers to YOUR network's servers)
620 set servers {
621 you.need.to.change.this:6667
622 }
623
624 # [0/1] if the bot's nickname is changed (for example, if the intended
625 # nickname is already in use) keep trying to get the nick back?
626 set keep-nick 1
627
628 # [0/1] use /ison instead of /trace to see if our botnick is free or being
629 # used? (note: some irc admins, look for excessive use of /trace)
630 set use-ison 1
631
632 # [0/1] if this is set, a leading '~' on user@hosts WON'T be stripped off
633 set strict-host 0
634
635 # [0/1] Squelch the error message when rejecting a DCC CHAT or SEND?
636 # Normally it tells the DCC user that the CHAT or SEND has been rejected
637 # because they don't have access, but sometimes IRC server operators
638 # detect bots that way.
639 set quiet-reject 1
640
641 # [0/1] answer lower case ctcps (non rfc compliant)
642 # mIRC will do this, most other clients will NOT
643 set lowercase-ctcp 0
644
645 # answer HOW MANY stacked ctcps at once
646 set answer-ctcp 3
647
648 # setting any of the following with how many == 0 will turn them off
649 # how many msgs in how many seconds from the same host constitutes a flood?
650 set flood-msg 5:60
651 # how many CTCPs in how many seconds?
652 set flood-ctcp 3:60
653
654 # [0/1] even if all the servers are down, cycle forever and keep trying to
655 # connect?
656 set never-give-up 1
657
658 # [0/1] If this setting is 0 then the eggdrop keeps a separate list of the names
659 # irc servers call themselves, retaining what you entered in the config file.
660 # setting it to 1 will cause the bot to replace your entry with what
661 # the server actually calls itself
662 set strict-servernames 0
663
664 # if no port is specified on a .jump, which port should I use?
665 set default-port 6667
666
667 # number of seconds to wait between each server connect (0 = no wait)
668 # useful for preventing ircu throttling
669 # setting this too low could make your server admins *very* unhappy
670 set server-cycle-wait 60
671
672 # how many seconds to wait for a response when connecting to a server
673 # before giving up and moving on?
674 set server-timeout 15
675
676 # if the number of servers on the net gets below this number, it will
677 # jump to a new server (i.e., it will assume it's on the losing end of a
678 # netsplit) -- set to 0 to turn off
679 # [most irc networks use TS or ND now, so it's to your advantage to turn
680 # this off]
681 set servlimit 0
682
683 # [0/1] check for stoned servers? (i.e. Where the server connection has
684 # died, but eggdrop hasn't been notified yet).
685 set check-stoned 1
686
687 # [0/1] enable console mode 'r'? this mode shows every raw message from the
688 # server to owners with console 'r' selected -- will take a bit more CPU.
689 # NOTE: This is a large security hole, allowing people to see mis-sent
690 # messages to the bot containing passwords
691 # This is now restricted to +n users only. Please choose your owners with care.
692 set use-console-r 0
693
694 # [0/1] enable logging of all information sent *to* a server, via console mode 'v'
695 # NOTE: This is a large security hole, allowing people to see passwords.
696 # This is now restricted to +n users only. Please choose your owners with care.
697 set debug-output 0
698
699 # [0/1] exit if the server sends a ERROR message?
700 set serverror-quit 1
701
702 # maximum number of lines to queue to the server.
703 # if you're going to dump large chunks of text to people over irc, you
704 # will probably want to raise this -- most people are fine at 300 though
705 set max-queue-msg 300
706
707 # [0/1] trigger bindings for ignored users?
708 set trigger-on-ignore 0
709
710 # [0/1] allow a msg being twice in a queue?
711 set double-mode 0
712 set double-server 0
713 set double-help 0
714
715 # [0/1/2] enable lag check? Set to 2 if you want the bot to change queues if
716 # somebody parts or changes nickname.
717 # ATTENTION: Setting 2 is very CPU intensive
718 set use-lagcheck 1
719
720 # [0/1/2] do you want the bot to optimize the kicking queues? Set to 2 if you
721 # want the bot to change queues if somebody parts or changes nickname.
722 # Note, setting 2 is not need if you set us-lagcheck to 2.
723 # ATTENTION: Setting 2 is very CPU intensive
724 set optimize-kicks 1
725
726 ##### SERVER MODULE - net-type 5 specific features (other networks) #####
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 # If there are more than max-bans active bans on a channel, then the
768 # bot won't try to put more bans. Thus it won't flood the irc server.
769 # ircd 2.9.5 allows 20 bans. ircd 2.10 allows 30 bans (max).
770 set max-bans 20
771
772 # There is a global limit for +b/+e/+I modes. This limit is set to 30 on
773 # 2.10 irc servers.
774 set max-modes 30
775
776 # [0/1] Do you want the bot to kick for control character/ctcp avalanches
777 # to a channel?
778 # Remember that if it does, as it won't ban them, it can be at the origin
779 # of a nice kick-flood
780 set kick-fun 0
781
782 # [0/1] Do you want the bot to ban for control character/ctcp avalanches
783 # to a channel?
784 # Can prevent the above described kick-flood, but can also fill the banlist
785 set ban-fun 0
786
787 # [0/1] let users introduce themselves to the bot via 'hello'?
788 set learn-users 0
789
790 # time (in seconds) to wait for someone to return from a netsplit
791 set wait-split 600
792
793 # time (in seconds) that someone must have been off-channel before
794 # re-displaying their info
795 set wait-info 180
796
797 # [0/1/2/3] Defines how the bot should punish bad users when revenging.
798 # 0 for deop - 1 for deop and +d - 2 for deop, +d and kick - 3 for deop,
799 # chattr +d, kick and ban. Default is 1.
800 set revenge-mode 1
801
802 ##### IRC MODULE - net-type 1 specific features (IRCnet) #####
803
804 # Don't modify the following settings if you don't use IRCnet. The defaults following
805 # values are harmless for you.
806
807 # [0/1] define this if you want to bounce all server exemptions (+e modes)
808 # * This is an IRCNET feature
809 set bounce-exempts 0
810
811 # [0/1] define this if you want to bounce all server invitations (+I modes)
812 # * This is an IRCNET feature
813 set bounce-invites 0
814
815 # If there are more than max-exempts active +e modes on a channel, then
816 # the bot won't try to put more exemptions. Thus it won't flood the irc
817 # server. Only 2.10 servers are concerned by these +e modes.
818 # * This is an IRCNET feature
819 set max-exempts 20
820
821 # If there are more than max-invites active +I modes on a channel, then
822 # the bot won't try to put more invitations. Thus it won't flood the irc
823 # server. Only 2.10 irc servers are concerned by these +I modes.
824 # * This is an IRCNET feature
825 set max-invites 20
826
827 # The following lines should be left uncommented unless the default values
828 # are being over-ridden. By default exempts and invites are on for IRCnet
829 # and hybrid EFnet, but off for all other networks. This behavior can be
830 # modified by the following 2 flags. If you're network doesn't support e/I
831 # modes then you'll be unable to use these features.
832 #
833 # [0/1] Do you want to enable exempts?
834 # set use-exempts 0
835
836 # [0/1] Do you want to use invites?
837 # set use-invites 0
838
839 # [0/1] Prevent mixing normal modes and +I/+e invite modes?
840 # At the moment (Sep/1999), IRCnet servers do not allow mixing those modes,
841 # so leave this flag set to 1. The servers will probably change their
842 # behavior in the future, so you should first check before accepting the
843 # default.
844 set prevent-mixing 1
845
846 ##### IRC MODULE - net-type 5 specific features (other networks) #####
847
848 # kick-method defines how kicks (when enforcing bans) should be made:
849 # 0 = kick all nicks at once in one command
850 # X = kick X users at a time
851 #
852 # Automatically set by net-type:
853 # net-type 0, 2, 3 & 4 sets this to 1
854 # net-type 1 sets this to 4
855 #
856 # If you use net-type 5, you must set this yourself (default is 1)
857 #set kick-method 1
858
859 # some networks allow you to stack lots of channel modes into one
860 # line.
861 # they're all guaranteed to support at least 3, so that's the default,
862 # but if you know your network supports more, you may want to adjust
863 # this value. this value must be less than or equal to 6.
864 # Automatically set to 4 for net-type 0/4, set to 3 for net-type 1, set to
865 # 6 for net-type 2/3.
866 # Only use this if you set net-type 5
867 #set modes-per-line 3
868
869 # [0/1] use ircu2.10.01 specific /who requests, therefore only asking for
870 # exactly what's needed
871 # Automatically set to 0 for net-type 0/1/3/4, set to 1 for net-type 2.
872 # Only use this if you set net-type 5
873 #set use-354 0
874
875 # [0/1] use rfc 1459 compliant string matching routines?
876 # All networks apart from Dalnet comply with rfc 1459, so you should only
877 # disable it on Dalnet or networks which use Dalnet's code.
878 #set rfc-compliant 1
879
880
881 ##### TRANSFER MODULE #####
882
883 # uncomment this line to load the transfer module, this provides
884 # dcc send/get support and bot userfile transfer support (not sharing)
885 #loadmodule transfer
886
887 ##### variables:
888 # set maximum number of simultaneous downloads to allow for each user
889 set max-dloads 3
890
891 # set the block size for dcc transfers (ircII uses 512 bytes, but admits
892 # that may be too small -- 1024 is standard these days)
893 # set this to 0 to use turbo-dcc (recommended)
894 set dcc-block 1024
895
896 # [0/1] copy files into the /tmp directory before sending them? this is
897 # useful on most systems for file stability. (someone could move a file
898 # around while it's being downloaded, and mess up the transfer.) but if
899 # your directories are NFS mounted, it's a pain, and you'll want to set
900 # this to 0. If you are low on disk space, you may want to set this to 0.
901 set copy-to-tmp 1
902
903 # time (in seconds) that a dcc file transfer can remain inactive
904 # before being timed out
905 set xfer-timeout 30
906
907
908 ##### SHARE MODULE #####
909
910 # this provides the userfile sharing support
911 # (this requires the channels & transfer modules)
912 #loadmodule share
913
914 # [0/1] when sharing user lists, DONT ACCEPT global flag changes from other bots?
915 # NOTE: the bot will still send changes made on the bot, it just wont accept
916 # any global flag changes from other bots
917 #set private-global 0
918
919 # when sharing user lists, if private-global isn't set, which global flag
920 # changes from other bots should be ignored ?
921 #set private-globals "mnot"
922
923 # [0/1] when sharing user lists, DON'T ACCEPT any userfile changes from other
924 # bots?
925 # NOTE: paranoid people should use this feature on their hub bot - this
926 # will force all +host/+user/chpass/etc. changes to be made via the hub
927 #set private-user 0
928
929 # [0/1] this setting makes the bot discard it's own bot records in favor of
930 # the ones sent by the hub. Note: This only works with hubs that are v1.5.1
931 # _or higher_.
932 #set override-bots 0
933
934
935 ##### COMPRESS MODULE #####
936
937 # The compress module provides support for file compression. This allows the
938 # bot to transfer compressed user files and therefore save a significant
939 # amount of bandwidth, especially on very active hubs.
940 #loadmodule compress
941
942 # [0/1] allow compressed sending of user files. The user files
943 # are compressed with the compression level defined in `compress-level'.
944 #set share-compressed 1
945
946 # [0-9] default compression level used.
947 #set compress-level 9
948
949
950 ##### FILESYSTEM MODULE #####
951
952 # uncomment this line to load the file system module, this provides
953 # an area within the bot where you can store files
954 #loadmodule filesys
955
956 # this is the 'root' directory for the file system (set it to "" if you
957 # don't want a file system)
958 set files-path "/home/mydir/filesys"
959
960 # if you want to allow uploads, set this to the directory uploads should be
961 # put into
962 set incoming-path "/home/mydir/filesys/incoming"
963
964 # [0/1] alternately, you can set this, and uploads will go to the current
965 # directory that a user is in
966 set upload-to-pwd 0
967
968 # eggdrop creates a '.filedb' file in each subdirectory of your dcc area,
969 # to keep track of its own file system info -- if you can't do that (like
970 # if the dcc path isn't owned by yours) or you just don't want it to do
971 # that, specify a path here where you'd like all the database files to
972 # be stored instead (otherwise, just leave it blank)
973 set filedb-path ""
974
975 # set maximum number of people that can be in the file area at once
976 # (0 to make it effectively infinite)
977 set max-file-users 20
978
979 # maximum allowable file size that will be received, in K
980 # (default is 1024K = 1M). 0 makes it effectively infinite.
981 set max-filesize 1024
982
983
984 ##### NOTES MODULE #####
985
986 # this provides support for storing of notes for users from each other
987 # notes between currently online users is supported in the core, this is
988 # only for storing the notes for later retrieval, direct user->user notes
989 # are built-in
990 loadmodule notes
991
992 # the notefile: where private notes between users are stored
993 set notefile "LamestBot.notes"
994
995 # maximum number of notes to allow to be stored for each user
996 # (to prevent flooding)
997 set max-notes 50
998
999 # time (in days) to let stored notes live before expiring them
1000 set note-life 60
1001
1002 # [0/1] allow users to specify a forwarding address for forwarding notes
1003 # to another bot
1004 set allow-fwd 0
1005
1006 # [0/1] set this to 1 if you want the bot to let people know hourly if they
1007 # have any notes
1008 set notify-users 1
1009
1010 # [0/1] set this to 1 if you want the bot to let people know on join if they
1011 # have any notes
1012 set notify-onjoin 1
1013
1014 # comment out this next line, otherwise your bot won't start
1015 die "You didn't edit your config file like you were told, did you?"
1016
1017
1018 ##### CONSOLE MODULE #####
1019
1020 # this module provides storage of console settings when you exit the bot
1021 # (or .store)
1022 loadmodule console
1023
1024 ##### variables:
1025 # [0/1] save users console settings automatically? (otherwise they have to use
1026 # .store)
1027 set console-autosave 1
1028
1029 # [0-99999] if a user doesn't have any console settings saved, which channel
1030 # do you want them automatically put on?
1031 set force-channel 0
1032
1033 # [0/1] display a user's global info line when they join a botnet channel?
1034 set info-party 0
1035
1036
1037 ##### SEEN MODULE #####
1038
1039 # this module provides seen commands via msg, on channel or via
1040 # dcc, similar to the various scripts
1041 #loadmodule seen
1042
1043
1044 ##### BLOWFISH MODULE #####
1045
1046 ##### IF YOU DONT READ THIS YOU MAY RENDER YOUR USERFILE USELESS LATER
1047
1048 # Choose your encryption method now, 'cause once you do, it ain't
1049 # changing 'til you get a new userfile, capish? At the moment, there
1050 # is only one encryption option: blowfish
1051
1052 # uncomment this line to load blowfish, the encryption module
1053 # for the bot, it will not start without it loaded and commented out
1054 # to make sure you read the whole config file
1055 # this is checkmodule, because during .restart the module will already
1056 # be loaded
1057 #checkmodule blowfish
1058
1059
1060 ##### ASSOC MODULE #####
1061
1062 # uncomment this line to load assoc support, i.e. naming channels on
1063 # the botnet
1064 #loadmodule assoc
1065
1066
1067 ##### WIRE MODULE #####
1068
1069 # this module provides all the standard .wire commands via dcc.
1070 # it's an encrypted partyline communication tool, compatible with wire.tcl
1071 # uncomment this line to load it
1072 #loadmodule wire
1073
1074
1075 ##### SCRIPTS #####
1076
1077 # these are some commonly loaded (and needed) scripts.
1078 source scripts/alltools.tcl
1079 source scripts/action.fix.tcl
1080
1081 # use this for tcl and eggdrop downwards compatibility
1082 source scripts/compat.tcl
1083
1084 # This script provides many useful minor informational commands
1085 # (like setting user's URLs, email address, etc). You can modify
1086 # it to add extra entries, you might also want to modify help/userinfo.help
1087 # and help/msg/userinfo.help to change the help files.
1088 source scripts/userinfo.tcl
1089 loadhelp userinfo.help

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23