There are no hype train events sent to the chat interface that tmi.js uses. The only channel point events that are available are ones that require user input. That's highlighted message, sub skip messages, and custom rewards that are set to require user input. These are all doubled through the relevant action, chat, and message events as well as the redeem event. You can get a custom reward's ID (UUID pattern) through the Helix API or just by testing it in the chat and logging unknown reward IDs.
client.on('redeem', (channel, username, rewardType, tags, message) => {
switch(rewardType) {
// Message that appears "highlighted" in the chat.
case 'highlighted-message': break;
// Message that skips the subscriber-only mode
case 'skip-subs-mode-message': break;
// Custom reward ID
case '27c8e486-a386-40cc-9a4b-dbb5cf01e439': break;
default: {
console.log('Unknown reward ID', rewardType);
break;
}
}
});
There are no hype train events sent to the chat interface that tmi.js uses. The only channel point events that are available are ones that require user input. That's highlighted message, sub skip messages, and custom rewards that are set to require user input. These are all doubled through the relevant
action
,chat
, andmessage
events as well as theredeem
event. You can get a custom reward's ID (UUID pattern) through the Helix API or just by testing it in the chat and logging unknown reward IDs.