Expand resolved data for "mentionable" entities in message data #3564
Unanswered
SinisterRectus
asked this question in
API Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
According to https://support-dev.discord.com/hc/en-us/articles/4404772028055, access to message
content
,embeds
,attachments
, andcomponents
will soon be restricted. Presumably,mentions
,mention_roles
, andmention_channels
will not be restricted since I don't see anything about these in the article.My library (Discordia) provides mention data in a way where message content is parsed for all relevant
<>
bracket style mentions including users, roles, channels, emojis, and datetimes in the order that they appear. If message content becomes unavailable, my users cannot reliably access mentioned data. I would have to expose only what the Discord API provides via thementions
,mention_roles
, andmention_channels
objects. That's not necessarily a bad thing, but these fields are limited: Emojis and datetimes are excluded, channels are limited to only announcement crossposts, roles are limited to only their IDs, and the mentions are not presented in a reliable order.Based on this, I'm requesting (or at least opening a discussion for) the inclusion of richer mention resolution via the regular message API independent of the slash commands API. I understand that this would add an extra burden on the server-side content parser, so if this is not possible, then maybe expand the mention resolution in slash commands, as they too are limited to only users, channels, and roles (emojis and datetimes are excluded).
Beta Was this translation helpful? Give feedback.
All reactions