diff --git a/data/web/corefork.telegram.org/api/custom-emoji.html b/data/web/corefork.telegram.org/api/custom-emoji.html index bb4046bd34..d185d6d505 100644 --- a/data/web/corefork.telegram.org/api/custom-emoji.html +++ b/data/web/corefork.telegram.org/api/custom-emoji.html @@ -45,6 +45,7 @@

Telegram allows including animated and static custom emojis inside of messages.

+

Custom emoji entities

messageEntityCustomEmoji#c8cf05f8 offset:int length:int document_id:long = MessageEntity;
 
 document#8fd4c4d8 flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:long thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
diff --git a/data/web/corefork.telegram.org/api/effects.html b/data/web/corefork.telegram.org/api/effects.html
index 763d6f288e..2d6911a582 100644
--- a/data/web/corefork.telegram.org/api/effects.html
+++ b/data/web/corefork.telegram.org/api/effects.html
@@ -66,6 +66,7 @@
 

Use messages.getAvailableEffects to fetch the full list of message effects that may be used.

Clients should re-invoke the method (re-using the hash returned from the previous method call) to check for updates in the effects list at most once an hour (or if a message with an unknown effect is received).

Info about each effect is stored in the availableEffect constructor, identified by its id field: this ID should then be passed to the effect field of messages.sendMessage, messages.sendMedia, messages.sendMultiMedia to attach the effect to the message, in the effect field.

+

All long IDs of availableEffect except for id are document.ids from the containing messages.availableEffects constructor.

Each effect has the following info, described by the fields of availableEffect as follows:

  • Emoji: specified in emoticon, used to quickly search for effects.
  • diff --git a/data/web/corefork.telegram.org/api/stickers.html b/data/web/corefork.telegram.org/api/stickers.html index 5a40850441..c0805008c7 100644 --- a/data/web/corefork.telegram.org/api/stickers.html +++ b/data/web/corefork.telegram.org/api/stickers.html @@ -111,7 +111,7 @@

    It should be played the first time the sticker scrolls into view; it should be played again if the chat is closed and then opened again.

    Premium stickers may only be sent by users with a Premium subscription, and the animated effect should be played by all users, including those without a Premium subscription.

    A premium sticker is identified by the presence of a videoSize of type=f in the sticker's main document.
    -The lottie file of the animated effect may be fetched by using inputDocumentFileLocation with thumb_size=f, as specified here ».

    +The TGS file of the animated effect (different from the TGS file of the sticker itself) may be fetched by using inputDocumentFileLocation with thumb_size=f, as specified here ».

    Note that animated message effects » can also re-use the animated effect of a premium sticker.

    Also, premium animated stickers may be sent with an extra animated message effect », in which case both the effect of the sticker and the additional effect should be played simultaneously.

    Video stickers

    diff --git a/data/web/corefork.telegram.org/constructor/availableEffect.html b/data/web/corefork.telegram.org/constructor/availableEffect.html index 2cddbd9ccb..cf627ad278 100644 --- a/data/web/corefork.telegram.org/constructor/availableEffect.html +++ b/data/web/corefork.telegram.org/constructor/availableEffect.html @@ -4,10 +4,10 @@ availableEffect - + - + @@ -44,6 +44,7 @@

    Represents a message effect ».

    All long IDs except for id are document.ids from the containing messages.availableEffects constructor.

    +

    See here » for more info on how to use following fields.