Eggdrop

Connecting to ZNC

Add this to your eggdrop configuration:

set servers {
    <server>:<port>:<user>:<pass>
}

While doing this is very possible, certain special considerations need to be taken into account that users need to be aware of.

SSL: As of this writing, the latest stable version of Eggdrop (1.6.21) supports neither IPv6 or SSL.
- To make SSL connections from ZNC to the IRC server effective, you must run both your Eggdrop and ZNC instances on the same server, and connect Eggdrop to ZNC through 127.0.0.1, the loopback IPv4 address. ZNC must therefore have a non-SSL (plaintext) listener on 127.0.0.1.
- While a VPN setup may be an alternative, how to do this is beyond the scope of this document.
- Eggdrop 1.8 beta supports SSL, but it's not a stable version. Recommended for advanced users only.

Scroll playback: Unless you are fully aware of the implications, it's recommended to set the scroll playback values for each joined channel to 0, for no playback at all. Not doing this can result in highly undesirable behavior.
- Failure to do this could result in highly delayed bot responses (e.g. if a user types !wz 90210 and gets a reply to the weather request significantly later, when it's no longer relevant).
- A more insidious potential side-effect can result when channel protection scripts or modules are used with a non-zero amount of scroll playback.
  - When the bot reconnects, it would receive a mini-flood during the playback phase. As many, probably most channel protection scripts don't distinguish between playback and actual floods, this could result in some innocent users getting kicked or banned accidentally.

Advanced: Using putnow in any TCL scripts is not recommended for any use case. However, if you choose to do so anyway, you must also disable ZNC's flood protection (built-in queue to keep the client from sending too many messages to the server at once). A special IRCd level exemption is still required to avoid 'Excess Flood' quits.