You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start a FollowerService and watch the OnNewFollowerDetected event, it always starts off by reporting 100 new followers. They're not new followers. I don't think it's setting its cache when the service starts. This means it always considers everyone to be "new" for the first trigger of the event.
This is the version of TwitchLib I am referencing.
You have to manually call "UpdateLatestFollowersAsync(false);"
I thought I created a separate method though which called that internally. Something like "InitializeWithLatestFollowersAsync or something". Might be good to add that just for clarification.
@RRickkert how did you want to attack this? In the Start() method? I know the follower code extends the base monitor class, so that might be a bit tricky.
The suggestion in the pull request might actually solve this problem for the FollowerService. Writing that, we might actually be able to implement the same kind of thing for the LiveStreamMonitorService. Because that one also has a "StartedAt" which we can use instead of the FollowedAt! So no need to put that in the Start() method.
When I start a FollowerService and watch the
OnNewFollowerDetected
event, it always starts off by reporting 100 new followers. They're not new followers. I don't think it's setting its cache when the service starts. This means it always considers everyone to be "new" for the first trigger of the event.This is the version of TwitchLib I am referencing.
The text was updated successfully, but these errors were encountered: