Make znc not reconnect on a '/kill', even if 'Connect to IRC & automatically re-connect' is checked.
Make znc increase its flood protection (temporary?) if it hits a 'excess flood'. Reasoning is if someone gets into a 'excess flood / connect / excess flood / connect ' loop, it will not stop until the person is banned from the network (K/G-Line) / removes channels / /kill'ed (pending he/she does not have the 'automatically re-connect' setting.
Make znc not reconnect on a '/kill', even if 'Connect to IRC & automatically re-connect' is checked.
Make znc increase its flood protection (temporary?) if it hits a 'excess flood'. Reasoning is if someone gets into a 'excess flood / connect / excess flood / connect ' loop, it will not stop until the person is banned from the network (K/G-Line) / removes channels / /kill'ed (pending he/she does not have the 'automatically re-connect' setting.
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/51551-make-znc-detect-excess-flood-and-kill?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:8077832 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Make znc not reconnect on a '/kill', even if 'Connect to IRC & automatically re-connect' is checked.
Make znc increase its flood protection (temporary?) if it hits a 'excess flood'. Reasoning is if someone gets into a 'excess flood / connect / excess flood / connect ' loop, it will not stop until the person is banned from the network (K/G-Line) / removes channels / /kill'ed (pending he/she does not have the 'automatically re-connect' setting.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.