Closed Number6174 closed 2 years ago
Thanks for the report, @Number6174. I don't understand your last comment.
Note that
gifter_display_name
was used for the gifter, butname
was used for the recipient.
I don't see the problem there.
It is an issue of consistency. Twitch refers to user names in two ways. In their docs they refer to this as a login
and a display_name
. The difference is a login
will be all lower case, and I believe substantially ASCII (but I'm not sure if that is documented). Whereas display_name
will preserve capitalization, and potentially be Unicode (think like Chinese characters for example).
It is used inconsistently in that for the gifter the display_name
is used, but for the recipient the login
is used.
Good point. I'll switch it to display_name
. It'll be the third time I've had to change the SL alert data endpoints. At this point, it's just a pain.
Updated the name and sub plan parsing to be more flexible and check multiple values https://github.com/Kruiser8/Kruiz-Control/commit/a717572bcdbe588a811c88da23b3d96208f2c379
Summary
The
{tier}
parameter of the eventsOnSLTwitchSubNoSync
,OnSLTwitchSub
,OnSLTwitchGiftSubNoSync
,OnSLTwitchGiftSub
all providedTier NaN
instead of the documentedPrime
,Tier 1
,Tier 2
, orTier 3
options.Included is documentation of this behavior in the case of a Prime resub,
Triggers
The relevant logging triggers used were:
And
where at
127.0.0.1:8001
is a Python script I wrote that has both a logging endpoint (/write
) and understanding of various Twitch events (/event
).This setup provides logging of both the
data
variable as well as all the other documented variables for the various StreamLabs subscription events. I also had similar logging setup forOnSLTwitchCommunityGiftSub
andOnSLTwitchCommunityGiftSubNoSync
, but those events did not fire despite community gift subs occurring. However I believe that is a separate issue.Examples
Prime subscription
Tier 1 subscription
Tier 1 Gift
Summary
Clearly the data contains the correct
sub_plan
information and it is getting converted into the wrong value.At first glance, it appears the problem in
js/streamlabs/streamlabsHandler.js
is that it refers tomessage.subPlan
in several cases when it probably should bemessage.sub_plan
. However I could be missing something with this analysis.Unfortunately I did not capute any occurences where
sub_plan
was 2000 or 3000. Nor did I capture any events of typesOnSLTwitchCommunityGiftSub
orOnSLTwitchCommunityGiftSubNoSync
, even though community gift subs occurred.In addition to the obvious problem of Tier NaN, in the case of a gift sub there is an inconsistency. Note that
gifter_display_name
was used for the gifter, butname
was used for the recipient.