Hi,
Since the release of the new Twitch version and of the new chat, the PubSub topic chat_moderator_actions.userId.channelId
tends to send invalid data when timing users out, as it is reported as a ban. This seems to happen when moderators issue a timeout from the new chat only, legacy chat always sends proper values.
Example value when timing out an user from the legacy chat (correct):
{"data":{"type":"chat_login_moderation","moderation_action":"timeout","args":["targetName","600"],"created_by":"moderatorName","created_by_user_id":"moderatorID","msg_id":"","target_user_id":"targetID"}}
Example value when timing out an user from the new chat (reported as ban):
{"data":{"type":"chat_login_moderation","moderation_action":"ban","args":["targetName",""],"created_by":"moderatorName","created_by_user_id":"moderatorID","msg_id":"","target_user_id":"targetID"}}
On both cases a CLEARCHAT
is issued on IRC with the correct time, but it is hard to connect these CLEARCHAT
events and the PubSub events, as CLEARCHAT
does not contain the name or ID of the moderator. As this PubSub topic is not directly documented, is this a bug that may get fixed, or is there a better way to handle timeouts and bans? This PubSub topic has been very practical in the past.
Thank you