I have the problem (on freenode) when a user ops himself through chanserv my eggdrop deops this user. Then chanserv ops this user again, then my bot deops him and so on....
What can I do that this doesn't happen
In the conf file from my bot I have "set allow-desync 1".
Add Chanserv to your bot and turn off stop-nethack
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
After I've done ".chattr GraveDigg -d #linux-club.de" it works but why is this line in the whois? Can I delete this line (how?)?
Is this user a bot ? or a room op??? Your bot give him the d flag to deop him/her if its a bot add the flag .chattr Gravedigg +bfo if its a user his set no password also u might want to set on protectops...... & take off his d flag
you cannot .chattr +b flag to a user you can only .+bot <nick> to gain that flag
If your bot automatically gave Gravedigg the +d flag then its set to +revenge or possibly protectops/friends and you should turn this off.
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
yes but you cannot add the +b flag with .chattr as you suggested.
Was just making it clear so the user wasn't wondering why when they copied your example it wasn't working
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born