# Twitch Prime IRC Tag and question about subscriber badge in tags

**URL:** <https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950>\
**Category:** Chat and IRC\
**Created:** [October 28, 2016, 1:27pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950 "2016-10-28T13:27:45Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Akhawais](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/akhawais/32/2857_2.png) [@Akhawais](https://staging-discuss.dev.twitch.com/u/Akhawais)\
**Post date:** [October 28, 2016, 1:27pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/1 "2016-10-28T13:27:45Z")

</div>

Hey, not sure if this is already in the process of being implemented, but could we have an IRC tag for Twitch Prime users?

Currently the only way to determine is via the `badges` tag:

`@badges=subscriber/0,premium/1;color=#2E8B57;display-name=(removed);emotes=;id=(removed);mod=0;room-id=(removed);subscriber=1;turbo=0;user-id=(removed);user-type=`

Similar to turbo, could we have a `prime` tag (or `premium` if it’s following the same naming as the badge):

`@badges=subscriber/0,premium/1;color=#2E8B57;display-name=(removed);emotes=;id=(removed);mod=0;room-id=(removed);subscriber=1;turbo=0;premium=1;user-id=(removed);user-type=`

* * *

Also is `subscriber/0` meant to be `subscriber/1`, or is there a reason as to why it’s 0? **(Answered - thanks for the info guys)**

* * *

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![matt\_thomas](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/matt_thomas/32/710_2.png) [@matt\_thomas](https://staging-discuss.dev.twitch.com/u/matt_thomas)\
**Post date:** [October 28, 2016, 1:34pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/2 "2016-10-28T13:34:45Z")

</div>

I believe the /0 would mean you haven’t be subbed for over 1 month yet. I think it’s the loyalty/resub badge counter. Once you have resubbed once, you earn the /1 then /3 then /6 then /12 and /24 or whatever they all are. (I think)

---

<div class="post-metadata">

**Author:** ![3ventic](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://staging-discuss.dev.twitch.com/u/3ventic)\
**Post date:** [October 28, 2016, 2:35pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/3 "2016-10-28T14:35:03Z")

</div>

The number after the slash is just the version of the badge and has no real meaning beyond that.

> [@\[beta\] Badge API](https://staging-discuss.dev.twitch.com/t/beta-badge-api/6388):
>
> Hi, This is an undocumented API that we just launched for the horde/alliance badge selection (and will be used for other badges in chat) [https://badges.twitch.tv/v1/badges/global/display?language=en](https://badges.twitch.tv/v1/badges/global/display?language=en)[https://badges.twitch.tv/v1/badges/channels/39141793/display?language=en](https://badges.twitch.tv/v1/badges/channels/39141793/display?language=en) The way our chat parses this is loads this data on startup, and then when the badges tag is encountered in a TMI privmsg tag, it looks at the key that matches it in this API response. Current TMI tag format: ...badges={bad…

---

<div class="post-metadata">

**Author:** ![Larklen](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/larklen/32/2138_2.png) [@Larklen](https://staging-discuss.dev.twitch.com/u/Larklen)\
**Post date:** [October 28, 2016, 2:37pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/4 "2016-10-28T14:37:38Z")

</div>

I assume we are talking about the subscriber tag since that is what Akhawais pointed out specifically, and if we are, then the number after the slash does have a purpose - it provides the appropriate loyalty badge level for the user.

ex.  
`subscriber/12 = 12 month loyalty badge`

[https://staging-discuss.dev.twitch.com/t/upcoming-loyalty-badges/7720/4?u=larklen](https://staging-discuss.dev.twitch.com/t/upcoming-loyalty-badges/7720/4?u=larklen)

---

<div class="post-metadata">

**Author:** ![Akhawais](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/akhawais/32/2857_2.png) [@Akhawais](https://staging-discuss.dev.twitch.com/u/Akhawais)\
**Post date:** [October 28, 2016, 2:49pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/5 "2016-10-28T14:49:18Z")

</div>

@matt_thomas @3ventic @Larklen Thanks for your help guys!

Just need to know about the prime tags now!

---

<div class="post-metadata">

**Author:** ![DallasNChains](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dallasnchains/32/1608_2.png) [@DallasNChains](https://staging-discuss.dev.twitch.com/u/DallasNChains)\
**Post date:** [October 28, 2016, 2:51pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/6 "2016-10-28T14:51:32Z")

</div>

What’s the use case for having the Prime status available?

---

<div class="post-metadata">

**Author:** ![Akhawais](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/akhawais/32/2857_2.png) [@Akhawais](https://staging-discuss.dev.twitch.com/u/Akhawais)\
**Post date:** [October 28, 2016, 3:01pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/7 "2016-10-28T15:01:47Z")

</div>

Don’t have a use for it currently (probably won’t ever need one). I just thought it could be easier to extract the information from its own tag than from the badge tag, just to match how the turbo tag is handled?

Just an idea 🙂

---

<div class="post-metadata">

**Author:** ![DallasNChains](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dallasnchains/32/1608_2.png) [@DallasNChains](https://staging-discuss.dev.twitch.com/u/DallasNChains)\
**Post date:** [October 28, 2016, 3:06pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/8 "2016-10-28T15:06:32Z")

</div>

Ah! Thought you might have a certain use case in mind. 🙂 Thanks for the feedback!

---

<div class="post-metadata">

**Author:** ![3ventic](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/3ventic/32/298_2.png) [@3ventic](https://staging-discuss.dev.twitch.com/u/3ventic)\
**Post date:** [October 28, 2016, 10:20pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/9 "2016-10-28T22:20:59Z")

</div>

It would have been useful to give them the same amount of access as turbo users have in my bot (or do they also get turbo=1 tag?), but no-one makes use of it anyway, so it doesn’t really matter.

---

<div class="post-metadata">

**Author:** ![Larklen](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/larklen/32/2138_2.png) [@Larklen](https://staging-discuss.dev.twitch.com/u/Larklen)\
**Post date:** [October 28, 2016, 10:56pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/10 "2016-10-28T22:56:41Z")

</div>

They will only get the `turbo=1` if they have chosen to use the Turbo badge instead of the Prime badge, otherwise it’ll be `turbo=0` ☹

---

<div class="post-metadata">

**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\
**Post date:** [November 27, 2016, 10:56pm UTC](https://staging-discuss.dev.twitch.com/t/twitch-prime-irc-tag-and-question-about-subscriber-badge-in-tags/7950/11 "2016-11-27T22:56:55Z")

</div>

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