I don't know why, but my bot adds the flag "d" to the users that kick me. Also, a user kicked me with my address and now i'm auto-deoped myself and i can't remove that flag...
I am against manual editing of user file and would suggest .chattr to remove undesired flags. Also, .chanset will do the trick for seting -revenge on the channel.
Btw, take note of the following trick to set certain flags on *all* channels:
.tcl foreach chan [channels] {channel set $chan -revenge}
This is easy to do from the partyline and would affect all channels.
Ignorant and lazy people will save 30 minutes by chosing simple config file. Smart ones will save 3000 minutes of *everyone's* time by opting for complete config file.
They are able to remove the -d flag. See the first post, he can't.
They have to manualy edit the channel file (not stated int he post, only that they should remove thoses settings).
They have access to the .tcl command.
Now, presuming he has a default setup, which is most likely, due to the +revenge settings, and the lack of knowledge (not the right word) regarding why it happened. I am guessing he does have access to .tcl.
1) What does +d flag have to do with partyline access and .chattr handle -d
2) Why not .chanset #channel -revenge
3) I gave him .tcl foreach... command just for the future reference, in case he has access to .tcl and wants to chanset all channels to a certain flags.
4) How's that Tequila doing? Pass some!
Ignorant and lazy people will save 30 minutes by chosing simple config file. Smart ones will save 3000 minutes of *everyone's* time by opting for complete config file.
3) Advising such things for first time/beginers, is the start of dreadful security. It's best not to advise them, toward items that give great security vuln's, without advising them on how to tighten it up.
2) I worded it wrong in the reply to you. I meant, I had not stated it in the post, and that it didn't say the method to use (IE, file or .chanset).
1) Re-read the users first post. He is unable to do this. He has stated he tried to remove it, but is unable to. I beleive this a security method introduced a few versions back (not able to check at the moment).