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