my bot, doesn't maintain the status

[sovietico]

My bot removes all the status and I don't know how to do him to that, see the log below:

Code: Select all

[01:17:07] TX set mode: -oo Megaf|AWAY meninoazul|off
[01:17:09] TX set mode: -o Sovietico

Code: Select all

[01:17:46] Flasher set mode: +o ReMaDoR
[01:17:48] TX set mode: -o ReMaDoR

As they will come, same being in the list of accesses the bot continues her had removed the status, always when somebody enters, or when who enters is the bot.

Help me, no longer I know what to do!

[De Kus]

check the hostmarks of your +d users

[Alchera]

My bot removes all the status and I don't know how to do him to that, see the log below:

Code: Select all

[01:17:07] TX set mode: -oo Megaf|AWAY meninoazul|off
[01:17:09] TX set mode: -o Sovietico

Code: Select all

[01:17:46] Flasher set mode: +o ReMaDoR
[01:17:48] TX set mode: -o ReMaDoR

As they will come, same being in the list of accesses the bot continues her had removed the status, always when somebody enters, or when who enters is the bot.

Help me, no longer I know what to do!

Try removing the revenge mode from your channel (?) and the +d flag from affected nicks (+d = deop)

Code: Select all

.chanset #channel revenge-mode 0

... also

# revenge
# Remember people who deop/kick/ban the bot, valid ops, or friends
# and punish them? Users with the +f flag are exempt from revenge.
#
# revengebot
# This is similar to to the 'revenge' option, but it only triggers
# if a bot gets deopped, kicked or banned.
#

Code: Select all

.chanset #channel -revenge -revengebot

[sovietico]

My friends the problem still perciste. See the logs below:

[23:36:19] <AcidBlood> !op
[23:36:20] Flasher set mode: +o AcidBlood
[23:36:22] TX set mode: -o AcidBlood

the bot of the net puts me OP but my bot removes soon afterwards.
see how the bot is configured in my channel.

[23:37:22] <TX> Settings for static channel #Tux-BSD:
[23:37:23] <TX> Protect modes (chanmode): +tn
[23:37:23] <TX> Idle Kick after (idle-kick): DON'T!
[23:37:23] <TX> stopnethack: DON'T!
[23:37:23] <TX> aop-delay: 5:30
[23:37:23] <TX> revenge-mode: 0
[23:37:23] <TX> ban-time: 120
[23:37:23] <TX> exempt-time: 60
[23:37:23] <TX> invite-time: 60
[23:37:23] <TX> Other modes:
[23:37:23] <TX> -inactive +statuslog -secret +shared
[23:37:23] <TX> +greet -seen +cycle +dontkickops
[23:37:23] <TX> +protectops +protectfriends -revenge -revengebot
[23:37:23] <TX> -bitch -autoop -autovoice -nodesynch
[23:37:23] <TX> +enforcebans -dynamicbans +userbans -autohalfop
[23:37:23] <TX> -protecthalfops
[23:37:23] <TX> +dynamicexempts +userexempts +dynamicinvites +userinvites
[23:37:23] <TX> flood settings: chan ctcp join kick deop nick
[23:37:23] <TX> number: 10 3 5 3 3 0
[23:37:23] <TX> time : 60 60 60 10 10 0

for the that appears in the information of the channel, I see that it agrees, but even so the bot removes the status of who enters.

Some suggestion to end with that?
I will be very thankful for the help.

[De Kus]

check the hostmarks of your +d users

...
Try removing ... the +d flag from affected nicks (+d = deop)
...

Use '.channel #Tux-BSD' to use current recognized handle names and their major access level.

[sovietico]

Dear friends, the problem continues. The users that my bot removes the status, it is not in the list, as one can see it is impossible of if they have the flag + d. They are in the list of the channel and who puts the status is the bot of the irc net, in my case MindForge. Would not you have more some alternative?

PS: whenever my bot is carried him the bot of the net puts in the it ignores, is it had as avoiding that?

Thank you very much!

[De Kus]

check ALL users, not just the one beeing deopped. If the one who ops him is flagged as deop (but not deopped because a master or owner opped him before or is deopprotected) then the error can will occur.
also make your dont have a bad programmed or misconfigured script loaded.

[sovietico]

Hey friend, thank you very much for the help, but I ended up discovering the problem, a problem easy to solve but that nor it imagined, I discovered making tests. It was enough me to do like this:

Code: Select all

.chanset #MyChan +nodesynch

Problem, resolved!

Even so, thank you