Chat Overlay for OBS based on streamer.bot's websocket, using pronouns from pronouns.alejo.io.
To use the Chat overlay locally just download the newest release from the releases page and unpack it somewhere OBS can reach it.
After unpacking you can open generator.html
in a browser to open the configurator.
While this is the easier method, using the online method comes with some drawbacks. First and foremost that Github has a soft limit on Bandwidth and Availability. There is no guarantee that this will always work.
Also keep in mind that Github has their own data collection policies.
To get started with using this method go to https://chat.bean.tools/generator.html
Supported settings are in options.md. It's easier to use the generator page, but in case you want to build the URL by hand or programatically, these might be helpful
Generally the best way to troubleshoot is to open the browser console (F12) and check for any errors. Error messages in the console might differ depending on your browser. Given OBS is based on CEF(Chromium Embedded Framework) it's likely that Chrome's console is the most accurate.
If you're not sure what to do, feel free to open an issue and we'll try to help. You can also join the discord(see below) and we can help you in text or voice chat.
- You have not removed the
Local File
checkbox in the OBS Source
- Uncheck
Local File
and paste the generated URL again
- Firefox can’t establish a connection to the server at ws://127.0.0.1:8080/
- Websocket connection to 'ws://127.0.0.1:8080/' failed: [...]
- Streamer.Bot is not running
- Streamer.Bot is listening on a different port
- Streamer.Bot is listening on a port that is not exclusively available
- Make sure Streamer.Bot is running
- If you're using a custom port, make sure it's the same as the one in the overlay's URL
- If you're using a custom port, make sure it's not in use by another application(try a different port)
- To make sure the port is exclusively available, close Streamer.Bot and run
Get-Process -Id (Get-NetTCPConnection -LocalPort 8080).OwningProcess
in PowerShell. If the output is empty, the port is available, otherwise it's in use by another process and you should probably try a different port.
- No direct errors
- Log will say connected, but not say
SUBSCRIBE: ok
- Wrong kind of Streamer.Bot websocket server started
- Make sure that in Streamer.Bot you started the internal Websocket server(under "Websocket Server"), not a custom one(under "Websocket Servers" - mind the plural)
If you have a Github account, opening an issue is the best way to give feedback. Otherwise feel free to join my Discord and ask your questions in the appropriate support channels.
Thanks to @andi242 for his fork on https://github.com/andi242/twitch-chat