Support for video-component has heavily improved, and even supports small screen sizes. Let me know if you encounter any issues.
Added mobile support.
This support is still experimental, since it is difficult to test on different devices. Please let me know if you have any issues or feedback!
Various layout and style improvements across the board.
Changed editor behavior in the configuration.
Instead of hovering over the preview to show options for adding new category and events, it now has a dedicated “edit” toggle.
Enabling the edit mode allows you to add categories and events like normal. Hovering over events while edit is enabled still shows controls for editing events. Keep in mind that enabling the edit mode shows the extension with default values.
Disabling the edit mode allows you to view the extension from a viewer’s perspective, including any changes to the default values from your streaming client (for example, if you changed locks via messages).
Added “advanced options” to categories and events for more sophisticated setups.
Added new controls for quickly setting the default lock of events and categories in the editor toolbars.
Categories can now be locked. When a category is locked, no events belonging to the category can be sent.
Changed visuals of locked events and categories.
Added new advanced option “Hide when locked” for categories and events. This hides the event or the whole category from the viewer should they be locked. Keep in mind they are still visible in the configuration editor when edit mode is active.
Added new advanced option “Use custom redeem response” to events. This powerful option allows you to send a custom response to the viewer from your WebSocket client, all within the extension. You can use this, for example, to implement a custom point system (see tutorials) - no more chat commands required. See also the API for more information.
Improved Streamer.bot integration.
Reworked whole Streamer.bot setup.
Improved and refactored code (I recommend reimporting the code if you already setup Streamer.bot in the past!).
Added examples to Streamer.bot import code.
Fixed bug with wrong WebSocket client address.
Fixed connection issue when WebSocket client is not first on the list. You can now add a global variable “StreamSocketConnectionIndex” to specify the current WebSocket client via a zero-based index of the list (for example, if the client is first in the list, you use 0, if it is second, you use 1, and so on - Streamer.bot currently doesn’t support getting WebSocket clients by name, which is why this is necessary). The variable is optional if you only connect to StreamSocket and use no other WebSocket clients.
Added new optional global variable “StreamSocketEventPrefix” if you want to use another event prefix besides “Event_”.
Added new optional global variable “StreamSocketDisableEventPrefix” if you don’t want to use an event prefix at all.
Made the following (non-persisted) global variables available when an event is received:
StreamSocketEventId
StreamSocketEventDisplayName
StreamSocketUserId
StreamSocketUserDisplayName
StreamSocketProductSku
StreamSocketProductBits
StreamSocketIsTest (for determining whether a test event is received from the configuration)
Added two tutorials for Streamer.bot, to show its capabilities in combination with StreamSocket Events.
Deprecated OBS Advanced Scene Switcher support for now in the configuration. It is still supported in the backend.
Added link to Twitchat in configuration, which supports StreamSocket Events as well.
(Near) real time configuration updates! As soon as the configuration is (automatically) saved, all currently connected viewers are updated as well. No more refreshing required. This should also fix issues with “invalid event configuration” (if you forgot to refresh and the event still used old data).
Added new API messages you can send from your client (see API for more information):