A Discord/Twitch bot.

Cloud Firestore requires the following:

discord > credentials > [clientID, clientSecret, token]

https://discord.com/developers/applications/ID/information -> Client ID & Client Secret

https://discord.com/developers/applications/ID/bot -> Token

twitch > config > [callback]

This is the IP or domain linking to the server the bot is hosted on.

twitch > credentials > [clientId, clientSecret, token]

https://dev.twitch.tv/console/apps/ID -> Client ID & Client Secret

https://twitchapps.com/tokengen/ -> Token -- Requires the chat:read chat:edit scopes. (https://dev.twitch.tv/docs/authentication#scopes)

(Partially optional) twitch > data > USERNAME > credentials

This is the token from the user. If you choose to track a user's subscriptions, you need a token from them. You can track a user by setting the channels field in the data document. Which will auto generate the USERNAME collection the next time it's ran.

https://id.twitch.tv/oauth2/authorize?client_id=CLIENT_ID&redirect_uri=https%3A%2F%2Ftwitchapps.com%2Ftokengen%2F&response_type=token&scope=channel_subscriptions+bits%3Aread

Replace CLIENT_ID in the link above and use the response token.

Known issues: If the bot went down for whatever reason, tokens can be released. An easy way to figure out which token is causing the problem is to do the following

• Count how many unhandled errors there are and compare the similar ones with your data (i.e. Watching 2 usernames in twitch.data.channels and you see 2 unhandled promises, chances are it's those tokens).
• Another example is if you don't see "Logged in as BotName#Number" then your Discord token needs to be fixed.
• And finally you can replace the bot's chat token if they don't appear in any Twitch channels.

In the future, these will eventually print out errors if they're caught and give proper feedback for them to be fixed easier.