/[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.32 - (show annotations) (download)
Mon Aug 13 03:08:42 2001 UTC (18 years, 2 months ago) by guppy
Branch: MAIN
CVS Tags: HEAD
Changes since 1.31: +1 -1 lines
FILE REMOVED
Sorry, forgot to remove eggdrop.advanced.conf -- we shouldn't give Canadians commit access

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23