Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing mention_roles in message snapshots #7193

Open
MinnDevelopment opened this issue Oct 4, 2024 · 1 comment
Open

Missing mention_roles in message snapshots #7193

MinnDevelopment opened this issue Oct 4, 2024 · 1 comment
Labels
bug synced Synced to internal tracker

Comments

@MinnDevelopment
Copy link
Contributor

Description

The message snapshots seem to sometimes not include the required mention_roles property, if the message is forwarded from another guild.

  "message_snapshots": [
    {
      "message": {
        "components": [],
        "attachments": [],
        "mentions": [],
        "flags": 0,
        "type": 0,
        "embeds": [],
        "edited_timestamp": null,
        "content": "<@&1291689786570047529>",
        "timestamp": "2024-10-04T09:20:03.181000+00:00"
      }
    }
  ],

This property is required according to the spec in MinimalContentMessageResponse.

Steps to Reproduce

  1. Create a new guild with one role
  2. Mention the role
  3. Forward the message to another server the bot has access to

Expected Behavior

The required properties should be present.

Current Behavior

Missing mention_roles

Screenshots/Videos

No response

Client and System Information

Gateway v10

@MinnDevelopment
Copy link
Contributor Author

For more context, this is only observed on gateway message create events. For GET requests the mention_roles list is present and even includes the IDs of the mentioned roles.

@Rodentman87 Rodentman87 added the synced Synced to internal tracker label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug synced Synced to internal tracker
Projects
None yet
Development

No branches or pull requests

2 participants