discord-api-docs icon indicating copy to clipboard operation
discord-api-docs copied to clipboard

Localised names of message commands not used in displayed interaction reply

Open Shepard opened this issue 1 year ago • 2 comments

Description

When I use a slash command, the bot's interaction reply will be shown with a little header in the client: It says "$username used /blah". If the command has a localised name in my client's language, that name is shown in that header. (I couldn't test what language it is shown in for other users - hopefully the one for their locale.)

However, if I use a message command and the bot replies, the header uses the default name of the command, not the localised one. (In the context menu where I can click on the command, the correct localised name is used.)

Steps to Reproduce

  • Set up a bot with a message command that has name_localizations in, say, the 'de' locale. Program the bot such that it will reply with a message to interactions received for that command.
  • Set your Discord desktop client's language to German.
  • Right-click on a message, select "Apps" and find the message command in question. Notice that the German name is shown here.
  • Click the message command.

Expected Behavior

The bot's reply should show a line above it that reads "$username verwendet $commandNameInGerman". (Side note: The German translation of this line uses present tense whereas the English one uses past tense.)

Current Behavior

The bot's reply shows a line above it that reads "$username verwendet $defaultCommandName".

Screenshots/Videos

localised slash command name in auto complete localised slash command name in interaction reply localised message command name in context menu default message command name in interaction reply

Client and System Information

Desktop program Stable 141352 (cf83f8c) Host 1.0.9006 Windows 10 64-Bit (10.0.19043) With build override feature/web-slash-command-localization

Shepard avatar Aug 12 '22 15:08 Shepard

Hi, we believe this has been fixed already. Can you confirm whether this is still an issue?

zeylahellyer avatar Sep 09 '22 18:09 zeylahellyer

Hi, we believe this has been fixed already. Can you confirm whether this is still an issue?

Sadly this is still an issue as described.

Shepard avatar Sep 11 '22 10:09 Shepard

We had a similar issue with slash commands that was fixed. We'll look into fixing this for non-slash commands.

yonilerner avatar Oct 04 '22 01:10 yonilerner

@yonilerner any updates on this? Because it's still pretty much a thing.

jocafamaka avatar Oct 25 '22 16:10 jocafamaka