Search in your .conf file for "flood-ctcp" and then replace in there with "flood-ctcp 0:0" to disable this protection, then do a ".rehash" of the eggy. After this there should not be any more problems of this kind.
You should only do this, if you are using static channels (very messy things, set in the config file).
If you have used a dynamic channel (using the pretty command provided on the partyline), then you can use the ".chanset #channel flood-ctcp 0:0" to disable it.
Hmm.. You are right ppslim. What i did say is for static channels, that are in .conf file. I have only one channel and is a static one. So this meens that from there came my answer. For dynamic ones he should do how you said, followed by a ".chansave" in the party line.
