OpenShock Events

Listen to your OpenShock shockers in Streamer.bot - get real triggers for shock, vibrate, sound and stop events.

OpenShockEvents v1.0.0 Streamer.bot 1.0.4+

- downloads ★ No ratings yet

What it does

Connects Streamer.bot to your OpenShock account and gives you your own custom triggers for every event your shockers receive - Shock, Vibrate, Sound and Stop - no matter what fired them. That means events will come in from anywhere with the shocker name, duration and intensity as arguments.

Handy for overlays, alerts, counters, model triggers, TTS reactions, or just logging what happened during a stream.

This download is a .zip, not a .sb file - it contains the Streamer.bot import and a .dll that has to be placed into your Streamer.bot install folder’s dlls folder. Follow the setup below rather than just importing.

Installation

Download the zip above and extract it somewhere.
Close Streamer.bot.
Place OpenShockBridge.dll into your Streamer.bot install folder’s dlls folder, under <StreamerBotInstall>/dlls/.
Start Streamer.bot back up.
In Streamer.bot, open the Import tab and import openshock.sb (drag the file in, or paste its contents into the Import String area), then click Import.

First-time setup

Open the OpenShock [0] - Setup action.
- Open its Execute Code sub-action and click Find Refs.
Open the OpenShock [2] - Listener action.
- Open its Execute Code sub-action and click Find Refs.
Set the global variable openshock_token to your OpenShock API token.
- Generate one at openshock.app/settings/api-tokens.
- See the comments in the Setup action’s sub-actions for more details
Restart Streamer.bot once more.

After the restart the listener connects on boot and the Connected trigger fires.

How to use

Create a new action and type OpenShock into the trigger search - you’ll find the triggers listed below under Custom. OpenShock [3] Example Trigger ships with the import as a working example to copy from.

If the connection ever drops, open the Setup action and run its Test Trigger to manually reconnect.

Triggers

Shock / Vibrate / Sound / Stop

Each of the four event types gets its own trigger, firing whenever one of your shockers receives that command - regardless of what sent it.

Argument	Type	Description
`%shockerName%`	string	Name of the shocker that triggered the event
`%typeName%`	string	Event name - matches the trigger type, unless you’ve done `any`
`%duration%`	int	Duration of the event, in milliseconds
`%intensity%`	int	Intensity as a percentage, `0`-`100`

The shocker Id is also provided, but is less useful for most people.

Connected

Fires when the listener connects to OpenShock - on boot, or after a manual reconnect via the Setup action’s Test Trigger.

No arguments.

Troubleshooting

No triggers at all after importing - the .dll is most likely missing or was added while Streamer.bot was running. Close Streamer.bot, confirm OpenShockBridge.dll sits in <StreamerBotInstall>/dlls/, and start it again.
Compile errors in the Execute Code sub-actions - open each one (Setup and Listener) and click Find Refs once, then restart Streamer.bot.
Connected never fires - check that the openshock_token global variable is set to a valid API token from your OpenShock API tokens page, then run the Setup action’s Test Trigger to reconnect.
Need help? Reach out on Discord or Twitter.

Reviews

Loading ratings…

Loading reviews…

Checking your download history…

★

Download this extension to leave a review.

Leave a review

Share your experience with this extension.