Is there a way to enable debugging to see the requests sent and responses received when an eggdrop starts up and logs into the IRC server ? I set the debug-output to 1 and I see the requests the bot sends but I am not convinced I am seeing the responses from the server. Is there a way to enable that ?
I set the line exactly as you had in your reply.
I am running it using eggdrop -n to keep it in the foreground. I would assume this mimic's a master's console.
It mimic's a console, and by my guessing, will take it's console flags, as the default ones set in the config file.
To make sure you have the correct flags, launch the bot into the backgrond, and telnet to it. This will allow you to change your console flags. A simple .jump should then get you to the position of reading server input.
It did work. I just was half asleep. Didn't check lower in the file where the default entry was resetting it back to 0. Works now. Thanks for the help !
Of course now that I see what I see, it's even more baffling. But that's for another post
If there is an issue, with eggdrop sitting on a channel, but displaying messages in the partyline, sugesting it's not there, then it is doubtful this is an eggdrop issue.
The next question would be, what IRCD / network are your bots on?
Some networks give non-standard replies, to certain messages, which eggdrop can't cope with, yet some IRC clients can. This is not an issue with eggdrop, but with the IRCD not supporting the standard. Why should eggdrop fix somthing the IRCD makers broke.
I only use it on webnet and they did change something in the way the /who commands responds, and it's since then the bot isn't performing. I was hoping that playing with the config file on the new version would maybe make it play with the broken server. I know it's webnet since the bot works fine on newnet. I was planning to try and capture packets and see exactly what is happening. Knowing that might give me an idea on what to tweak (if anything)