I will need to find someone that knows how to fix an eggdrop big time because I went to install a tcl script that I thought will have it tell ChanServ to reop it in the event of it being deoped. What happened is when I went to test this script by having KaneFox deop the bot resulting in that the script didn't work or wasn't properly called. But when I reoped the bot, I found that its revenge-mode was triggered causing it to kick KaneFox (should have also made a ban, but it didn't) allowing him to auto-rejoin and the bot rekicking him. Because of all the notices that Edmond's script was sending in response to the joins, the server disconnected him due to "excess flood" and when he reconnected and rejoined, that made the bot go into flood-protect and kick me as well triggering my auto-join as well resulting in it constantly kicking me as well because of it not knowing to set a ban. Right now, this definitely has some errors to fix because for one thing it should not be attempting to kick/ban its owner. So, right now I have an eggdrop that does not know how to read TCL scripts like the one I was testing that caused all of this, doesn't know how to set bans when it goes to kick someone, and doesn't realize that I am its owner when it goes to attempt to kick/ban me. This is something that I need advice on to fix because the last thing I need is an eggdrop that is trying to takeover my own channel and pissing off everyone that is in the channel. To stop this, I had ChanServ DEOP the eggdrop so that it would stop this mess and to kill a couple of bans that it created, and them I had ChanServ reop it without it starting up again. If there is anyone that can help me find out what is up with this psycho bot and help me to fix it, please let me know. I am also willing to show you its eggdrop.conf file and what is on it so you can figure out what is wrong with it.
The bot is not psyco, it is likely only doing what it has been configured to do.
The first step, make sure that you remove the +revenge and +revengebot channel flags. These are the main area for concern. They should allways be disabled when doing tests, as should 1 person not be recognised, it can bing hell to heaven.
Second, using the ".match" command, search for "+k", "|+k", "+d", "|+d". Remove the flags of any user that shows up, with the exception of people that should have these flags. You may notice that the bot has created several users with these flags. Unless you have created them yourself, or you specifcly need them, you may simply delete them.
Check the global and channel bans lists (in the bot and the channel) for bans that may cause concern.
The bot should now be at a stage where it is operational. Keep the revenge flags, and +bitch off for at least a day, jsut to make sure there isn't any issues with deops and kicks.
Eggdrops internal userreconition is not a "once-seen, I know you for life" system. It's far from it. It works by storing and searching user hostmasks. These masks are simalar to searching for files (EG: *.txt). You must make sure you ahve a sutiabl hostmask, or hostmasks (it's safer to use multiple strong hostmasks).
You should also note, that the +o flag, is simply not enough to protect users. This signifies that the bot should op this user, and allow himt o use OP commands, and nothing more. The +f flag is used to signify that a user is a friend, and should be treated with respect. These two flags together, will work better for you.
You will also need to enable the +protect* channel flags (see: .chaninfo & .help chanset).
Remember, 99% of the time, it's usualy a userconfiguration error that cuases the problems. This isn't an attack on you, it's just the facts, that due to eggdrops complexity, simple changes can affects things in big ways.
Right now, I am trying to find out what TCL command you would use to make the bot send a message to someone or something else so I can put it in the .chanset need-op so the bot will know to use it to have ChanServ Reop it in the event it was deopped by someone.
And, I am still wondering why it doesn't make bans when bans are requested by it, even though the channel has currently 29 bans and can take up to 100 bans.