IRC not receiving notice about sub/prime/channel point rewards/etc

Hello, I was playing around with an irc bot and I noticed that I wasn’t getting notices regarding new subs/prime subs/channel point rewards/etc… I’ve CAP’d for /comamnds and /tags. Below I have the commands I send when I first connect, The response from the server, and a sample of a stream I was watching. In the middle of these messages someone redeemed their channel points for reward which had a message printed in chat.

EDIT: The odd thing is when I view the same chat in hexchat I can see lines where the notices would be as “GARBAGE: USERNOTICE #cirno_tv :cirCursed”

self.irc.connect((server, port))

self.irc.send(bytes("CAP REQ\n", "UTF-8"))
self.irc.send(bytes("CAP REQ\n", "UTF-8"))
self.irc.send(bytes("CAP REQ\n", "UTF-8"))

self.irc.send(bytes(f"PASS {botpass}\n", "UTF-8"))
self.irc.send(bytes(f"NICK {botnick}\n", "UTF-8"))

self.irc.send(bytes(f"JOIN {channel}\n", "UTF-8"))
$ python3 
Connecting to: CAP * ACK CAP * ACK CAP * ACK 001 waterflame321 :Welcome, GLHF! 002 waterflame321 :Your host is 003 waterflame321 :This server is rather new 004 waterflame321 :- 375 waterflame321 :- 372 waterflame321 :You are in a maze of twisty passages, all alike. 376 waterflame321 :>

6-626d-4da0-9706-fe8ca56f3fff;mod=1;room-id=39508026;subscriber=1;tmi-sent-ts=1631149588349;turbo=0;user-id=163452794;user-type=mod :bz_______! PRIVMSG #swee
tcheekstvr :<msg>

r=1;tmi-sent-ts=1631149592758;turbo=0;user-id=131520388;user-type= :drsyrus! PRIVMSG #sweetcheekstvr :<msg>

r=1;tmi-sent-ts=1631149603754;turbo=0;user-id=131520388;user-type= :drsyrus! PRIVMSG #sweetcheekstvr :<msg>

8026;subscriber=0;tmi-sent-ts=1631149605400;turbo=0;user-id=167002468;user-type= :nekoasunya! PRIVMSG #sweetcheekstvr :<msg>

@badge-info=;badges=;client-nonce=d1476486820f107e3283e43432a7dd12;color=#FF0000;display-name=thescarlettdahlia;emotes=;first-msg=0;flags=;id=72ff2679-e631-4636-8b9e-47a960750958;mod=0;room-id=39508026;subscriber=0;tmi-sent-ts=1631149611897;turbo=0;user-id=679762757;user-type= :thescarlettdahlia! PRIVMSG #sweetcheekstvr :<msg>

This seems to indicate you have no # at the start of the room. So you didn’t join a IRC room/channel.

Since your Log output didn’t respond with a JOIN. So you tried to join a room that doesn’t exist


self.irc.send(bytes(f"JOIN #{channel}\n", "UTF-8"))

Additionally make sure the channel is ALL lowercase (ie the channels username NOT their display name)

Alas I wish it was that simple of a fix. But in the config file I have the #.

## IRC Config
server = ""
port = 6667

channel = "#sweetcheekstvr"
botnick = ""
botpass = ""

Channel point redemption does not come thru IRC. Subs would tho.

They do if the redeemer is invited to leave a message. Which is what I assumed OP was referring to. (Highlight message/leave message in sub only mode/custom reward asking user to leave a message aka prompt)

Ah, right. Sorry, I wasn’t precise.

I’m out of ideas/can’t see anything obviously wrong here.

Unless your parser doesn’t understand USERNOTICE but yoiu appear to be RAW logging everything.

USERNOTICE is gonna be for subs
PRIVMSG with a reward-id tag (I forget the specific name of the tag) for rewards that trigger a chat message.

Ah okay… I’m looking for just the redeem. I was hoping to be able to do this without having to gather oauth tokens for pubsub.

Why doesn’t the below trigger in IRC? Obviously twitch has some form of endpoint for it to display in chat. Is it supported in the websocket version of chat?

You’ll need pubsub or eventsub for that.

Redeems that don’t let a user/redeember enter text are not sent to chat.

Twitch uses “internal” PubSub to display non message redeems “in chat”

So then how do I the user who doesn’t have a auth token for streamA see pubsub events I can’t subscribe to?(BadAuth)

You will need authorisation from the streamer. And thus use the streamers token with the relevant scopes applied.

Okay cool. Thanks for answering my questions ^^

Most Welcome :slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.