message on reaction add event v14.3.0

D

d.js docsAPP•1/17/23, 6:15 PM

Suggestion for @hugo4774:
guide

Popular Topics: Reaction collectors
read more

D

d.js docsAPP•1/17/23, 6:15 PM

Suggestion for @hugo4774:
guide

Popular Topics: Awaiting reactions
read more

D

d.js docsAPP•1/17/23, 6:16 PM

Popular Topics: Listening for reactions on old messages
read more

HHugo4774 ` client.rest.on(Events.MessageReactionAdd, async (re...

S

Squid•1/17/23, 6:17 PM

1) You don't need to go through

.rest

.rest

.rest

.rest; just

client.on(...)

client.on(...)

client.on(...)

client.on(...) is correct for almost every event
2) Compare

reaction.message.id

reaction.message.id

reaction.message.id

reaction.message.id to the id of the specific message
3)

reaction.emoji

reaction.emoji

reaction.emoji

reaction.emoji is the emoji that was added

Dd.js docs <:guide:862626783890636830> **Popular Topics: Listening for reactions on old me...

H

Hugo4774OP•1/17/23, 6:17 PM

that's what i've done

H

Hugo4774OP•1/17/23, 6:17 PM

and i'm getting

                            client.rest.on(Events.MessageReactionAdd, async (reaction, user) => {
                                        ^

TypeError: Cannot read properties of undefined (reading 'on')

                            client.rest.on(Events.MessageReactionAdd, async (reaction, user) => {
                                        ^

TypeError: Cannot read properties of undefined (reading 'on')

                            client.rest.on(Events.MessageReactionAdd, async (reaction, user) => {
                                        ^

TypeError: Cannot read properties of undefined (reading 'on')

                            client.rest.on(Events.MessageReactionAdd, async (reaction, user) => {
                                        ^

TypeError: Cannot read properties of undefined (reading 'on')

D

deminearchiver•1/17/23, 6:21 PM

From the guide:

const { Client, Events, GatewayIntentBits, Partials } = require('discord.js');

const client = new Client({
    intents: [GatewayIntentBits.Guilds, GatewayIntentBits.GuildMessages, GatewayIntentBits.GuildMessageReactions],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

client.on(Events.MessageReactionAdd, async (reaction, user) => {
    // When a reaction is received, check if the structure is partial
    if (reaction.partial) {
        // If the message this reaction belongs to was removed, the fetching might result in an API error which should be handled
        try {
            await reaction.fetch();
        } catch (error) {
            console.error('Something went wrong when fetching the message:', error);
            // Return as `reaction.message.author` may be undefined/null
            return;
        }
    }

    // Now the message has been cached and is fully available
    console.log(`${reaction.message.author}'s message "${reaction.message.content}" gained a reaction!`);
    // The reaction is now also fully available and the properties will be reflected accurately:
    console.log(`${reaction.count} user(s) have given the same reaction to this message!`);
});

const { Client, Events, GatewayIntentBits, Partials } = require('discord.js');

const client = new Client({
    intents: [GatewayIntentBits.Guilds, GatewayIntentBits.GuildMessages, GatewayIntentBits.GuildMessageReactions],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

client.on(Events.MessageReactionAdd, async (reaction, user) => {
    // When a reaction is received, check if the structure is partial
    if (reaction.partial) {
        // If the message this reaction belongs to was removed, the fetching might result in an API error which should be handled
        try {
            await reaction.fetch();
        } catch (error) {
            console.error('Something went wrong when fetching the message:', error);
            // Return as `reaction.message.author` may be undefined/null
            return;
        }
    }

    // Now the message has been cached and is fully available
    console.log(`${reaction.message.author}'s message "${reaction.message.content}" gained a reaction!`);
    // The reaction is now also fully available and the properties will be reflected accurately:
    console.log(`${reaction.count} user(s) have given the same reaction to this message!`);
});

const { Client, Events, GatewayIntentBits, Partials } = require('discord.js');

const client = new Client({
    intents: [GatewayIntentBits.Guilds, GatewayIntentBits.GuildMessages, GatewayIntentBits.GuildMessageReactions],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

client.on(Events.MessageReactionAdd, async (reaction, user) => {
    // When a reaction is received, check if the structure is partial
    if (reaction.partial) {
        // If the message this reaction belongs to was removed, the fetching might result in an API error which should be handled
        try {
            await reaction.fetch();
        } catch (error) {
            console.error('Something went wrong when fetching the message:', error);
            // Return as `reaction.message.author` may be undefined/null
            return;
        }
    }

    // Now the message has been cached and is fully available
    console.log(`${reaction.message.author}'s message "${reaction.message.content}" gained a reaction!`);
    // The reaction is now also fully available and the properties will be reflected accurately:
    console.log(`${reaction.count} user(s) have given the same reaction to this message!`);
});

const { Client, Events, GatewayIntentBits, Partials } = require('discord.js');

const client = new Client({
    intents: [GatewayIntentBits.Guilds, GatewayIntentBits.GuildMessages, GatewayIntentBits.GuildMessageReactions],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

client.on(Events.MessageReactionAdd, async (reaction, user) => {
    // When a reaction is received, check if the structure is partial
    if (reaction.partial) {
        // If the message this reaction belongs to was removed, the fetching might result in an API error which should be handled
        try {
            await reaction.fetch();
        } catch (error) {
            console.error('Something went wrong when fetching the message:', error);
            // Return as `reaction.message.author` may be undefined/null
            return;
        }
    }

    // Now the message has been cached and is fully available
    console.log(`${reaction.message.author}'s message "${reaction.message.content}" gained a reaction!`);
    // The reaction is now also fully available and the properties will be reflected accurately:
    console.log(`${reaction.count} user(s) have given the same reaction to this message!`);
});

Original message was deleted

H

Hugo4774OP•1/17/23, 6:59 PM

well, i logged client and got that :

{
  BaseClient: [class BaseClient extends EventEmitter],
  Client: [class Client extends BaseClient],
  Shard: [class Shard extends EventEmitter],
  ShardClientUtil: [class ShardClientUtil],
  ShardingManager: [class ShardingManager extends EventEmitter],
  WebhookClient: [class WebhookClient extends BaseClient],`
...

{
  BaseClient: [class BaseClient extends EventEmitter],
  Client: [class Client extends BaseClient],
  Shard: [class Shard extends EventEmitter],
  ShardClientUtil: [class ShardClientUtil],
  ShardingManager: [class ShardingManager extends EventEmitter],
  WebhookClient: [class WebhookClient extends BaseClient],`
...

{
  BaseClient: [class BaseClient extends EventEmitter],
  Client: [class Client extends BaseClient],
  Shard: [class Shard extends EventEmitter],
  ShardClientUtil: [class ShardClientUtil],
  ShardingManager: [class ShardingManager extends EventEmitter],
  WebhookClient: [class WebhookClient extends BaseClient],`
...

{
  BaseClient: [class BaseClient extends EventEmitter],
  Client: [class Client extends BaseClient],
  Shard: [class Shard extends EventEmitter],
  ShardClientUtil: [class ShardClientUtil],
  ShardingManager: [class ShardingManager extends EventEmitter],
  WebhookClient: [class WebhookClient extends BaseClient],`
...

HHugo4774 well, i logged client and got that : ```client { BaseClient: [class BaseClien...

S

Squid•1/17/23, 7:01 PM

That looks like all of discord.js' exports, not a Client instance

H

Hugo4774OP•1/17/23, 7:03 PM

const client = new Client({
    intents: [
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMessages,
        GatewayIntentBits.MessageContent,
        GatewayIntentBits.GuildVoiceStates,
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMembers,
        GatewayIntentBits.GuildMessageReactions
    ],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

const client = new Client({
    intents: [
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMessages,
        GatewayIntentBits.MessageContent,
        GatewayIntentBits.GuildVoiceStates,
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMembers,
        GatewayIntentBits.GuildMessageReactions
    ],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

const client = new Client({
    intents: [
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMessages,
        GatewayIntentBits.MessageContent,
        GatewayIntentBits.GuildVoiceStates,
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMembers,
        GatewayIntentBits.GuildMessageReactions
    ],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

const client = new Client({
    intents: [
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMessages,
        GatewayIntentBits.MessageContent,
        GatewayIntentBits.GuildVoiceStates,
        GatewayIntentBits.Guilds,
        GatewayIntentBits.GuildMembers,
        GatewayIntentBits.GuildMessageReactions
    ],
    partials: [Partials.Message, Partials.Channel, Partials.Reaction],
});

`

client.on('messageCreate', message => {
...

        command.execute(message, args, Discord, client);
    ...
});

client.on('messageCreate', message => {
...

        command.execute(message, args, Discord, client);
    ...
});

client.on('messageCreate', message => {
...

        command.execute(message, args, Discord, client);
    ...
});

client.on('messageCreate', message => {
...

        command.execute(message, args, Discord, client);
    ...
});

index.js

H

Hugo4774OP•1/17/23, 7:03 PM

and then my command i go in the execute function

Original message was deleted

H

Hugo4774OP•1/17/23, 7:03 PM

nope

S

Squid•1/17/23, 7:04 PM

The messageReactionAdd event isn't a command though...

H

Hugo4774OP•1/17/23, 7:04 PM

or maybe is it this ?

const { Client, GatewayIntentBits, Partials } = require('discord.js');

const { Client, GatewayIntentBits, Partials } = require('discord.js');

const { Client, GatewayIntentBits, Partials } = require('discord.js');

const { Client, GatewayIntentBits, Partials } = require('discord.js');

SSquid The messageReactionAdd event isn't a command though...

H

Hugo4774OP•1/17/23, 7:04 PM

yes he's in the execute of a command

H

Hugo4774OP•1/17/23, 7:06 PM

why ?

S

Squid•1/17/23, 7:06 PM

the first time you create the command, you make one messageReactionAdd event listener
1 total
the second time you create the command, you make one messageReactionAdd event listener
2 total
etc.

D

d.js docsAPP•1/17/23, 7:07 PM

Popular Topics: Reaction collectors
read more

S

Squid•1/17/23, 7:07 PM

These are designed for temporary use, and you can create them to only listen on specific messages

H

Hugo4774OP•1/17/23, 7:08 PM

so i should pass with a collector of reaction on my specific message ?

S

Squid•1/17/23, 7:08 PM

what do you mean by "pass"

H

Hugo4774OP•1/17/23, 7:08 PM

i should go and change my code for...

S

Squid•1/17/23, 7:09 PM

That's what I would do since you're not using a persistent database for each message that you care about

H

Hugo4774OP•1/17/23, 7:09 PM

but i don't understand the utility of Events.MessageReactionAdd then, in which case should we use it ?

SSquid That's what I would do since you're not using a persistent database for each mes...

H

Hugo4774OP•1/17/23, 7:09 PM

yes

S

Squid•1/17/23, 7:10 PM

If you care about listening to reactions as soon as the bot starts, use the client event
If you care about listening to reactions when a command is used, use collectors

H

Hugo4774OP•1/17/23, 7:11 PM

in my case it's when i do my command, i send a message with reactions, i wait for a certain time to catch all reactions to then do something

H

Hugo4774OP•1/17/23, 7:11 PM

so it's case 2 ?

S

Squid•1/17/23, 7:11 PM

Correct
Use the collector's

end

end

event whose first parameter is a Collection of each reaction added since the collector was created

H

Hugo4774OP•1/17/23, 7:12 PM

end is when the filter is "true" ?

H

Hugo4774OP•1/17/23, 7:14 PM

mmh and what's interesting is that in the filter i can check roles of user who react to collect it or no ?

S

Squid•1/17/23, 7:14 PM

yep

H

Hugo4774OP•1/18/23, 7:04 PM

I have this filter condition, i enter to my

collector.on()

collector.on()

collector.on()

collector.on() when i react to A, but when i react to B, i still enter to my

collector.on()

collector.on()

collector.on()

collector.on()

                            const filterReactionCollector = (reaction, user) => {
                                return [emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel;
                            };

                            const collector = theMessage.createReactionCollector({ filterReactionCollector, time: time1 * 1000 });

                            collector.on('collect', (reaction, user) => {
                                console.log([emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel);

                            const filterReactionCollector = (reaction, user) => {
                                return [emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel;
                            };

                            const collector = theMessage.createReactionCollector({ filterReactionCollector, time: time1 * 1000 });

                            collector.on('collect', (reaction, user) => {
                                console.log([emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel);

                            const filterReactionCollector = (reaction, user) => {
                                return [emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel;
                            };

                            const collector = theMessage.createReactionCollector({ filterReactionCollector, time: time1 * 1000 });

                            collector.on('collect', (reaction, user) => {
                                console.log([emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel);

                            const filterReactionCollector = (reaction, user) => {
                                return [emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel;
                            };

                            const collector = theMessage.createReactionCollector({ filterReactionCollector, time: time1 * 1000 });

                            collector.on('collect', (reaction, user) => {
                                console.log([emojiA, emojiB, emojiC, emojiD].includes(reaction._emoji.id)
                                    && usersReaction[user] == undefined
                                    && reaction.message.channel.id == channel);

H

Hugo4774OP•1/18/23, 7:04 PM

Does anyone knows what happens in my filter ?

H

Hugo4774OP•1/18/23, 7:04 PM

it logs true then false but still enter in it

H

Hugo4774OP•1/18/23, 7:06 PM

i must rename filterReactionCollector to filter ?

H

Hugo4774OP•1/18/23, 8:05 PM

that's a good answer ! ty !

Similar Threads

Similar Threads

Similar Threads