Containers & components

Embeds are fine, but they’re rigid. Containers are Discord’s newer layout system: a bordered block with a coloured accent bar that you fill with text, images, thumbnails and buttons in whatever order you like. Anywhere you can write an embed script, you can write a container instead.

{box: #5cacec}
{box.header: Server Rules}
{box.text: Be decent to each other. That's mostly it.}
{box.separator}
{box.text: Breaking them gets you a warn, then a mute, then a ban.}
{box.button: label: "Full rules" url: "https://example.com"}
{box.button: label: "Got it" style: "success" message: "Thanks for reading 💙"}

Rather build it visually? The message builder previews containers exactly like Discord, shows you the script as you go, and can send the message straight to a channel.

Opening a container

Node	Aliases	Notes
`{container}`	`box`, `cntr`, `ctr`	Opens a container
`{container: #hex}`	—	Opens one with an accent colour
`{container: #hex spoiler}`	—	The whole container is blurred until clicked
`{container: dominant}`	—	Accent taken from the first image inside
`{container: dominant.image}`	—	Accent taken from a specific image — see below
`{layout}`	—	Components that sit loose in the message, with no box around them

Everything after it that starts with box. (or container., etc.) belongs to that container. Open a second {box} to start a new one. {layout} works the same way — {layout.text: ...}, {layout.media: ...} and so on — for text, galleries or button rows that sit directly in the message, above or below your containers.

What goes inside

Text and headers

Node	Aliases
`{box.header: ...}`	`heading`, `h`, `title` — `h1`, `h2`, `h3` pick the size
`{box.text: ...}`	`description`, `desc`, `txt`, `body`, `content`

{box.header: Welcome to {guild.name}}
{box.text: {user.mention}, you're member **{guild.members}**.}

Both support full Discord markdown, including # headings, -# subtext, lists and > quotes. A header without its own # renders at ## size.

Separators

{box.separator}
{box.separator: large}
{box.separator: large invisible}

Aliases: sep, divider, hr. large (or lg / big) adds more breathing room. invisible (or hidden) keeps the spacing but drops the line — {box.spacer} is shorthand for that.

Images and galleries

{box.media: https://example.com/one.png}
{box.media: https://example.com/one.png | https://example.com/two.png}
{box.media: spoiler:https://example.com/secret.png | https://example.com/cat.png A sleepy cat}

Aliases: image, img, gallery, photo, pic. Up to 10 items separated by |, laid out in Discord’s gallery grid. Put spoiler: in front of a URL to blur it, and anything after the URL becomes its alt text.Only real https:// links are sent — an image that fails to resolve (say, a variable that came out empty) is left out rather than breaking the whole message.

Sections: text with a thumbnail or button

A section is up to three blocks of text with a thumbnail — or a button — beside them.

{box.section: text: "Level 12 — 4,200 xp" thumbnail: "{user.avatar}"}
{box.section: text: "**Rules**" text2: "Read them before posting." button: "Open" button_url: "https://example.com"}

Part	Keys
Text	`text`, `text2`, `text3` (the first also accepts `label`, `description`, `content`, `body`)
Thumbnail	`thumbnail` (or `thumb`, `image`, `icon`), plus optional `alt` and `spoiler: true`
Button	`button` (the label), `button_url`, `button_style`, `button_emoji`, `button_message`, `button_disabled`

Aliases: sec. {box.thumbnail: <url>} next to a {box.text} pairs the two into a section as well.Quotes inside a quoted value are written as \".

Buttons and rows

Buttons written one after another share a row, the way Discord lays them out — up to 5 per row, after which a new row starts. Anything else between them, or {box.row}, ends the row.

{box.button: label: "Website" url: "https://example.com"}
{box.button: label: "Say hi" style: "primary" emoji: "👋" message: "Hey, welcome!"}
{box.row}
{box.button: label: "Rules" style: "secondary" message: "Head to #rules"}

Key	Notes
`label`	Up to 80 characters
`url`	Makes it a link button. `<#channel>` becomes a jump link
`style`	`primary`, `secondary`, `success`, `danger` (also `blurple`, `grey`, `green`, `red`)
`emoji`	A unicode emoji or a custom one like `<:name:id>`
`message`	A private reply to whoever clicks. Variables are filled in when the message is sent, so `{user.mention}` in a welcome message is the new member
`disabled`	`true` greys it out

Button replies keep working forever — they survive restarts and never time out. A non-link button with no message just acknowledges the click.Top-level {button: ...} nodes work the same way, and {row} starts a new row for them too.

Files

{box.file: attachment://report.pdf}
{box.file: attachment://spoilers.txt spoiler}

Shows a file that was uploaded with the message. Discord only accepts uploaded files here, so this is mainly for the message builder, which attaches the files for you.

Accent colour and spoilers

Set on the opening node, or separately afterwards:

{box}
{box.color: #ff5c8a}
{box.spoiler}

{box.dominant}

{box.dominant} pulls the colour from the first Discord-hosted image in the container — section thumbnails first, then media gallery images.A container has no author or footer, so there are only two slots worth naming:

{box.color: dominant.image}

{box.color: dominant.thumbnail}

{box.dominant: image}

Same rules as embeds: the separator can be a dot, colon or space, and a named slot is preferred rather than required.

Container vs embed

Neither is better — they’re for different shapes of message.

	Embed	Container
Layout	Fixed: title, description, fields, image	Free — items in the order you write them
Images	One large, one thumbnail	Galleries of up to 10, thumbnails beside text
Buttons	Below the message	Anywhere, in rows of up to 5, or beside text
Accent	Left colour bar	Left colour bar
Best for	Structured info, field grids	Announcements, panels, anything with mixed media

Discord doesn’t let a Components V2 message carry plain content or embeds, so as soon as a script uses a container Mira adapts the rest for you: {content} becomes loose text in the same spot, top-level buttons become a loose button row, and each embed is turned into a container that reads the same way. Stickers can’t be sent alongside containers.

A worked example

A welcome message that actually looks designed:

!welcome add #general {content: {user.mention}}
{box: dominant}
{box.section: text: "## Welcome to {guild.name}" text2: "{user.name} — you're our **{guild.members|comma}th** member." thumbnail: "{user.avatar}"}
{box.separator}
{box.text: -# account created <t:{user.created_at}:R>}
{box.button: label: "Read the rules" style: "secondary" message: "Head over to #rules — it takes 30 seconds."}
{box.button: label: "Say hi" style: "primary" emoji: "👋" message: "Welcome in, {user.mention}!"}

Build it with !embed first so you can see it, tweak it, and only paste it into !welcome add once you’re happy. !copyembed on the result gives you the script back if you lose it.

Limits

Discord enforces these, not the bot:

40 components total per message (every text, button, thumbnail and container counts)
5 buttons per row
4000 characters across all text in the message
10 items per media gallery, 3 texts per section

Going over any of these means the message won’t send. If a script silently fails to appear, this is usually why — trim it down and try again. The message builder counts all of these for you as you go.

​Opening a container

​What goes inside

​Container vs embed

​A worked example

​Limits

Opening a container

What goes inside

Container vs embed

A worked example

Limits