When you: /msg *admin AddCTCP $me VERSION
this should make ZNC not respond to the CTCP aswell as block it from getting through to the client, but this however is not the case: it still gets passed along to the client.
If you however do this: /msg *admin AddCTCP $me VERSION blahblah
then it works as expected, ZNC replies to it by itself (with blahblah as reply) and does not bother the client at all.
When you: /msg *admin AddCTCP $me VERSION
this should make ZNC not respond to the CTCP aswell as block it from getting through to the client, but this however is not the case: it still gets passed along to the client.
If you however do this: /msg *admin AddCTCP $me VERSION blahblah
then it works as expected, ZNC replies to it by itself (with blahblah as reply) and does not bother the client at all.
<!-- github-sync-id:2851590 -->
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.
When you: /msg *admin AddCTCP $me VERSION
this should make ZNC not respond to the CTCP aswell as block it from getting through to the client, but this however is not the case: it still gets passed along to the client.
If you however do this: /msg *admin AddCTCP $me VERSION blahblah
then it works as expected, ZNC replies to it by itself (with blahblah as reply) and does not bother the client at all.
Doesn't sound like everything goes as it should there, can't be that hard to fix really.