GUILDS intent is not enough to receive messages. You will also need GUILD_MESSAGES intent for messages: const client = new Client({ intents: [ Intents.FLAGS.GUILDS, Intents.FLAGS.GUILD_MESSAGES ] })
repl.it uses node v12.22.1 but the nullish coalescing operator (??), is relatively new and was added in node v14. So to use the ?? operator you need to update node in repl.it. Which you can do by following this repl.it forum post by lukenzy. Create a file and name it .replit Inside it, copy and … Read more
The send code has been changed again. Both the items in the question as well as in the answers are all outdated. For version 12, below will be the right code. The details about this code are available in this link. To send a message to specific channel const channel = <client>.channels.cache.get(‘<id>’); channel.send(‘<content>’); To send … Read more
The error is coming from discord.js and it’s because you’re using an older version of Node.js. The logical nullish assignment operator (??=) is only available in node v15+. You might think that you’re using the latest version of Node.js, but Heroku says that “if a Node version isn’t specified in the engine, the 14.x release … Read more
Discord.js no longer supports voice. You need to use the other package they made (@discordjs/voice). You can import joinVoiceChannel from there. //discord.js and client declaration const { joinVoiceChannel } = require(‘@discordjs/voice’); client.on(‘messageCreate’, message => { if(message.content === ‘!join’) { joinVoiceChannel({ channelId: message.member.voice.channel.id, guildId: message.guild.id, adapterCreator: message.guild.voiceAdapterCreator }) } })
Discord.js v13 has a lot of changes, and those are only a few. Before updating to v13, you should change the following things //member.hasPermission(“SEND_MESSAGES”) member.permissions.has(“SEND_MESSAGES”) //channel.send(someEmbed) / channel.send({embed: someEmbed}) channel.send({ embeds: [someEmbed] }) //make sure it’s an array! //client.on(“message”, msg => {}) client.on(“messageCreate”, msg => {}) //channel.send(user) channel.send(user.toString()) //const client = new Client() const { … Read more
Here are some of the most common breaking changes introduced in Discord.js v12 that people run into. Managers Properties such as Client#users and Guild#roles are now managers, instead of the cached Collection of items. To access this collection, use the cache property: const user = client.users.cache.get(‘123456789012345678’) const role = message.guild.roles.cache.find(r => r.name === ‘Admin’) In … Read more
In discord.js v13, it is necessary to specify an intent in new discord.Client(). Events other than the specified intent will not be received. ClientOptions Intents#FLAGS To receive the message event, you will need the GUILDS and GUILD_MESSAGES intents. You mean… const client = new Discord.Client({ partials: [‘MESSAGE’, ‘CHANNEL’, ‘REACTION’], intents: [Discord.Intents.FLAGS.GUILDS, Discord.Intents.FLAGS.GUILD_MESSAGES] }); Or to … Read more
The Issue: One of the prerequisites for using Discord.js v13 is that you need to use NodeJS v16.6 or higher (emphasis mine): v13 requires Node 16.6 or higher to use, so make sure you’re up to date. To check your Node version, use node -v The Fix: The fix is to update your node version, … Read more
🤖 Discord is now enforcing privileged intents What are intents? Maintaining a stateful application can be difficult when it comes to the amount of data you’re expected to process, especially at scale. Gateway Intents are a system to help you lower that computational burden. Gateway intents allow you to pick and choose what events you … Read more