Little Confused!

St0L3n · Post by **St0L3n** » Sat Feb 26, 2005 4:25 am

Hello Every One ...
I m the owner of my bot .... when ever i join the master channel .... bot deop me ???

^DooM^ · Post by **^DooM^** » Sat Feb 26, 2005 4:35 am

have you given yourself the +d flag? ifso remove it.

St0L3n · Post by **St0L3n** » Sat Feb 26, 2005 4:39 am

ya i got that .. buddy ... n i fix that also ...
But i didn`t give it to myself ..... is think bot do as taking revange ....

..but why ?? n how should i keep that off ?
And one more ... is +d handle is in defult .... ???

^DooM^ · Post by **^DooM^** » Sat Feb 26, 2005 7:35 am

+d is not default the bot would of given you that flag for being naughty i.e. flooding or kicking the bot.

do this from the partyline.

Code: Select all

.chanset #yourchannel -revenge

also try doing

Code: Select all

.chanset #yourchannel -bitch

and lastly

Code: Select all

.chanset #yourchannel -revengebot

this should turn off the features that could give you the +d flag

awyeah · Post by **awyeah** » Sat Feb 26, 2005 8:20 am

You should always see which flags you have, or which ones you give to others, since they are many and you can't remember all. You will need to refer to the help files. Here is the explanation, from docs/users.txt

Eggdrop does not have access levels like some bots. There are no
meaningless numbers or titles. Instead, each user has "flags" that
entitle them to certain privileges. Think of a flag as a badge. Any user
can have any number of flags -- you can have no flags, or you can have
all of them. Some flags are good, some are bad. Each flag is identified
by a letter. A channel flag applies only to a specific channel, and a
global flag applies to all channels. The standard global flags are:

n (owner) user has absolute control. Only give this flag to
people you trust completely.

m (master) user has access to almost every feature of the bot.

t (botnet-master) user has access to all features dealing with the
botnet.

a (auto-op) user is opped automatically upon joining a channel.

o (op) user has op access to all of the bot's channels.

y (auto-halfop) user is halfopped automatically upon joining a channel.

l (halfop) user has halfop access to all of the bot's channels.

g (auto-voice) user is voiced automatically upon joining a channel.

v (voice) user gets +v automatically on +autovoice channels.

f (friend) user is not punished for flooding, etc.

p (party) user has access to the partyline.

q (quiet) user does not get voice on +autovoice channels.

r (dehalfop) user cannot gain halfops on any of the bot's channels.

d (deop) user cannot gain ops on any of the bot's channels.

k (auto-kick) user is kicked and banned automatically.

x (xfer) user has access to the file transfer area of the bot
(if it exists) and can send and receive files to/from
the bot.

j (janitor) user can perform maintenance in the file area of the
bot (if it exists) -- like a "master" of the file
area. Janitors have complete access to the filesystem.

c (common) this marks a user who is connecting from a public site
from which any number of people can use IRC. The user
will now be recognized by NICKNAME.

b (bot) user is a bot.

w (wasop-test) user needs wasop test for +stopnethack procedure.

z (washalfop-test) user needs washalfop test for +stopnethack procedure.

e (nethack-exempt) user is exempted from stopnethack protection.

u (unshared) user record is not sent to other bots.

h (highlight) use bold text in help/text files.

All global flags other then u, h, b, c, x, j, and p are also
channel-specific flags. Flags are set with the chattr command.
The syntax for this command is:

chattr <nickname> [attributes] [channel]

There are also 26 global user-defined flags and 26 channel user-defined
flags. These are used by scripts, and their uses very depending on the
script that uses them.

St0L3n · Post by **St0L3n** » Sun Feb 27, 2005 2:22 am

Hi again .. thanx for all that ... But

<Devil> .chattr Ahsan -x
<(Evil> [01:31] #Devil# chattr Ahsan -x
<(Evil> Global flags for Ahsan are now +fjlmoptx.

It`s Still Showing +x

Now what should i do ??

^DooM^ · Post by **^DooM^** » Sun Feb 27, 2005 7:42 am

thats because you have +t set

St0L3n · Post by **St0L3n** » Sun Feb 27, 2005 8:49 am

awwww ... how silly m i

awyeah written all that ... n i m still making mistake ... any way thanx again ... but i will be back soon with some other stupid mistake

St0L3n · Post by **St0L3n** » Mon Mar 07, 2005 3:21 pm

Hello again...
I am facing some problems in my bot ... i was running kaos trivia tcl .. the bot is working well that time ... then i add channel commad tcl its working well ... then i add bseen tcl .. the bot was working well at that time also ... but suddenly after 2 3 days the bot gives me the error ... cannot write the user files.... then its gives me the kaos TCL error ... that table overflow ... and then more error like this ... i remove the source line of all tcl from my config file ... and rehash the bot ... it gone dc by having error says ... cannot found CONFIG file .... then i try to restart my bot from the putty.exe ... it shows me error in conf file telling me that you having an error on blah blah line ... i didn`t change any thing in my conf file ... i just upload it again .. and try to restart the bot .. and it was done .... and now i m still facing the same kind of problems. When ever i try to rehash the bot it says cannot fine CONFIG file or an error

Anyone can help me out from this.

greenbear · Post by **greenbear** » Mon Mar 07, 2005 3:59 pm

maybe you ran out of space

awyeah · Post by **awyeah** » Mon Mar 07, 2005 9:30 pm

Also can be because of maybe your admin or you changed permissions on the file or folders?

St0L3n · Post by **St0L3n** » Mon Mar 07, 2005 10:40 pm

So it`s mean .. i have to contact with the shell providers ?

St0L3n · Post by **St0L3n** » Mon Mar 07, 2005 10:43 pm

One more question ... i m in the partyline of my bot ... i quit it from there n when again i try to get in the partyline ... there is no ctcp reply from the bot ....

awyeah · Post by **awyeah** » Mon Mar 07, 2005 10:48 pm

You might wana take a look at these and try to set them again correctly: (read all the comments)

# This setting will drop telnet connections not matching a known host. It
# greatly improves protection from IRCops, but makes it impossible to add
# hosts on limbo (NOIRC) bots or have NEW as a valid login.
set protect-telnet 0

# This setting will make the bot ignore DCC chat requests which appear to
# have bogus information on the grounds that the user may have been trying
# to make the bot connect to somewhere that will get it into trouble, or
# that the user has a broken client (like mIRC tends to do), in which case
# the connect wouldn't work anyway. It's suggested that you turn this on.
set dcc-sanitycheck 0

# This settings defines a time in seconds that the bot should wait before
# a dcc chat, telnet, or relay connection times out.
set ident-timeout 5

# Define here whether or not a +o user still needs the +p flag to dcc the bot.
set require-p 0

# If you want people allow to telnet in and type 'NEW' to become a new user,
# set this to 1. This is similar to the 'hello' msg command. The protect-telnet
# setting must be set to 0 to use this.
set open-telnets 1

# If you don't want Eggdrop to identify itself as an eggdrop on a telnet
# connection, set this setting to 1. Eggdrop will display 'Nickname' instead.
set stealth-telnets 0

# If you want Eggdrop to display a banner when telneting in, set this setting
# to 1. The telnet banner is set by 'set telnet-banner'.
set use-telnet-banner 0

# This settings defines a time in seconds that the bot should wait before
# a dcc chat, telnet, or relay connection times out.
set connect-timeout 20

# Specify here the number of lines to accept from a user on the partyline
# within 1 second before they are considered to be flooding and therefore
# get booted.
set dcc-flood-thr 3

# Define here how many telnet connection attempts in how many seconds from
# the same host constitute a flood. The correct format is Attempts:Seconds.
set telnet-flood 5:60

# If you want telnet-flood to apply even to +f users, set this setting to 1.
set paranoid-telnet-flood 1

# Set here the amount of seconds before giving up on hostname/address
# lookup (you might want to increase this if you are on a slow network).
set resolve-timeout 15