Heads up - over the next hour or two we’ll be removing the metadata privmsgs sent for TWITCHCLIENTs (USERCOLOR, EMOTESET, etc).
This update will also remove some deprecated tags (user_type, emotesets) since all our official clients are using the correct user-type, emote-sets tags.
PRIVMSG no longer has an emote-sets tag after this update. Intentional?
PRIVMSG never had emote-sets, but the USERSTATE does. You need to instead parse the emotes tag.
It had “emotesets” (not “emote-sets”), I got it off PRIVMSG just yesterday during some testing, from what I can remember.
Then maybe it was a bug? I’d refer to the docs: https://github.com/justintv/Twitch-API/blob/master/chat/capabilities.md#userstate-1
Is there a cross-walk to identify which emote-sets belong to which channels?
The only type of API is third party (thanks to @george for making it): http://twitchemotes.com/api_cache/v2/sets.json
Heads-up everyone: later today we plan on retiring the remaining “jtv admin” style messages and replacing them with the new-stye NOTICE messages.
We’ll also be removing HISTORYEND messages, so if your application happens to use HISTORYEND to detect when you’ve joined a room, you should instead be listening on the JOIN server command.
@jrizzo Looks like the error id for trying to host someone when not a Twitch editor is the same one you get for trying to time someone out when you’re not a moderator. Any chance editor permissions and mod permissions can be separated into different ids? At the moment the msg-id is “no_permission.”
It’s creating issues with “Do I not have Twitch editor privileges, or am I not being detected as a mod?.”
The NOTICE is “@msg-id=no_permission :tmi.twitch.tv NOTICE #moocat :You don't have permission to perform that action.”
EDIT: This applies to both the /host and /unhost commands.
Still not showing who triggered the clearchat? 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.