/[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.17 - (hide annotations) (download)
Mon Aug 9 22:51:05 1999 UTC (21 years, 8 months ago) by segfault
Branch: MAIN
Changes since 1.16: +3 -0 lines
Fabian's patch to add telnet-banner to the config and add a sample
telnet-banner.

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23