What's Changed
Update 7-18-2024
Posted an updated .zip release build addressing issues when using a streamer account for the bot account.
/Update
Since v.1.3.0.0 the focus was on fixing crashes and updating the database, such as user Ids in place of usernames for monitoring streams if they're live. Tried to convert to EntityFrameworkCore (EFC), update bot crashes, update database, update TwitchLib all at the same time but as a solo coder, got very messy and broken. Hence, focused on critical bot crashing first, specifically with the auto-refreshing tokens.
The new focus is on EFC, where the code will update the GUI when there's a new record in a database table, but currently not when the data changes <-have to implement a content change notification. Also, this new database is slightly different than the existing datafile, so apart from a data import into a database, future application versions will not support the current xml database file. Several databases support EFC but including all of them in a single distribution will produce a very large binary. Have ideas to produce separate binaries based on the database distribution and probably can batch build each of the different versions, just have to write/configure the scripts to make it all seamless & produce the zip files with the distributables per EFC database type. There are database versions not requiring an existing installed database, such as 'mysql', as well as support for "SQL Server" which is installed separately. The application only requires the connection string and user credentials, per the database. The anticipation date is currently unknown for multiple factors, though the critical EFC database query part to the bot operation is written, the content notification shouldn't take very long, and have a plan to implement each EFC database for separate release builds (just will have limited testing if a certain database behaves differently with EFC and testers don't have that database version).
Also, Twitch announced their "PubSub" API will expire next year, https://discuss.dev.twitch.com/t/legacy-pubsub-deprecation-and-shutdown-timeline/58043, this bot will soon migrate to "EventSub". At a cursory review, "PubSub", "Follower Bot", and "Livestream Bot"-just other channels not bot/user channel, will migrate to 'EventSub' as it supports channel point reward redemptions, new followers, stream online/offline, and stream raid notifications. On top of this update, TwitchLib also updated their library with updates to key features, including async events for the chat bot-which need some changes in this bot to accommodate.
In summary:
- (first focus) Finish implementing EFC
- Add content update notification to refresh the GUI when content changes other than a new data entry
- Add mechanisms to build different EFC distributable binaries for the different EFC supported databases-the full file size for all supported databases would be in the 50-60MB range
- (next focus) Update this bot for the updated TwitchLib library
- Twitch deprecated PubSub, requiring EventSub
- For TwineStreamerBot, features will move to EventSub-including (depending on implementation challenges):
- PubSub - Channel Point Redemptions
- FollowBot - receiving a new follow
- LiveStream Bot - exclude the broadcaster from this bot to detect stream online/offline
- Review TwineStreamerBot connections to Twitch; the architecture can be improved for more streamlined implementation and debugging issues
Updates with no specific timeframe
- Add option to include the "Media Overlay" within the bot tabs instead of a separate window-can still have the separate window if the user wishes
- Add and support new features now open in Twitch API, including "shoutout" users and "announcements"-which separates messages in chat with an announcement adornment; and many more.
- Continue to fix bugs, especially critical bugs
Known issue(s):
- Just found clip bot isn't posting new clips to Discord webhook. Will need to review and if an easy fix, can update in an upcoming release.
Full Changelog: v.1.2.10.0...v.1.3.1.0