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

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

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


Revision 1.1 - (show annotations) (download)
Wed Jun 23 19:51:23 1999 UTC (21 years, 9 months ago) by segfault
Branch: MAIN
Branch point for: eggdev
Initial revision

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23