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