/[cvs]/eggdrop1.6/eggdrop.conf.dist
ViewVC logotype

Contents of /eggdrop1.6/eggdrop.conf.dist

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


Revision 1.12 - (show annotations) (download)
Wed Dec 15 17:20:33 1999 UTC (20 years, 10 months ago) by fabian
Branch: MAIN
Changes since 1.11: +5 -0 lines
the share_botoverride patch...

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23