Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

134
Vistas
TypeError: bot.commands.get(...).run is not a function

I've just been trying to make a command handler on discord.js and whenever I run the bot, it throws

TypeError: bot.commands.get(...).run is not a function

Here's the bottom of the code on where the error is happening.

bot.on("message", async message => {

    if(message.author.bot) return;   
    if(message.channel.type === 'dm') return;

    if(message.content.startsWith(prefix)) {
        const args = message.content.slice(prefix.length).trim().split(/ +/);

        const command = args.shift().toLowerCase();

        if(!bot.commands.has(command)) return;


        try {
            bot.commands.get(command).run(bot, message, args);
        } catch (error){
            console.error(error);
        }
    }
})

bot.login(token);
about 4 years ago · Juan Pablo Isaza
1 Respuestas
Responde la pregunta

0

It seems like you command handler is a little bit incomplete. Here is how I have mine setup, you can try it and tell me if it works (I explain everything with the comments :

// your bot.js or main.js file
const bot = new Discord.Client(); // I setup the bot client
bot.commands = new Discord.Collection(); // I create a collection with all the commands

const commandsFiles = fs.readdirSync('./commands').filter(file => file.endsWith('.js')); 
// In my project tree, I define all the files with the .js extension in this folder as command files. I will add a file (.js) to this folder for each command I want to create. For example, there will be './commands/ping.js' inside.

for(const file of commandsFiles){
  const command = require(`./commands/${file}`);
  client.commands.set(command.name, command);
}
// For each command file detected, I add it's name and it's path to my client.commands collection


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

  if(message.author.bot) return;   
  if(message.channel.type === 'dm') return;

  if(message.content.startsWith(prefix)) {

    const args = message.content.slice(prefix.length).trim().split(/ +/); 
    const command = args.shift().toLowerCase();

    if(!bot.commands.has(command)) return;
    // if the collection doesn't have a command with this name, return

    try {
      bot.commands.get(command).run(bot, message, args);
      // I get the command object defined previously in the 'for' loop, and I execute the run function with bot, message and args as arguments
    } catch (error){
      console.error(error);
    }
  }

}

Now that you have your command handle set up, for each command that you want to create, add a file inside the ./commands/ folder (for example, ./commands/ping.js, don't forget the .js part). In this newly created file, write :

module.exports = {
  name : 'ping',
  description : 'Ping command',
  run(bot, message, args) {

  // the code to be executed

}

Here you can see that we define an object, that will be used by the command handler.

When we do client.commands.set(command.name, command) (in bot.js or main.js), we use the name defined here.

When we do client.commands.get(command).run(bot, message, args), we run the run function defined inside of the module.export object of the targetted command file.

Don't hesitate to tell me if there's anything you don't understand.

about 4 years ago · Juan Pablo Isaza Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda