Misleading information with regards to mentioning users in reference #4734
Comments
|
Can reproduce. Any platform, any Discord branch :-) |
|
After reviewing the server nicknames implementation it appears this is not a client markdown implementation, but rather a flag for the server to consume. I'm looking into if this is expected behavior, and if so we can update the documentation to properly reflect its function. |
|
It appears that Android follows the behaviour of omitting the ! |
|
After speaking with our product team we've already transitioned away from using |
|
What about older messages that still use the older syntax or bots that explicitly use the older syntax? Wouldn't a note be better just to say that it can optionally include a |
For more information, see discord/discord-api-docs#4734
### UPDATED - Switched project to ESM module and updated ECMA to 2022 - All permission bitfields in the configuration files are now pascal cases due to a `discord.js` upgrade - TypeScript builds will no longer check for `config.json` inconsistencies - Explicit `inline` properties for message embed fields - Log messages with Discord-related properties (such as `Guild` or `TextChannel`) will now show only an object with its corresponding ID instead of the entire object itself - Channel detection mechanism, where the bot would guess an acceptable channel based on its features instead of the channel type itself - When posting a request to Discord via webhooks, the form data will be copied before it is sent, in case things go wrong and we can go back to reference - When posting a request to Discord via webhooks, the entire instance will be bottlenecked to prevent 429 errors ### FIXED - Generate output message was sent even when `log-level` was set below `30` - Broadcast alerts skipped/continued task log message was sending an entire instance instead of the current user ID - Return type of "toString()" on channels due to [this issue](discordjs/discord.js#7836) - Impersonator alert failed regex rule match log message was not using cleaned nickname or username - Server tools messages with replies will sometimes fail due to a race condition where the command message was deleted before the reply message was sent ### ADDED - Scammer alert feature - Threads and invites are now cached with a lifetime of 30 days - Helper function to convert entity types and status from scheduled events ### REMOVED - Detection for guild members with nicknames `<@!12345>` due to [this issue](discord/discord-api-docs#4734) - Unnecessary log detail (`message.member`) for message proxy invoke function
Description
When looking at the formatting reference for message, I noticed that there seemed to be a difference between mentioning users with an exclamation mark (
<@!ID>) and without the exclamation mark (<@ID>), where mentioning a user without the exclamation mark seemed like it would display the username and not the guild member's nickname. This is not the case, and both give the same result, hence the description is misleading.Steps to Reproduce
https://discord.com/developers/docs/reference#message-formatting - The table contains the misleading information
Expected Behavior
In theory, either
<@ID>should show the user's username, or the description in the documentation should be adjusted.Current Behavior
In reality, the information is, well, wrong.
Screenshots/Videos
No response
Client and System Information
Windows 11 Pro, Edge 99.0.1150.55
The text was updated successfully, but these errors were encountered: