Discord.js v14 includes many breaking changes. It now requires Node 16.9 or higher to use, so make sure you upgrade to the latest LTS version. This version of v14 uses the Discord API v10. Errors with intents: // v13 const client = new Client({ intents: [ Intents.FLAGS.GUILDS, Intents.FLAGS.GUILD_MESSAGES, ], }); // OR const client = … Read more
Make sure you enable the message content intent on your developer portal and add the GatewayIntentBits.MessageContent enum to your intents array. Applications ↦ Settings ↦ Bot ↦ Privileged Gateway Intents You’ll also need to add the MessageContent intent: const client = new Client({ intents: [ GatewayIntentBits.DirectMessages, GatewayIntentBits.Guilds, GatewayIntentBits.GuildBans, GatewayIntentBits.GuildMessages, GatewayIntentBits.MessageContent, ], partials: [Partials.Channel], }); If … Read more
Make sure you enable the message content intent on your developer portal and add the GatewayIntentBits.MessageContent enum to your intents array. Applications ↦ Settings ↦ Bot ↦ Privileged Gateway Intents You’ll also need to add the MessageContent intent: const client = new Client({ intents: [ GatewayIntentBits.DirectMessages, GatewayIntentBits.Guilds, GatewayIntentBits.GuildBans, GatewayIntentBits.GuildMessages, GatewayIntentBits.MessageContent, ], partials: [Partials.Channel], });
The node-fetch latest version doesn’t use the require() syntax to import the package. You need to go to your package.json and type { “type”: “module”, } to use the import syntax and import node-fetch, but then you can’t use require for any other packages. You need to work with import statement only. Or you can … Read more
First of all, never show a token of your bot, or try to change it later. Second of all: Try using this. Since the new updated version of discord.js, like version ^13.0, you have to specify client intents: const { Client, Intents } = require(‘discord.js’); const client = new Client({ intents: [Intents.FLAGS.GUILDS, Intents.FLAGS.GUILD_MESSAGES] }); And … Read more
The discord.js api has been updated and there is a better way since .exists() has been deprecated. if (message.member.roles.cache.some(role => role.name === ‘Whatever’)) {} This is better than .find() because .find() returns the role object (or undefined) which is then converted into a boolean. The .some() method returns a boolean by default.
In order for a bot to send a message, you need <client>.send() , the client is where the bot will send a message to(A channel, everywhere in the server, or a PM). Since you want the bot to PM a certain user, you can use message.author as your client. (you can replace author as mentioned … Read more
Your code looks fine, the problem is that the event isn’t triggered. Thats because discord turned off “privileged intents” by default. Some intents are defined as “Privileged” due to the sensitive nature of the data. Those intents are: GUILD_PRESENCES GUILD_MEMBERS One effect of that is what you are experiencing, the not working guildMemberAdd event. The … Read more
You didn’t provide any code that you already tested so I will give you the code for your ready event that will work! client.on(‘ready’, client => { client.channels.get(‘CHANNEL ID’).send(‘Hello here!’); }) Be careful that your channel id a string. Let me know if it worked, thank you! 2020 Jun 13 Edit: A Discord.js update requires … Read more
Updated Luke’s code to Discord.js v12 for anyone else in 2020 who has this same problem const attachment = new Discord .MessageAttachment(‘./card_images/sample.png’, ‘sample.png’); const embed = new Discord.MessageEmbed() .setTitle(‘Wicked Sweet Title’) .attachFiles(attachment) .setImage(‘attachment://sample.png’); message.channel.send({embed});