Browse Source

Fix for misleading behaviour in the emoji guide

+ Original lines stated that sending a emoji wrapped in colon will not be parsed, but that was incorrect; replaced with reactions instead of sending messages as the example
pull/1161/head
Still Hsu 7 years ago
parent
commit
171dd1f51e
No known key found for this signature in database GPG Key ID: 8601A145FDA95209
1 changed files with 3 additions and 3 deletions
  1. +3
    -3
      docs/guides/emoji/emoji.md

+ 3
- 3
docs/guides/emoji/emoji.md View File

@@ -14,9 +14,9 @@ depending on the type of emoji, they are sent in an entirely
different format.

What does this all mean? It means that you should know that by
sending a string like `“Discord.Net is :ok_hand:”` will **NOT**
translate to `Discord.Net is 👌`; rather, it will be treated as-is,
like `Discord.Net is :ok_hand:`.
reacting with a string like `“:ok_hand:”` will **NOT** automatically
translate to `👌`; rather, it will be treated as-is,
like `:ok_hand:`, thus the server will return a `400 Bad Request`.

## Emoji



Loading…
Cancel
Save