Getting started help

[BulletSpongeTM]

I'm pretty new to discordjs. I have a bot that only runs in one discord server and in v12 I made basic reaction roles that were pretty buggy but worked. I've rebuilding my bot for discordjs v13 and wanted to do something more dependable for reactions and found this module. I'm having trouble wrapping my head around where and how to call this and make it work. As I said I'm fairly new and would love to use this, I just have no idea how to implement it.

So far I understand adding the different roles into the array, I have mine setup something like this:

var {default: ReactionRole} = require('discordjs-reaction-role');

const rulesM = "893943445914279967";
const assignmentsM = "893943445914279969";
const agreedR = "893943445675180040";
const refusedR = "895191949022199828";
const announcerR = "893943445675180038";
const eftR = "893943445675180037";
const valorantR = "893943445675180034";
const rlR = "893943445675180035";
const apexR = "893943445675180036";
const nwR = "893943445675180033";

const agreedE = `✅`;
const notagreedE =`❌`;
const announcerE = "893948862039998504";
const eftE = "893945272282005564";
const valorantE = "893945255366381578";
const rlE = "893945262853206016";
const apexE = "893945245245530132";
const nwE = "893948932453957632";

	const reactionRoles = new ReactionRole(this.client, [
		{ messageId: rulesM, reaction: agreedE, roleId: agreedR },
		{ messageId: rulesM, reaction: notagreedE, roleId: refusedR },
		{ messageId: assignmentsM, reaction: announcerE, roleId: announcerR },
		{ messageId: assignmentsM, reaction: eftE, roleId: eftR },
		{ messageId: assignmentsM, reaction: valorantE, roleId: valorantR },
		{ messageId: assignmentsM, reaction: rlE, roleId: rlR },
		{ messageId: assignmentsM, reaction: apexE, roleId: apexR },
		{ messageId: assignmentsM, reaction: nwE, roleId: nwR },
	  ]);

[danirod]

This should be enough, the reactionRoles variable is useful to stop the bot, but as long as you spawn the ReactionRole instance it starts to handle reactions if you provide the client.

Are you using correctly the partials and the intents?

[danirod]

False alarm. I can make the bot boot with JavaScript using a code similar to yours. It looks a little ugly when not using ES Modules, though:

const { Client, Intents } = require("discord.js");
const ReactionRole = require("discordjs-reaction-role").default;

This would be the same as

const { Client, Intents } = require("discord.js");
const { default: ReactionRole } = require("discordjs-reaction-role");

But I'm noticing in your code you use a lot of custom emojis. So I gave it a try with custom emojis and indeed I've discovered that this library does not work with custom emojis, or at least not like this. I can make it work with custom emojis if I provide the custom emoji name, so if your emoji is called :kekw:, you'd have to type

{ messageId: "12341234", reaction: "kekw", roleId: "123412341234" }

Clearly I think that this is not ideal, because I don't know if emoji names are stable (they get suffixes like kekw-1 when there are multiple emojis with the same name in multiple servers), so I'll make a change in the library to support providing the ID of a custom emoji, something like:

{
  messageId: message,
  reaction: "896356919890034748",
  roleId: role,
},

[danirod]

I've deployed a new version to npm (2.1.0). The README.md file has been updated with the new use cases for custom emojis and hopefully a better explanation on how to startup stuff in JS:

const client = new Client(...);
const rr = new ReactionRole(client, [
  { messageId: "12341234", reaction: "🔔", roleId: "5959859595" }, // Basic usage
  { messageId: "12341234", reaction: "✅", roleId: "5959859598" }, // Multiple reactions per message!
  { messageId: "12341234", reaction: "784536908345", roleId: "5959859598" }, // Custom emoji by ID
  { messageId: "12341234", reaction: "worry", roleId: "5959859598" }, // Custom emoji by emoji name
]);

Let me know if this makes the code start or still don't, and thank you for helping me notice the incorrect behaviour of the lib 😄

[BulletSpongeTM]

I'm glad I was able to help resolve it!
So funny thing is.. I realized that I was indeed missing the GUILD_MESSAGE_REACTIONS intent.. In my original code before I got your module on npm I had it listed in the client with my old structure of role reactions for djs v12 and when I was rebuilding from nothing I guess I just overlooked it. Even when you told me to make sure my intents and partials were all there I still somehow overlooked it haha..
Something so small and simple to overlook that it took me this long posting and showing my code to even notice it was missing!

Everything is working as it should now, the roles get added perfectly even with the custom emojis now!

Now, an new issue and a simple solution:

Instead of the clunky chain of

const x = ""; 
const y = ""; 
const z = ""; 

I am using a .json file to get all the values structured like so:

{
	"msgID" : {
		"rules":"896466661287288863", 
		"assignments":"895691297053098045"
	},
	"gameR" : {
		"agreed":"893943445675180040",
		"refused":"895191949022199828",
		"announcer":"893943445675180038",
		"eft":"893943445675180037",
		"apex":"893943445675180036",
		"rocketleauge":"893943445675180035",
		"valorant":"893943445675180034",
		"newworld":"893943445675180033"
	},
	"gameE" : {
		"agreed":"✅",
		"refused":"❌",
		"announcer":"893948862039998504",
		"eft":"893945272282005564",
		"apex":"893945245245530132",
		"rocketleauge":"893945262853206016",
		"valorant":"893945255366381578",
		"newworld":"893948932453957632"
	}
}

Then calling the values like so:

const { msgID, gameR, gameE } = require('./reactions.json');

new ReactionRole(client, [
	{ messageId: msgID.rules, reaction: gameE.agreed, roleId: gameR.agreed },
	{ messageId: msgID.rules, reaction: gameE.refused, roleId: gameR.refused },
	{ messageId: msgID.assignments, reaction: gameE.announcer, roleId: gameR.announcer },
	{ messageId: msgID.assignments, reaction: gameE.eft, roleId: gameR.eft },
	{ messageId: msgID.assignments, reaction: gameE.valorant, roleId: gameR.valorant },
	{ messageId: msgID.assignments, reaction: gameE.rocketleague, roleId: gameR.rocketleague },
	{ messageId: msgID.assignments, reaction: gameE.apex, roleId: gameR.apex },
	{ messageId: msgID.assignments, reaction: gameE.newworld, roleId: gameR.newworld },
]);

Inherently this should work just fine, but when trying to run the bot I get this error:

Now a simple solution is in your index.js line:17 you just change:

-        index[conf.messageId][conf.reaction.toString()] = conf.roleId;
+        index[conf.messageId][conf.reaction] = conf.roleId;

Seems to solve any issue and calling from the .json works just as it should.
I tested it in the traditional way that you described above:

const msg = "896466661287288863";
const emoji1 = "✅";
const emoji2 = "❌";
const role1 = "893943445675180040";
const role2 = "895191949022199828";

new ReactionRole(client, [
	{ messageId: msg, reaction: emoji1, roleId: role1 },
	{ messageId: msg, reaction: emoji2, roleId: role2 },
]);

///////////////////////////////////////////////////////////////////// And Simply:

new ReactionRole(client, [
	{ messageId: "896466661287288863", reaction: "✅", roleId: "893943445675180040" },
	{ messageId: "896466661287288863", reaction: "❌", roleId: "895191949022199828" },
]);

and it still works correctly as it should.

Very happy to have this working now, as it seems from the start it was just an issue on my end!
Thank you very much for all the replies and helping to walk me through implementing your module, you've been a tremendous help to making my bot just that much more functional, and I'm glad I was able to help resolve the custom emoji dilemma! :)

[danirod]

I think you have a typo in your JSON, because you have "rocketleauge" and not "rocketleague", and this is what causes the error. I don't do .toString() in my code -- might be the compiler adding it on its own 🤔

Glad it was somehow a intents issue. I really don't understand why intents are so hard to configure.

[BulletSpongeTM]

Ah so it appears I did, thank you for that. My bad :) Typos are always the death of me in this when I just sit at my computer for a couple hours at a time just messing with my bot haha.