d0p3t / d0p3tbot Goto Github PK

Expected Behavior: Whenever someone subscribes or resubscribes to the channel, a message should pop up thanking them and displaying their username and message.

Current Behavior: Alert gets triggered but the username, message, months etc do not get displayed (see screenshot)

This issue is due to the string that gets sent via client.say does not recognize the passed variables in the event listener client.on. Probably has to do with scope. A solution could be to use a different way of anotating the variables inside the database and then replacing them accordingly before emitting the chat message to Twitch.

For example:

• Database: "Thank you for subscribing {username}!"
• Backend: Replace {username} with " + username + "

This issue has high priority as it's an issue with one of the core features of the product. The proposed solution may also complete the task to support variables in commands!

Current Behavior: The frontend dashboard should connect to the backend. Unfortunately the frontend socket has a timeout due to trying to connect to localhost:3000

Expected Behavior: Socket.IO connects from the frontend to the backend so that a websocket is established between them.

This will not be an issue if the bot is self hosted, but can cause issues if you're trying to access the dashboard remotely (if the bot is running on a VPS, for example). This will require some changes to the frontend code. Perhaps mention this in the README.md or Wiki

Current Behavior: Last update included the addition of categorizing commands. The basic commands do not work currently.

Expected Behavior: The basic commands should be inserted into the database so that the bot can recognize them.

Currently, on first setup, the bot does not insert the basic commands into the database. This will be a quick and easy fix that has to be done in utils/twitch.js.

Give the user the ability to enable bit/cheer support for chat alerts. This has been requested multiple times in SubNotifier and as such should also be included in here once a decision on this feature is made.

Very easy to implement due to tmi.js's support for a Cheers event listener.`