Translate Ideas and Comments
Choose language:
There was an error during translation

Developers

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. If would be very useful for chat clients or chat overlays to be able to show live updates on these features. Currently they are only available for the broadcaster (redemptions) or not at all through websockets (polls/predictions).

    Ideally this would be available for all users to receive, just like chat is (which allows more simple integration into all kinds of tools), but even just mods using third-party moderation tools would already benefit greatly from this.

    I included all three of those features, since they all seem to follow the same idea of only allowing the broadcaster access to that information…

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  2. Summary:
    A cheer message can be multiple cheers in a single payload. Providing the individual cheer components in an int array would provide data that is not currently there. Emote placement, while also desired, would be still more work than should be necessary at first glance to determine the bits used.

    Example: **
    BarryCarlyon PogChamp100 PogChamp100 Party100 Wow Soaryn is Frustrated!
    This would result in **"bits": 300;
    however this is incomplete and would be desired to also have something like "bits_used": [100,100,100]

    Reasoning:
    While again, emote placement would help, determining the bits used from it would be extra and redundant…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  3. When viewers cheer, they use cheermotes and commonly emotes in their cheer messages. Unfortunately, the payload received from EventSub's channel.cheer callbacks only have the raw text as entered by the user, with no indiciation of which portions of that text are cheermotes nor emotes. Thus, I propose the following update to the callback payload, similar to the channel.subscription.message event, that passes along the data for both so that a consumer of EventSub can reconstruct the message:

    {
        "subscription": {
            ...
        },
        "event": {
            ...
            "message": {
                "text": "Rah Rah Cheer! cheerwhal1 Cheer100 notACheer101 finite6ThrowBall",
                "cheermotes": [
                    {
                        "begin": 16,
                        "end":
    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add three topics

    • Raid Begin, a channel started a /raid
    • Raid progress, the number of users in the raid changed (sensibly capped so not too spammy on the webhook, but if socket, more spammy perhaps)
    • Raid End, raid completed or was cancelled.
    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  5. This is more of a uncertainty of necessity, as the hype train documentation is still fairly new to me. As a broadcaster there have been scenarios where a level 5 hype train was the starting level.

    Providing the level at the start could alleviate some confusion for progress and end as well as provide some consistency for the other two event types.

    Reasoning:
    The hype train on the end user side could start at a completed level 5. Depending on when the event is actually sent, this could provide odd results.

    Related events:
    - channel.hype_train.begin
    - channel.hype_train.progress
    - channel.hype_train.end

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  0 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  6. To forward live notifications, it would be awesome to also receive the live notification message the streamer has set - either when they set it with channel.update and/or when the stream goes live.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  7. Include the same data as received from https://api.twitch.tv/helix/moderation/banned/events. Primarily event timestamp (time when the ban/unban action occurred) and the id (allows checking for duplication with eventsub messages already received when pulling from helix)

    Add the following fields to "event" paylod for ban/unban eventsub messages:
    "id": "1IPFqmlu9W2q4mXXjULyM8zX0rb",
    "action_timestamp": "2019-03-13T15:55:19Z"

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?