Syntax

$addFile[url;(spoiler)]

Parameters

Parameter	Required	Default	Description
url	Yes	—	URL of the file. The engine does not check or download it, it is passed as is to the component.
spoiler	No	no	yes/true to mark the file as a spoiler, no/false otherwise. An empty value means no; any other value is an error (Expected yes or no, got "...").

Return value

None (empty string). The file component is added to the components of the pending message.

Components V2 message

A file is a rich (Components V2) component. When the message contains one, it is sent as a Components V2 message, which cannot carry text content or embeds: the text of the message and the embeds are not sent. Put any text in a $addTextDisplay[] component instead.

Examples

Attaching a file

$addTextDisplay[Here is the requested chart]
$addFile[https://cdn.example.com/chart.png]

Spoiler file

$addTextDisplay[Warning: ending spoiler!]
$addFile[https://cdn.example.com/spoiler_endgame.png;yes]

Multiple files

$addTextDisplay[Configuration files]
$addFile[https://files.example.com/logs.txt]
$addFile[https://files.example.com/config.json]

Notes

• Multiple $addFile[] calls can be used in the same message.
• Do not confuse this with $addModalFileUpload[], which is for interactive modals.
• $addFile[] ends the section opened by a previous $addSection: following components are not added to it.
• $addFile[] has no container name. In a script that uses names, the file attaches to the message itself; in a script that names nothing, it goes inside the latest $addContainer.
• A Components V2 message holds at most 40 components (the file counts as one).