-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Twitch Sending CAP REQ Stops All Channel Message Events #533
Comments
Until this is fixed, I will just avoid adding the Cap Req. |
When you add CAP's it changes the raw lines as it adds IRCv3 stuff to the message/line. The parser in this library doesn't handle it. You need to add stuff to I cherry picked some code from https://github.com/sigkell/irc-message/ into my Fork of node-irc to deal with it. I inserted on https://github.com/martynsmith/node-irc/blob/master/lib/parse_message.js#L20 Something along the lines of the following:
that should at least get your going somewhat with IRCv3 support and thus Twitch IRC Capabilities. Edit: This will at least make
Which'll pass tags over as needed/etc. Or fudge however you want |
I am not sure of the issue, but when I go through the irc client creation process and add the cap req:
ircClient.send('CAP REQ', 'twitch.tv/tags');
Then connect to the channel:
ircClient.join((userChannel), function () {
console.log('Connected to ' + userChannel);
chatTalk('/color hotpink');
chatAction('Hello Everybody! I\'m here to help. Type !help for commands.');
});
The following code, doesn't execute:
ircClient.addListener(('message' + userChannel), function (from, text, messageObject) {
console.log('got a message!');
console.log(from + ' => ' + userChannel + ': ');
console.log(text);
});
What I think is happening is that for some reason, the twitch cap req somehow stops the message event from being called, because RAW events still occur with the messages. I know I could probably just parse the raw event with the information I'd like, but I'd rather avoid doing that if possible, and there may be some real underlying issue here.
I'm sorry if this issue report is inadequate, I'm not entirely sure of GitHub convention.
Thank you,
The text was updated successfully, but these errors were encountered: