/[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.11 - (hide annotations) (download)
Sun Jul 11 14:57:39 1999 UTC (21 years, 9 months ago) by poptix
Branch: MAIN
Changes since 1.10: +16 -1 lines

     dw's default_chansets2.patch

 Modified Files:
 	eggdrop.conf.dist doc/UPDATES1.3 src/patch.h
 	src/mod/channels.mod/channels.c src/mod/channels.mod/tclchan.c

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

webmaster@eggheads.org
ViewVC Help
Powered by ViewVC 1.1.23