My inspiration started 2 years ago, when I started doing scripts for Streamlabs chatbot after seeing some holes in the toolkit of Streamlabs chatbot and I made a few popular scripts, but a year in I started to realize how limited I was because of Streamlabs API and the programming languages they were using for their scripts. The big turning point was when I started working on a channel point script (this was just as the API launched) and had to some elaborate workaround to implement the features I wanted, which made for a confusing and hard to use UI.
So it started with me wanting a better and easier way to create tools for streamers and the more I thought about it the more I realized it would be best to just create my own chatbot as I've over the year seen that there were things people felt like they were missing or that they got confused with the tools they had. I wanted to create something that was highly customizable but still had a big focus on ease of use.
What it does
So Bikubot is a Chatbot that is in alpha, its functionality at the moment includes the possibility to create commands, timers, and channel point redemptions. This is done with a modular system where different actions have their own module and the user adds the module they want to the "command", so as an example to make text appear in chat you would add the text module to the "command", to the same "command" ta user could also add a sound with the sound module. The user is free to mix and match as they want to create their own unique "commands". The current modules allow for text, sounds, cmd actions, file read/write, randomization, text to speech, and OBS control.
How I built it
I wanted something that was easy to use for the user and something where I could easily add more and more functionality, that's how I came up with the modular design, where people add modules to their "commands" and these modules are executed in order, and where I could add new things by "just" creating new modules.
along the way I have tried to listen to the community and what their needs and wants is to see what I should put my focus on next.
Challenges I ran into
The selection of the languages and framework was the big first challenge, there are so many all with up and downsides.
The other challenge was that I wanted to give as much customization to the user as possible, but I came to realize at some point I have to take control over what's possible, to make it functional and not confusing, as again ease of use is a big goal.
Accomplishments that I'm proud of
The modular design, my main goals were customization and ease of use for the user, and this gives both of these. Customization in the sense that users can put together their own unique commands by mixing different modules. Ease of use comes from not overloading the user with information, if they want just text they just add a text module, there will be no other information on the screen like settings for sounds or the like.
The community around the bot, so many great and helpful people, the creativity sharing, and support for the bot is just amazing.
What I learned
I have learned so many things through this, a whole new programming language and its possibility, a better understanding of how people use and see a product. That there is many different people on twitch, with different need and knowledge.
What's next for Bikubot
There are so many plans in Bikubots future, it's just at the starting point, some of the future ideas can be found here: https://trello.com/b/Za3AQp46/bikubot-development
Some things to note
At the moment Bikubot is in alpha and requires the user to be a patron on Patreon to get access (apart from the judges), future plans are hopefully to make it free or come with a very small cost. More info can be found at: