This issue proposes the addition of a .twemoji <codepoint|emoji> command. This will be useful for viewing and downloading Twemojis (the default emojis on Discord, which we base a lot of our branding on).
Proposed Implementation
Invocation
An invocation of the command could look something like this. These are all common formats for specifying an emoji. However, I might limit the available formats, in order to make things simpler.
.twemoji 😁
.twemoji \U0001f9d0
.twemoji 1f9d0
.twemoji U+1f9d0
This would work with multi-character emojis as well:
.twemoji ☺️
.twemoji \u263a\ufe0f
.twemoji U+1F46A U+1F3FF
Bot response
The bot will respond with an embed containing the following information about the given Twemoji:
- Emoji name (if I can find a simple way to fetch it)
- Download link to the source file (as an svg)
- A preview of the emoji
- The emoji codepoint
Including the codepoint will be occasionally useful when the user specifies the emoji of interest through an emoji (eg. "🥰" instead of "1f970"). The color of the embed will be blue, to match Twitter's color scheme, since Twitter are the creators of Twemojis.
Additional Details
It's possible to add support for specifying multiple emojis in the same call to the command. The emojis could then be separated using pagination.
However, considering the niche use cases for this feature, I think it's better to keep the implementation simple. If we against all odds find a significant need for specifying multiple emojis, in the future, I'm open to discussing the possibility of adding pagination at that point in time.
Would you like to implement this yourself?
This issue proposes the addition of a
.twemoji <codepoint|emoji>command. This will be useful for viewing and downloading Twemojis (the default emojis on Discord, which we base a lot of our branding on).Proposed Implementation
Invocation
An invocation of the command could look something like this. These are all common formats for specifying an emoji. However, I might limit the available formats, in order to make things simpler.
This would work with multi-character emojis as well:
Bot response
The bot will respond with an embed containing the following information about the given Twemoji:
Including the codepoint will be occasionally useful when the user specifies the emoji of interest through an emoji (eg. "🥰" instead of "1f970"). The color of the embed will be blue, to match Twitter's color scheme, since Twitter are the creators of Twemojis.
Additional Details
It's possible to add support for specifying multiple emojis in the same call to the command. The emojis could then be separated using pagination.
However, considering the niche use cases for this feature, I think it's better to keep the implementation simple. If we against all odds find a significant need for specifying multiple emojis, in the future, I'm open to discussing the possibility of adding pagination at that point in time.
Would you like to implement this yourself?