[Bug]: SocketMessageComponent.Message.ReferencedMessage always returns null
drizzle-mizzle opened this issue · 1 comments
drizzle-mizzle commented
Check The Docs
- I double checked the docs and couldn't find any useful information.
Verify Issue Source
- I verified the issue was caused by Discord.Net.
Check your intents
- I double checked that I have the required intents.
Description
When you get a message from an executed button:
...it has a Reference
, but there's no ReferencedMessage
.
Example:
Version
3.9.0
Working Version
Logs
Sample
private async Task HandleButton(SocketMessageComponent component)
{
var message = component.Message;
var messageRef = message.ReferencedMessage;
// ...
}
Packages
Misha-133 commented
That's not a bug.
API doesn't send the referenced message with interaction payload