# Simple configuration file for eggdrop 1.3.27 and later versions
# v2.1 (21/6/2000) by slennox <slennox@egghelp.org>, http://www.egghelp.org
#
# This is a simplified version of the eggdrop.conf.dist file. It's written
# mainly for people new to eggdrop who find all the options in the example
# config file somewhat daunting. If you want to get your channel bot up and
# running as quickly and painlessly as possible, you should edit this file
# to create your bot's config file. However, if you want to take full
# advantage of all of eggdrop's features, you'll need to make some time to
# go through all the options in eggdrop.conf.dist and base your config on
# that file.
#
# Before you can start your bot, you'll need to set all the options below
# to specify things such as the bot's nickname, the servers it should
# connect to, etc. Be sure to read each description carefully.
## EGGDROP BOT CONFIGURATION ##
# These lines load all the modules necessary for a simple channel bot.
loadmodule channels
loadmodule server
loadmodule ctcp
loadmodule irc
loadmodule notes
checkmodule blowfish
# Bot admin - set your name and e-mail address.
set admin "Ansaar <Nadr@ircnetwerk.com.be>"
# Bot owner - set your nickname here.
set owner "Tux"
# New user notification - set your nickname here.
set notify-newusers "Nadr"
# User name - set this to your username on the shell.
set username "Ansaar_nl"
# Vhost - if you want your bot to use a vhost, uncomment the the following
# line (i.e. remove the #) and set the vhost. Note that you can't just set
# anything here - the vhost must be available on the shell your bot is on.
# You may also need to set the vhost's IP number for it to work on some
# shells.
#set my-hostname "look.at.my.cool.hostname.net"
#set my-ip "100.200.40.200"
# IRC network - set this to the name of the network your bot will be on.
set network "CoolNet"
# IRC network type - to allow eggdrop to function optimally on your IRC
# network's servers, set the network type below.
# 0 = EFnet, 1 = IRCnet, 2 = Undernet, 3 = DalNet, 4 = EFnet (for new
# hybrid 6.0 servers with +e support), 5 = Other Networks
set net-type 0
# Bot nickname - set the nickname you want for your bot here. Also set the
# alternate nickname (in case the first nick is in use).
set nick "islamKwis"
set altnick "islam_Bot"
# Real name - the name that appears when you /whois the bot.
set realname "AmChum's Qu|Z Bot"
# Server list - make a list of servers your bot should try to connect to.
# You will need to change this to servers on your IRC network.
set servers {
irc.blitzed.org:6667
}
# Channels - you need to create a "channel add" setting for each channel
# you want the bot to be on. Make sure you change the examples below to
# your channel(s).
#
# Each channel add has options to configure how your bot should act on the
# channel:
#
# chanmode
# Channel modes the bot will enforce.
# idle-kick
# Kick people who are idle in the channel after how many minutes? Leave
# it set to 0 to disable.
# flood-chan
# How many channel messages in how many seconds is a flood?
# flood-ctcp
# How many channel CTCPs in how many seconds is a flood?
# flood-join
# How many joins or nick changes in how many seconds is a flood?
# flood-deop
# How many deops in how many seconds is a flood?
# flood-kick
# How many kicks how many seconds is a flood?
#
# Flood settings can be set to 0:1 to disable detection.
channel add #ansaar_nl {
chanmode ""
idle-kick 0
flood-chan 10:60
flood-join 5:60
flood-ctcp 3:60
flood-deop 0:1
flood-kick 0:1
}
# Additional channel settings - these further determine how the bot should
# act on the channel(s) it's on. These settings are switched on/off using
# the + or - symbol. + (plus) switches the option on, - (minus) switches it
# off. Available settings are:
#
# enforcebans
# When a new ban is set on the channel, kick users who match the ban?
# dynamicbans
# Activate bans only when necessary (e.g. when someone who matches a ban
# joins the channel), instead of leaving it active around the clock?
# autoop
# Automatically op +o users when they join the channel? (generally a bad
# idea).
# bitch
# Only allow +o users to be opped?
# protectops
# Reop +o users if they get deopped?
# stopnethack
# Deop non +o users if they're given ops by a server?
# revenge
# Punish users who deop/kick/ban the bot?
channel set #ansaar_nl -enforcebans -dynamicbans -autoop -bitch -protectops -stopnethack -revenge
# User file - set the filename for your bot's userfile.
set userfile "mocrodream.user"
# Channel file - set the filename for your bot's chanfile.
set chanfile "ansaar_nl.chan"
# Notes file - set the filename for your bot's notes file.
set notefile "ansaar_nl.notes"
# These lines specify the logfiles the bot should keep. The first line
# makes the bot to log all bot activity to the file "nicebot.log". The
# second line makes the bot log all activity on the channel "#yourchan" to
# "#yourchan.log". You can have up to five log files. If you don't want the
# bot to keep log files, delete the three lines below. Otherwise, make sure
# you change the channel names to the channel(s) your bot will be on.
logfile mcobxs * "nicebot.log"
logfile jkp #ansaar_nl "#ansaar_nl.log"
# TCL scripts - specify any TCL scripts you wish to load.
source scripts/alltools.tcl
source scripts/action.fix.tcl
source scripts/trivia.tcl
## THAT'S IT! ##
## Don't edit below unless required ##
set help-path "help/"
set hourly-updates 02
set init-server { putserv "MODE $botnick +i-ws" }
set ctcp-mode 2
set double-mode 0
set double-server 0
set double-help 0
unbind dcc n tcl *dcc:tcl
unbind dcc n set *dcc:set
unbind dcc n simul *dcc:simul