Also provide in channel.cheer an array of bits used
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.
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]
While again, emote placement would help, determining the bits used from it would be extra and redundant computational work that was already processed on Twitch's side. On the same note, determining in the emote where the cheer values actually start vs the emote regex may cause issues for this particular use case, unless on the client side a running emote store was kept.
While the emote info would also be important, the amount that the cheer is, is albeit more important to me. If each bit amount were encoded in the emote structure as well that might work, though I am preferable to a separated integer array in order of provision.
Something to note, an emote alone would not be able to tell me what the amount was. Example being Party1337, would likely be an emote of Party1000.
Another note, is if the bit amounts were encoded in the emote array, you start to become less consistent with the other eventsub topics such as sub messages + emotes.
Adminecressey (Admin, Twitch) commented
HI Soaryn, thank you for the request. There's a similar request here: https://twitch.uservoice.com/forums/310213/suggestions/43765794 to provide a more structured message format. Would the other requested solution meet your needs as well?