/[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.3 - (hide annotations) (download)
Thu Jun 24 15:34:12 1999 UTC (21 years, 9 months ago) by segfault
Branch: MAIN
Changes since 1.2: +4 -0 lines
This patch fixes the problem of users with +f still being ignored in the
case of a telnet flood.  Patch sent by dw, manually applied by SegFault.

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23