Currently a merged version of two bots: a Reaction Role Bot and a Temporary Voice Channel Bot. Hopefully more to come!
- To use this bot, Node.js 12.0.0 or newer must be installed.
-
Download the
zipfile. -
Configure the Bot:
- Run
npm i - You will need to create a bot application in the developers space
- Make sure you enable the
GUILD_MEMBERSandGUILD_PRESENCESintent
- Make sure you enable the
- Replace the placeholders in
config.jswith your preferred settings, along with your bot token. This file acts as a JSON, only I'm able to add comments.
- Run
-
Invite the Bot to your Server:
-
In your bot's application page, navigate to OAUTH2
-
In the "scopes" section, select
bot -
In the "bot permission" section, select:
ADMINISTRATOR
This will account for permissions needed on both features.
-
Copy and paste the generated invite link!
-
-
Get the Bot Online
- Run
node index.js - The bot is now operational ! 🎉
- Run
This bot only has one command, which can be triggered by any server admin with -rr or -reactionroles (case-insensitive). The bot assumes you have already sent the message that you want to set up reaction roles with.
A make-shift setup guide will then appear, prompting you to mention/provide the ID of the channel the message was sent in. The channel is required so that, just in case the message isn't cached, we can fetch it with Discord's API through the channel.
The next prompt will be to provide the ID/link to the message. Finally, the last step will be to react with all of your emojis, and then send a message mentioning/providing the IDs of all the corresponding roles in the order that you mentioned them
When making the original order, you pointed out that you would like the capability of reacting 20 emotes on a message for multiple messages. I assumed that you would be using reaction roles in quantities of ~20, so I made this method instead of the standard "on at a time" idea.
Disregard how long it takes for the emojis to unreact. That's not the code, it's just my wifi acting up 🤣
This bot's only feature is, when you join the channel specified in config.js, it will immediately create a channel specifically for you, and automatically move you there.
You will have all the permissions in this channel, such as to add other people, change the permissions, mute and move members, etc.
If the join back into the base voice channel while your channel is still available, it will simply move you back to that channel.
I set the delay before deletion to just five seconds for the purpose of the video.