Hey @Firesplash thanks for the message.
The app we’ve made creates an online room named after the broadcaster. Once I know the channel’s name that the viewer is on, if they’re using the extension, it simply connects to that room.
Can you confirm whether or not the EBS is just a single file, or if it’s an actual program that needs to be running all the time? As mentioned, I’m new to this side of things, and so far I’ve simply been able to send an AJAX to Twitch, and receive the info I’m looking for. I was hoping that I could just use an ebs.js file, hosted on my website that will act as a decryper… So I could send the OpaqueID to that and receive a JSON as a response.
Instead, I’m getting the feeling I need to have an actual program running constantly, which is even further outside of my wheelhouse.
Yeah, we’ve taken your example, and followed the guide as best as we could. We assume “In the ebs folder copy config_sample.json to config.json” is asking us to rename the file, but we weren’t 100% sure.
Also the last step: “Change the https://theURLtoMyEBS to the URL of your now running EBS” confused us, as it doesn’t tell us where we’re meant to change the url, let alone where the URL is meant to be aimed at, especially as we appeared to be running it via our command prompt.
In any case, running it through the Twitch Developer Rig, we were able to get the front end to run, but the backend was throwing up a lot of errors.
We then shifted our attention to the colour changing example within the Dev Rig, and managed to get that working, but we’re hitting walls regarding how to change the path of the backend.js.
Gotta say, for an example code, they’ve made it incredibly hard to reverse engineer, with variables being converted into other variables, then finally getting called. I understand that for an actual program, but it seems like a strange choice for a tutorial/example.