Eggdrop does not protect ops or force chanmodes

[Sbarkeri]

I really don't understand, for some reason my Eggdrop does not protect Ops (Re-op them once they before deopped) nor does it force the chanmodes for a specific channel should they become changed.

Code: Select all

            channel add #channel {
      ban-time 0
      chanmode "+smtnCNuTk key"
      flood-chan 0:0
      flood-deop 0:0
      flood-kick 0:00
      flood-join 0:00
      flood-ctcp 0:00
      flood-nick 0:00
     }

channel set #channel +enforcebans +dynamicbans +userbans +dynamicexempts +protectops +dontkickops +autovoice +autoop

That is the section from my eggdrop config file that relates to that channel, is there something I am missing here as this has me compleatly stumped.

Cheers

[nml375]

My first guess would be the "owner-override" being in effect. That is, any visitor matching a +m or +n user may override any opping or channelmodes without your eggdrop taking any actions. Possibly, one of the master/owner user records have a very permissible hostmask, matching whoever is misbehaving.

Try using the .channels command from the dcc chat partyline to see as whom the de-opper/mode changer is identified as, and with which privileges.

[speechles]

That is the section from my eggdrop config file that relates to that channel, is there something I am missing here as this has me compleatly stumped.

Cheers

That section only applies when you first start the bot "eggdrop -m", otherwise any changes you make to that static section are irrelevant and meaningless. Use dcc chat/partyline and .chanset your changes.

<me> /dcc chat bot
<bot> Enter your password.
<me> password
<bot> Hey me! My name is bot and I am running eggdrop v1.6.19, on an LCD toaster.
<me> .chanset #yourchan chanmode +smtnCNuTk key
<bot> Successfully set modes { chanmode { +smtnCNuTk key } } on #yourchan.
<me> .chanset #yourchan ban-time 0
<bot> Successfully set modes { ban-time { 0 } } on #yourchan.
<me> .chanset #yourchan flood-chan 0:0
<bot> Successfully set modes { flood-chan { 0:0 } } on #yourchan.
<me> .chanset #yourchan flood-deop 0:0
<bot> Successfully set modes { flood-deop { 0:0 } } on #yourchan.
<me> .chanset #yourchan flood-kick 0:00
<bot> Successfully set modes { flood-kick { 0:00 } } on #yourchan.
<me> .chanset #yourchan flood-join 0:00
<bot> Successfully set modes { flood-join { 0:00 } } on #yourchan.
<me> .chanset #yourchan flood-ctcp 0:00
<bot> Successfully set modes { flood-ctcp { 0:00 } } on #yourchan.
<me> .chanset #yourchan flood-nick 0:00
<bot> Successfully set modes { flood-nick { 0:00 } } on #yourchan.

Understand?

[Sbarkeri]

Yeah I did also set them via the partyline just to ensure they were set, however it turns out that it was the owner-override that was kicking in, it was me who was changing the chanmode to test if the bot would chance them back little did I know that it would allow me or any other +mn to.

Cheers anyway, all sorted now