Botserv remove mode

[HeRiNo]

Hi,

I am Dutcg but I try my best English. I hope I put my question at the right place. Since today an IRC oper when he set mode +V or @ its given and taken away right away by the services bot. Its only happening to him in 1 single room. Can some one tell me whats wrong?

Greetings, Herman

[G50]

Hi,

I am Dutcg but I try my best English. I hope I put my question at the right place. Since today an IRC oper when he set mode +V or @ its given and taken away right away by the services bot. Its only happening to him in 1 single room. Can some one tell me whats wrong?

Greetings, Herman

You need to turn secureops off.

/msg chanserv #channel secureops off

[HeRiNo]

Hi,

thanx for your quick answer. I already did that.

13:29:20] -ChanServ- Secure ops option for #Webraiolimburg is now OFF.

I also tryed /rehash after the command but the same result. Any Idea?

[13:39:04] -ChanServ- Opties: Topicbehoud, Veilig, Veilige Stichter, xOP lijsten systeem
-
[13:39:04] -ChanServ- Modeslot: +nrt
-
[13:39:04] -ChanServ- Expires in: 24 Feb 2012 16:10:53 CET
-

That how it is now. I translate for you: Options: Keeptopic, save, save founder, xOP list system
Modelock: nrt

Greetings, Herman.

[G50]

Hi,

thanx for your quick answer. I already did that.

13:29:20] -ChanServ- Secure ops option for #Webraiolimburg is now OFF.

I also tryed /rehash after the command but the same result. Any Idea?

[13:39:04] -ChanServ- Opties: Topicbehoud, Veilig, Veilige Stichter, xOP lijsten systeem
-
[13:39:04] -ChanServ- Modeslot: +nrt
-
[13:39:04] -ChanServ- Expires in: 24 Feb 2012 16:10:53 CET
-

That how it is now. I translate for you: Options: Keeptopic, save, save founder, xOP list system
Modelock: nrt

Greetings, Herman.

Which Oper? or do you chanop?

[HeRiNo]

I am sorry but I dont understand what you mean.

Greatings, Herman.

[Jobe]

Assuming Anope, it is also worth noting that if the oper is the only user in the channel (ignoring botserv bots), then Anope will automatically undo any +o, even when secureops is off. The reason for this is because Anope interprets the +o on the first user that joins by seeing that the user being +o'ed is the only user in the channel. At least that is what my experiance is of the matter. I have not however verified this in the code.