/[cvs]/eggdrop-alpha/eggdrop.advanced.conf
ViewVC logotype

Contents of /eggdrop-alpha/eggdrop.advanced.conf

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


Revision 1.4 - (show annotations) (download)
Wed Jul 18 06:20:55 2001 UTC (17 years, 2 months ago) by tothwolf
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +11 -3 lines
sync with 1.6.6-CVS-995399486

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23