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

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

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


Revision 1.6 - (hide annotations) (download)
Fri Jun 25 15:41:32 1999 UTC (21 years, 9 months ago) by segfault
Branch: MAIN
Changes since 1.5: +3 -0 lines
Arthur's patch for a +protectfriends option

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23