I was having this problem with my perlbot 1.9.2 setup, and i've tried upgrading to perlbot 1.9.4 and I see the same weirdness. Any ideas what I'm doing wrong? A description of the weirdness follows:
- - -
When I op someone in my channel who doesn't have a user entry in config.xml ... My perlbot will repeatedly deop them until someone in the channel kicks the perlbot for mass op/deop. If I deop someone, the bot also follows suit with repeated deop attempts even after i've successfully deoped them ... This is very annoying. It doesn't seem to happen to people that im oping or deoping that are listed as a valid user in the config.xml file... Does _everyone_ that has an @ in my channel need to exist in config.xml so the bot won't do this?
Any ideas would be greatly appriciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
I was having this problem with my perlbot 1.9.2 setup, and i've tried upgrading to perlbot 1.9.4 and I see the same weirdness. Any ideas what I'm doing wrong? A description of the weirdness follows:
- - -
When I op someone in my channel who doesn't have a user entry in config.xml ... My perlbot will repeatedly deop them until someone in the channel kicks the perlbot for mass op/deop. If I deop someone, the bot also follows suit with repeated deop attempts even after i've successfully deoped them ... This is very annoying. It doesn't seem to happen to people that im oping or deoping that are listed as a valid user in the config.xml file... Does _everyone_ that has an @ in my channel need to exist in config.xml so the bot won't do this?
Any ideas would be greatly appriciated.
Try modifying your configuration file and <noload>BitchOps</noload>
I belive this will solve your problem
You also may want to modify the config file for the Protection plugin so that you have some protection over mass-deops.