Implementing Slash Commands in Discord.js v14: Registration, Handling, and Recovery

Desired Outcome

You need a Discord bot built with discord.js v14 that registers a slash command through Discord's REST API and responds to it in a guild. The command must appear in the Discord client, receive an interactionCreate event, and send a reply before the initial three-second response window closes. This guide focuses on guild-scoped registration because it propagates in seconds, making it suitable for development and targeted deployments.

Prerequisites

• Node.js 18 or newer; discord.js v14 depends on modern JavaScript features.
• An installed Discord application with a bot user. Retrieve the bot token, application (client) ID, and a test guild (server) ID from the Developer Portal.
• The Guilds gateway intent enabled in the Developer Portal under Bot > Privileged Gateway Intents. Slash-command interactions arrive over the guild gateway; without this intent the client will not receive them.
• Project dependencies: discord.js, @discordjs/rest, discord-api-types, and dotenv for loading the token from .env.

Store the token in an environment variable. Never commit it to source control. A .env file loaded by process.env is the minimum safe pattern.

Registering the Command

Slash commands are created with a REST call, not by sending a message. Create a deployment script, for example deploy-commands.js, and run it with node deploy-commands.js. The script needs DISCORD_TOKEN, CLIENT_ID, and GUILD_ID.

// deploy-commands.js
require('dotenv').config();
const { REST, Routes } = require('discord.js');

const rest = new REST({ version: '10' }).setToken(process.env.DISCORD_TOKEN);

const commands = [
  {
    name: 'ping',
    description: 'Replies with Pong!',
  },
];

(async () => {
  try {
    await rest.put(
      Routes.applicationGuildCommands(process.env.CLIENT_ID, process.env.GUILD_ID),
      { body: commands },
    );
    console.log('Successfully registered application commands.');
  } catch (error) {
    console.error(error);
  }
})();

Guild commands propagate within seconds. Global commands can take up to an hour to appear across all guilds, so use guild scope while iterating. Discord enforces rate limits on bulk registration; a 429 response means you have sent too many requests in the current window. Spread registrations over time or delete stale commands before adding new ones.

Command Definition Details

Each command object requires a name and description. To restrict who can invoke it, add default_member_permissions as a permission bitfield string, or omit it to allow all members by default. For subcommands and typed options, use ApplicationCommandOptionType from discord-api-types when building the payload.

Handling the Interaction

Create the client with the Guilds intent and listen for interactionCreate. Because the initial response must arrive within three seconds, either reply immediately or defer if the operation is slow.

// index.js
require('dotenv').config();
const { Client, GatewayIntentBits, Events } = require('discord.js');

const client = new Client({ intents: [GatewayIntentBits.Guilds] });

client.once(Events.ClientReady, () => {
  console.log(`Logged in as ${client.user.tag}`);
});

client.on(Events.InteractionCreate, async (interaction) => {
  if (!interaction.isChatInputCommand()) return;

  if (interaction.commandName === 'ping') {
    await interaction.reply('Pong!');
  }
});

client.login(process.env.DISCORD_TOKEN);

Run the bot with node index.js. The process must stay alive to maintain the gateway connection. If the command logic takes longer than three seconds—such as an external API call—call interaction.deferReply() first, then use interaction.editReply() when the result is ready. Wrap the handler body in a try/catch block and log the stack trace; an unhandled promise rejection inside the listener can terminate the process.

Reading Options

When a command includes options, read them from interaction.options. For example, a string option declared as name: 'target' is retrieved with interaction.options.getString('target'). Subcommands are nested under interaction.options.getSubcommand().

Expected Checks

After running the deployment script, open the target guild in the Discord client and type /ping in a text channel. The command should appear in the autocomplete list within seconds. Invoking it should produce a Pong! reply from the bot. In the bot process logs, the ClientReady event confirms the gateway connection, and any errors thrown inside the interaction handler should be caught and logged with stack traces.

To verify the interaction pipeline independently of command logic, add a temporary console.log(interaction) inside the interactionCreate listener. If the log does not appear when you invoke the command, the gateway connection or intent configuration is the likely cause.

Recovery Options

Command Not Appearing

If the command does not show up, confirm the GUILD_ID in the deployment script matches the server where you are testing. Check the script output for HTTP errors. If you registered globally instead of per-guild, wait up to an hour or re-register with the guild route.

Silent Interaction Failures

If the command is visible but the bot does not respond, verify that the client was constructed with GatewayIntentBits.Guilds and that the same intent is enabled in the Developer Portal. A missing intent causes the bot to miss the interaction entirely. Also confirm the event name is interactionCreate and that the command name string matches exactly.

Permission Mismatches

If members report that the command is hidden or unusable, inspect default_member_permissions. A restrictive bitfield prevents users without those permissions from seeing or running the command. Remove the field or set it to '0' to allow everyone, then re-register.

Rate Limits and Cleanup

If you receive 429 errors during registration, pause and retry after the indicated delay. To remove a command, send a DELETE request to the same guild route, or overwrite the guild command list with an empty array [] to clear all guild-scoped commands. This is a state-changing operation; only clear commands you own.

Limitations

This guide assumes discord.js v14 on Node.js 18+. Discord may adjust API rate limits, intent requirements, or interaction timeouts over time. The MessageContent intent is unnecessary for slash commands and should remain disabled unless your bot reads message text. Always test permission and option logic in a private guild before deploying globally.