Localised names of message commands not used in displayed interaction reply

Shepard commented 2 years ago

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 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

zeylahellyer commented 2 years ago

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

Shepard commented 2 years ago

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.

yonilerner commented 2 years ago

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

jocafamaka commented 2 years ago

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

jocafamaka commented 1 year ago

Is this done with?

As of now, still happening in web and desktop clients:

Works as intented on android...

Smidul commented 1 year ago

It's fixed on canary and ptb and will be on stable soon

infinitestory commented 1 year ago

Oops, forgot to check in here (although it looks like our ticketing system correctly closed the issue). Yes this is fixed, please let me know if you see anything else inconsistent with message commands. I think I made sure everything goes through the same shared pathways so localization should work equally well.

jocafamaka commented 1 year ago

This exact problem now is happenig on modal reply.

I have a command that has parameters that are validated, if passed, a modal is displayed.

When the response occurs in the initial interaction (slash) the name is displayed correctly. But when the response is on modal interaction, the error occurs.

jocafamaka commented 1 year ago

@infinitestory + Seems the bug of context menu is back as well. However, it may be related to the modal response as well.

Client: Web + Desktop PTB

discord / discord-api-docs