my bot keeps de-oping other oped users in the channel!!

[kangoll]

I followed all the instructions on the FAQ and still my bot keeps de-opping the op'ed users in the channel even me the owner of the bot.. these are the things i changed

a) If the nick is being opped by a special user that doesn't appear on the channel (e.g. ChanServ), you will need to make sure the allow-desync option is set to 1 in your bot's config file. (there was not a allow-dsync on the config file so i set the nodesync to +nodesync)

b) Check the channel's bitch settings. Type .chaninfo #channel in the bot's console to do this. If the channel is in +bitch mode, type .chanset #channel -bitch to switch it off. Bitch mode allows only +o users to receive op.
c) Check the channel's revenge settings. Type .chaninfo #channel to do this. If the channel is +revenge, type .chanset #channel -revenge to switch it off. Revenge can cause your bot to give someone the +d (deop) flag if they do something naughty (e.g. deop a bot).
d) Make sure the bot hasn't added the +d flag to the user. Type .whois <user> to check for this. If the +d flag is there, use .chattr <user> -d #channel to remove it. Users are often added with the +d flag if your bot is in revenge mode.


i'm using the latest version of windrop 1.6.2

please help this is frustrating!

[ppslim]

Can you please paste the output form typeing ".chaninfo #channel_affected" and the output from a ".whois affected_user".

This information will help track down the problem.

You may want to change some of the pasted output, to keep security, but try and keep it as acurate as possible, to give us a full picture.

[kangoll]

hi thanks for replying! here are the outputs from the commands you told me to type

<kangoll> .chaninfo #el33t-warez affected
<big_bopper> Settings for static channel #el33t-warez
<big_bopper> Protect modes (chanmode): +tn-klim
<big_bopper> Idle Kick after (idle-kick): DON'T!
<big_bopper> stopnethack: DON'T!
<big_bopper> aop-delay: 5:30
<big_bopper> revenge-mode: 1
<big_bopper> To regain op's (need-op):
<big_bopper> gain_entrance op #el33t-warez
<big_bopper> To get invite (need-invite):
<big_bopper> gain_entrance invite #el33t-warez
<big_bopper> To get key (need-key):
<big_bopper> gain_entrance key #el33t-warez
<big_bopper> If Im banned (need-unban):
<big_bopper> gain_entrance unban #el33t-warez
<big_bopper> When channel full (need-limit):
<big_bopper> gain_entrance limit #el33t-warez
<big_bopper> Other modes:
<big_bopper> -inactive -statuslog -secret -shared
<big_bopper> +greet -seen +cycle +dontkickops
<big_bopper> +protectops +protectfriends -revenge +revengebot
<big_bopper> -bitch -autoop +autovoice +nodesynch
<big_bopper> +enforcebans +dynamicbans +userbans
+dynamicexempts +userexempts +dynamicinvites +userinvites
<big_bopper> flood settings: chan ctcp join kick deop nick
<big_bopper> number: 10 3 5 3 3 5
<big_bopper> time : 60 60 60 10 10 60
<big_bopper> [20:06] #kangoll# chaninfo #el33t-warez

.whois <user>

<kangoll> .whois biginc
<big_bopper> [20:08] #kangoll# whois biginc
<big_bopper> HANDLE PASS NOTES FLAGS LAST
<big_bopper> bigInc no 0 ahjmnoptux 06:03 (#el33t-war)
<big_bopper> #el33t-warez o 06:03
<big_bopper> HOSTS: *!bradsmith@12.110.244.156
<kangoll> .whois kangoll
<big_bopper> [20:08] #kangoll# whois kangoll
<big_bopper> HANDLE PASS NOTES FLAGS LAST
<big_bopper> kangoll yes 2 ahjmnoptux 20:05 (partyline )
<big_bopper> #el33t-warez d 19:09
<big_bopper> HOSTS: *!kangoll@*.cadvision.com, -telnet!*@*

[ppslim]

2 methods to fix this problem

Set the channel -revengebot, but you will lose this functionality.

Give the people that are having problems the +f flag.

Now if memory serves me right, you shouldn't need to do either of these, as the revenge code makes allowances for global +o (when +protectops is set). Further looking at the code, if the channel +d's where to be removed, you shouldn't need to git every1 +f. As long as they are global or channel +o, don't have channel +d and the channel is set +protectops, you should be fine.

[kangoll]

k i set the affected users +f flags and protect ops and +o many times but it still de-ops me and another user when i do a whois for me i have the d flag there

<kangoll> .whois kangoll
<big_bopper> [20:08] #kangoll# whois kangoll
<big_bopper> HANDLE PASS NOTES FLAGS LAST
<big_bopper> kangoll yes 2 ahjmnoptux 20:05 (partyline )
<big_bopper> #el33t-warez d 19:09
<big_bopper> HOSTS: *!kangoll@*.cadvision.com, -telnet!*@*

i've done the command .chattr kangoll -d many times but the problem still presists
who do i get rid of the #el33t-warez d 19:09
i've tried .chanset #el33t-warez -d and that command does't exist

[Petersen]

either give the user the +f flag (either globally or for the chan), or .chanset #chan revenge-mode 0

[ppslim]

The problem lies in the .chattr command you are using.

Try typing ".help chattr" and you will see your error.

To change channel flags use ".chattr <hand> <flags>".

[kangoll]

Whats a handle??

[ppslim]

A handle is the equivilant of a username.

You can change nicknames on irc, but your handle remains the same.

[kangoll]

how do i put the handle in? can u give me an example?

.chattr *!*@*.address +o

that command gives me a error always

[ppslim]

<kangoll> .whois kangoll
<big_bopper> [20:08] #kangoll# whois kangoll
<big_bopper> HANDLE PASS NOTES FLAGS LAST
<big_bopper> kangoll yes 2 ahjmnoptux 20:05 (partyline )
<big_bopper> #el33t-warez d 19:09
<big_bopper> HOSTS: *!kangoll@*.cadvision.com, -telnet!*@*

you used a handle here. The whois command takes a handle to display the information. In which case, you handle is kangoll.

Seeing as the problem is on the +d flag for #el33t-warez. You would type.

.chattr kangoll -d #el33t-warez