%targetChannelTitle%
moderator:manage:banned_users
for the Twitch Bot account, this was missing for banning users to workgames.dat
data file for Twitch game categories, it is now realtime search capable
isTest
argument to some Twitch events, this will be set when the event comes from the Test button within Streamer.botCPH
object in the Execute C# Code sub-action editorisTest
variable to the Community Goal eventmoderator:read:followers
$length()$
, this will get the length of a string, and variables are supported, any variable used will be treated as a stringThere 2 pending changes for the Twitch API:
The first involves IRC slash commands and 3rd party applications.
As of Februray 24th, 2023, 3rd party apps will no longer be able to use IRC slash commands. Streamer.bot has already been updated with support for the new API methods to perform these commands
The second, involves the old, undocumented API to retrieve a channels list of chatters. Currently the Raid Event adds a %raiderNames%
variable with information on who it thinks is part of the raid. Because this end point is being retired, this variable will no longer be available, as there are no replacement methods that can be used publicly.
As of April 3rd, 2023, the tmi endpoint for obtaining a channel's list of chatters will be removed, Streamer.bot will be removing the afformentioned
%raiderNames%
variable sometime in March with an update.
long TwitchGetBitsDonatedByUserId(string userId);
bool TwitchIsUserSubscribed(string userId, out string tier);
List<TwitchReward> TwitchGetRewards()
Structure of TwitchReward
public class TwitchReward
{
public string Id { get; set; }
public string Title { get; set; }
public string Prompt { get; set; }
public int Cost { get; set; }
public bool InputRequired { get; set; }
public string BackgroundColor { get; set; }
public bool Paused { get; set; }
public bool Enabled { get; set; }
public bool IsOurs { get; set; }
}
Trying to manage the games.dat file was starting to get out of hand, so with v0.1.18, it is gone completely, and in its place, when selecting specific games, you're able to perform realtime searches against Twitch's own categories, so you'll always have the most current data moving forward.
Internally, because of this change, some methods were also updated to handle the data file no longer existing.
Starting with Streamer.bot v0.1.18, it will now keep a record of any bit donations that it sees, this means if something comes in when it is not open, it will never know it happened (since there is no way to get past data from Twitch on this).
The total amount that has been seen is also shown in the user's information in the UI
If you do a test event, this will be ignored and not added to whomever shows up for the test event.
The DonorDrive integration now pulls a list of known charities from the DonorDrive api, and uses this for the different provider types now. This is mostly a quality of life improvement so you do not have to try and figure out the endpoint to use for a custom provider.
If the charity you are setting up, doesn't happen to be in the new list, you'll still be able to configure a custom provider
This sub-action will get your current follower count
Variables available:
Name | Description |
---|---|
followerCount |
Your follower count |
This sub-action will get the last user that followed your channel
Variables available:
Name | Description |
---|---|
latestFollower.user |
The display name of the user that followed you |
latestFollower.userName |
The login of the user that followed you |
latestFollower.userId |
The ID of the user that followed you |
This sub-action will get your current subscriber count and point total
Variables available:
Name | Description |
---|---|
subscriberCount |
Your subscriber count |
subscriberPoints |
The total number of subscriber points you have |
This sub-action will let you ban a user, you will be able to either enter in a specific user nname, or use a variable. You can also specify a reason, and use variables in this field
Variables available:
Name | Description |
---|---|
banResult |
True / False if the ban was successful |
These variables are only available if the sub-action was successful.
Name | Description |
---|---|
bannedUserId |
The user id of the user that was banned |
bannedUserName |
The user login of the user that was banned |
bannedUser |
The display name of the user that was banned |
This sub-action will let you unban a user, you will be able to either enter in a specific user name, or use a variable.
Variables available:
Name | Description |
---|---|
unbanResult |
True / False if the ban was successful |
These variables are only available if the sub-action was successful.
Name | Description |
---|---|
unbannedUserId |
The user id of the user that was banned |
unbannedUserName |
The user login of the user that was banned |
unbannedUser |
The display name of the user that was banned |
This sub-action will let you ban a user, you will be able to either enter in a specific user nname, or use a variable.
Variables available:
Name | Description |
---|---|
banResult |
True / False if the ban was successful |
These variables are only available if the sub-action was successful.
Name | Description |
---|---|
unTimedOutUserId |
The user id of the user that was banned |
unTimedOutUserName |
The user login of the user that was banned |
unTimedOutUser |
THe display name of the user that was banned |
Requesting the following new scopes for the broadcaster account
moderator:read:followers
Requesting the following new scopes for the bot account, as they were missing or new
moderator:manage:banned_users