The IRCv3 Client Capability Negotiation document indicates that a ERR_INVALIDCAPCMD message should contain two parameters after the client identifier: the name of the (invalid) command, and a human-readable description of the error (for information, the freenode server correctly sends both arguments).
ZNC only provide the description of the error.
In src/Client.cpp, at line 930, one just needs to add sSubCmd as second argument, before the third one (the description of the error).
The [IRCv3 Client Capability Negotiation document](http://ircv3.org/specification/capability-negotiation-3.1) indicates that a `ERR_INVALIDCAPCMD` message should contain two parameters after the client identifier: the name of the (invalid) command, and a human-readable description of the error (for information, the freenode server correctly sends both arguments).
ZNC only provide the description of the error.
In [`src/Client.cpp`, at line 930](https://github.com/znc/znc/blob/c99eedaac3666130110b9cdf5e548eb61b8af0dc/src/Client.cpp#L930), one just needs to add `sSubCmd` as second argument, before the third one (the description of the error).
<!-- github-sync-id:26160420 -->
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.
The IRCv3 Client Capability Negotiation document indicates that a
ERR_INVALIDCAPCMDmessage should contain two parameters after the client identifier: the name of the (invalid) command, and a human-readable description of the error (for information, the freenode server correctly sends both arguments).ZNC only provide the description of the error.
In
src/Client.cpp, at line 930, one just needs to addsSubCmdas second argument, before the third one (the description of the error).