Multi language Bot

Hey everyone,
I’m working on a Discord bot with multiple commands that supports multiple languages. Each server can set its own language, and I need to ensure that commands and other content are displayed in the correct language.

Currently, after every relevant action (e.g., an unban), I call deployCommands({ guildId }) to update the commands with the right translations.

My bot has multiple commands (unban is just an example).

Issue: deployCommands({ guildId }) is triggered every time an action happens → This leads to a lot of API requests, especially when the bot is on many servers.

Goal: I want to update commands less frequently while still ensuring they are in the correct language.

My questions:

Is there a more efficient way to handle language-dependent commands without redeploying after every action?

Has anyone worked with batching or delayed deployments for multilingual bots?

How can I make sure commands update when a language change happens, but without unnecessary redeployments?

I’d really appreciate any advice!

export async function deployCommands({ guildId }: DeployCommandsProps) {
  try {
    console.log(
      `Started refreshing application (/) commands for guild ${guildId}.`
    );

    const commandsData = await Promise.all(
      Object.values(commands).map((command) => command.getCommandData(guildId))
    );

    await rest.put(
      Routes.applicationGuildCommands(config.DISCORD_CLIENT_ID!, guildId),
      { body: commandsData }
    );

    console.log(
      `Successfully reloaded application (/) commands for guild ${guildId}.`
    );
  } catch (error) {
    console.error("Error deploying commands:", error);
  }
}

export async function deployCommands({ guildId }: DeployCommandsProps) {
  try {
    console.log(
      `Started refreshing application (/) commands for guild ${guildId}.`
    );

    const commandsData = await Promise.all(
      Object.values(commands).map((command) => command.getCommandData(guildId))
    );

    await rest.put(
      Routes.applicationGuildCommands(config.DISCORD_CLIENT_ID!, guildId),
      { body: commandsData }
    );

    console.log(
      `Successfully reloaded application (/) commands for guild ${guildId}.`
    );
  } catch (error) {
    console.error("Error deploying commands:", error);
  }
}

export async function deployCommands({ guildId }: DeployCommandsProps) {
  try {
    console.log(
      `Started refreshing application (/) commands for guild ${guildId}.`
    );

    const commandsData = await Promise.all(
      Object.values(commands).map((command) => command.getCommandData(guildId))
    );

    await rest.put(
      Routes.applicationGuildCommands(config.DISCORD_CLIENT_ID!, guildId),
      { body: commandsData }
    );

    console.log(
      `Successfully reloaded application (/) commands for guild ${guildId}.`
    );
  } catch (error) {
    console.error("Error deploying commands:", error);
  }
}

export async function deployCommands({ guildId }: DeployCommandsProps) {
  try {
    console.log(
      `Started refreshing application (/) commands for guild ${guildId}.`
    );

    const commandsData = await Promise.all(
      Object.values(commands).map((command) => command.getCommandData(guildId))
    );

    await rest.put(
      Routes.applicationGuildCommands(config.DISCORD_CLIENT_ID!, guildId),
      { body: commandsData }
    );

    console.log(
      `Successfully reloaded application (/) commands for guild ${guildId}.`
    );
  } catch (error) {
    console.error("Error deploying commands:", error);
  }
}

d.js toolkit•3/15/25, 5:58 PM

What's your exact discord.js

npm list discord.js

npm list discord.js

and node

node -v

node -v

version?

Not a discord.js issue? Check out #other-js-ts.
Consider reading #how-to-get-help to improve your question!
Explain what exactly your issue is.
Post the full error stack trace, not just the top part!
Show your code!
Issue solved? Press the button!
```
✅
```
```
✅
```
Marked as resolved by staff

Samtino•3/15/25, 6:07 PM

Instead of setting a language for an entire server, you can just add locales to your commands and responses so it responds in the language of the user (if available)

d.js docsAPP•3/15/25, 6:10 PM

:guide: Slash Commands: Advanced command creation - Localizations
The names and descriptions of slash commands can be localized to the user's selected language. You can find the list of accepted locales on the discord API documentationopen in new window.
read more

Mark•3/15/25, 6:13 PM

why would you be deploying after every interaction? why not just re-deploy when a specific command (eg.

/set language

/set language

) is used?

SSamtino Instead of setting a language for an entire server, you can just add locales to ...

TercanOP•3/15/25, 6:13 PM

Thank you for the suggestion! I appreciate it, but that's a bit different from the feature I'm aiming for. I want to allow the server admin to set a global language for their server, which then gets mapped to the guild ID in Redis. After that, for every command or event reaction, I would use a Translation key instead of a plain string. This Translation key, along with the guild ID, is passed to my translation pipeline (i18n) for translation. Once that's done, I would need to redeploy the command. Hope that clarifies things!

Samtino•3/15/25, 6:15 PM

And I was just about to say that. Your command list should only change either when you as the developer add or modify a command (thus needing to redeploy on all servers), or if a server admin changes the language of their server.

Checking and redeploying the commands every single time a command is used is just bad design on your part. You're likely doing something wrong in your command flow

SSamtino And I was just about to say that. Your command list *should* only change either ...

TercanOP•3/15/25, 6:18 PM

That's the issue I'm facing. I no longer want to do that, but I can't seem to find a solution that achieves the same result without having to redeploy the command after every use.

TTercan That's the issue I'm facing. I no longer want to do that, but I can't seem to fi...

Samtino•3/15/25, 6:18 PM

You should:

Only redeploy the commands by manually triggering a script (like
```
npm run deploy
```
```
npm run deploy
```
) whenever you push a new version of the bot to prod
Add a
```
/set-language (language)
```
```
/set-language (language)
```
or similar command for server admins to use (should be on a cooldown to avoid rate limiting)

Samtino•3/15/25, 6:20 PM

On your backend, you can fetch the locale from your redis DB with the interaction.guild.id and respond with the corresponding language. But with the /set-language command, you can change the language of the command itself. If set up correctly, you shouldn't even have to change your command handling in any way. The "backend" of the interaction should run identically

Samtino•3/15/25, 6:21 PM

But again. A "deployCommands" function/script should NEVER be run automatically. It should always be triggered either by you or someone intentionally doing so.

You should be the only one who can update ALL servers, and server admins should be able to update theirs

TercanOP•3/15/25, 6:23 PM

The execution of the command isn't the issue; it's more about the building of the command, which needs to be redeployed. Here's an example:

export async function getCommandData(guildId: string) {
  const description = await translate("COMMANDS.BAN.DESC", guildId);
  const userToBanDesc = await translate("COMMANDS.BAN.OPTIONS.USER", guildId);
  const banReasonDesc = await translate("COMMANDS.BAN.OPTIONS.REASON", guildId);
  return new SlashCommandBuilder()
    .setName("ban")
    .setDescription(description)
    .addMentionableOption((option) =>
      option.setName("user").setDescription(userToBanDesc).setRequired(true)
    )
    .addStringOption((option) =>
      option.setName("reason").setDescription(banReasonDesc).setRequired(false)
    )
    .setDefaultMemberPermissions(PermissionFlagsBits.BanMembers)
    .setContexts(InteractionContextType.Guild);
}

export async function getCommandData(guildId: string) {
  const description = await translate("COMMANDS.BAN.DESC", guildId);
  const userToBanDesc = await translate("COMMANDS.BAN.OPTIONS.USER", guildId);
  const banReasonDesc = await translate("COMMANDS.BAN.OPTIONS.REASON", guildId);
  return new SlashCommandBuilder()
    .setName("ban")
    .setDescription(description)
    .addMentionableOption((option) =>
      option.setName("user").setDescription(userToBanDesc).setRequired(true)
    )
    .addStringOption((option) =>
      option.setName("reason").setDescription(banReasonDesc).setRequired(false)
    )
    .setDefaultMemberPermissions(PermissionFlagsBits.BanMembers)
    .setContexts(InteractionContextType.Guild);
}

SSamtino But again. A "deployCommands" function/script should NEVER be run automatically....

TercanOP•3/15/25, 6:24 PM

Okay, that’s new to me. If I can solve the translation issue, the problem should be resolved. Thank you for clarifying!

TercanOP•3/15/25, 6:26 PM

I’m not sure if my brain isn’t working properly right now, but I haven’t been able to find a solution that doesn’t require redeploying the commands

Samtino•3/15/25, 7:10 PM

You're going to have to redeploy the commands for that server at some point. Avoiding that is impossible if you want to avoid using the built in

locales

locales

settings and instead replace the commands entirely with a different language

I don't know the exact code to do this as I haven't personally done anything with translations, but the snippets you sent aren't inherently problematic. But the exact process to use i18n is something I haven't done before..

But I want to cycle back around...why do you not want to use locales, as they avoid this entire process since you can add all of the translations for the command ahead of time, and then each user can see in their own native language

const command: Command = {
  data: new SlashCommandBuilder()
    .setName('ban')
    .setNameLocalizations({
      de: 'verbot',
    })
    .setDescription('Ban a target user')
    .setDescriptionLocalizations({
      de: 'Bannt einen Benutzer',
    })
    .addUserOption((option) =>
      option
        .setName('target')
        .setNameLocalizations({
          de: 'Ziel',
        })
        .setDescription('The target user')
        .setDescriptionLocalizations({
          de: 'Der Ziel',
        })
        .setRequired(true)
    )

    .addStringOption((option) =>
      option
        .setName('reason')
        .setNameLocalizations({
          de: 'Grund',
        })
        .setDescription('The reason for the ban')
        .setDescriptionLocalizations({
          de: 'Der Grund',
        })
        .setRequired(true)
    ),
};

const command: Command = {
  data: new SlashCommandBuilder()
    .setName('ban')
    .setNameLocalizations({
      de: 'verbot',
    })
    .setDescription('Ban a target user')
    .setDescriptionLocalizations({
      de: 'Bannt einen Benutzer',
    })
    .addUserOption((option) =>
      option
        .setName('target')
        .setNameLocalizations({
          de: 'Ziel',
        })
        .setDescription('The target user')
        .setDescriptionLocalizations({
          de: 'Der Ziel',
        })
        .setRequired(true)
    )

    .addStringOption((option) =>
      option
        .setName('reason')
        .setNameLocalizations({
          de: 'Grund',
        })
        .setDescription('The reason for the ban')
        .setDescriptionLocalizations({
          de: 'Der Grund',
        })
        .setRequired(true)
    ),
};

TercanOP•3/15/25, 7:12 PM

Are you german?

Samtino•3/15/25, 7:13 PM

I am not...those translations were made using Copilot....so I don't know for sure if that's correct in any way

NyR•3/15/25, 7:17 PM

If I understand your issue correctly? You want to deploy commands (names, description) according to language chosen by the server admins or just the responses of the commands?

NNyR If I understand your issue correctly? You want to deploy commands (names, descri...

TercanOP•3/15/25, 7:43 PM

The responses already go through the Pipeline so there is no Problem only for the Description, Name…

TercanOP•3/15/25, 7:44 PM

But I think I will just make it for each user with the locales just as samtino mentioned

NyR•3/15/25, 7:51 PM

That's the correct approach.

export async function getCommandData(guildId: string) { const description = await translate("COMMANDS.BAN.DESC", guildId); const userToBanDesc = await translate("COMMANDS.BAN.OPTIONS.USER", guildId); const banReasonDesc = await translate("COMMANDS.BAN.OPTIONS.REASON", guildId); return new SlashCommandBuilder() .setName("ban") .setDescription(description) .addMentionableOption((option) => option.setName("user").setDescription(userToBanDesc).setRequired(true) ) .addStringOption((option) => option.setName("reason").setDescription(banReasonDesc).setRequired(false) ) .setDefaultMemberPermissions(PermissionFlagsBits.BanMembers) .setContexts(InteractionContextType.Guild); }

const command: Command = { data: new SlashCommandBuilder() .setName('ban') .setNameLocalizations({ de: 'verbot', }) .setDescription('Ban a target user') .setDescriptionLocalizations({ de: 'Bannt einen Benutzer', }) .addUserOption((option) => option .setName('target') .setNameLocalizations({ de: 'Ziel', }) .setDescription('The target user') .setDescriptionLocalizations({ de: 'Der Ziel', }) .setRequired(true) ) .addStringOption((option) => option .setName('reason') .setNameLocalizations({ de: 'Grund', }) .setDescription('The reason for the ban') .setDescriptionLocalizations({ de: 'Der Grund', }) .setRequired(true) ), };

Multi language Bot

Similar Threads

Similar Threads

Similar Threads