From 80ae5384cb06a42b86f5cdcf93f82fe0f25f1c18 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Fri, 9 Sep 2022 18:25:46 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/dice.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/web/corefork.telegram.org/api/dice.html b/data/web/corefork.telegram.org/api/dice.html index a556327e3e..f0da84d500 100644 --- a/data/web/corefork.telegram.org/api/dice.html +++ b/data/web/corefork.telegram.org/api/dice.html @@ -64,7 +64,7 @@ The returned stickerset will contain a set of animated stickers, one for each of

If a user attempts to send a single emoji from the ones specified in emojies_send_dice, the dice should be sent using messages.sendMedia, providing the dice emoji to the emoticon field.

Incoming dice stickers will be received as a messageMediaDice constructor, along with a randomly generated server-side value, ranging from 1 to the maximum allowed value for this type of dice.
Clients should display the correct dice animated sticker for the specified value: since dice values start from 1, and the first animated sticker in dice stickerset is the preview, value can be used to directly index the documents sticker array from the animated stickerset.

-

The emojies_send_dice_success configuration parameter contains more info about dice emojis other than the basic 🎲:

+

The emojies_send_dice_success configuration parameter contains more info about dice emojis other than the basic 🎲: 

    "emojies_send_dice_success": {
         "\ud83c\udfaf": {
             "value": 6,