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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ All notable changes to this project will be documented in this file.
23
23
- Broadcaster login now also requests the Twitch permissions needed for gifted-sub and cheer-based VIP token automation.
24
24
- The app header and settings pages now surface Twitch reauthorization more clearly when a reconnect is required.
25
25
- VIP token balances now support fractional values, including partial token grants and clearer balance handling when a viewer has less than one full VIP token remaining.
26
+
- Existing requests can now be converted between regular and VIP from chat and from the playlist manager without creating duplicate playlist entries.
26
27
- Local-development guidance now strongly separates production bot/broadcaster usage from local testing and explains the risks of cross-environment chat handling.
27
28
- The moderation dashboard now supports faster Twitch username search with debouncing, in-chat prioritization, and clearer saved-state feedback for VIP tokens.
28
29
- Search results now show newer song versions first, and public search includes a dedicated `!edit` copy command.
@@ -39,6 +40,7 @@ All notable changes to this project will be documented in this file.
39
40
- Duplicate EventSub deliveries for cheers and gifted-sub automation no longer double-grant VIP tokens.
40
41
- Twitch reply handling now distinguishes between accepted API requests and messages that Twitch actually sent to chat.
41
42
- Bot/account status screens now show the real connected bot identity instead of only the configured bot name.
43
+
- VIP request upgrade and downgrade replies now clearly state when a token was used or refunded, and dashboard-triggered request kind changes follow the same token logic and bot reply flow as chat commands.
42
44
- Production deployment config regeneration now stays in sync after remote migrations.
? `${mention(requesterIdentity.login)} your existing request "${firstMatch ? formatSongForReply(firstMatch) : unmatchedQuery}" is now a VIP request${existingMatchingRequest.status==="current" ? "." : " and will play next."} 1 VIP token was used.`
1030
+
: `${mention(requesterIdentity.login)} your existing VIP request "${firstMatch ? formatSongForReply(firstMatch) : unmatchedQuery}" is now a regular request again. 1 VIP token was refunded.`,
1031
+
});
1032
+
return{body: "Accepted",status: 202};
1033
+
}
1034
+
924
1035
if(isEditCommand&&existingActiveCount>0){
925
1036
awaitdeps.removeRequestsFromPlaylist(env,{
926
1037
channelId: channel.id,
@@ -1148,6 +1259,19 @@ export function createEventSubChatDependencies(): EventSubChatDependencies {
0 commit comments