/[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.25 - (hide annotations) (download)
Fri Sep 10 07:56:11 1999 UTC (21 years, 7 months ago) by arthur2
Branch: MAIN
Changes since 1.24: +2 -1 lines
check-mode-r details

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23