Resources | Scripting
Embeds
Master the fundamentals of greed's custom embed scripting.
Slash commands for this page
Use the slash version of each command below. Prefix commands keep working until March 5, 2027. What is changing
,embed create→/embed create,embed save→/embed save
Core Structure
greed uses a specialized token-based system for building embeds. Each component is defined within braces {} and follows a key: value pattern.
The syntax for a standard parameter is:
{- Opens the parameter block.key:- Identifies the property (e.g.,title,description).value- The content or configuration for that property.}- Closes the parameter block.
Block Separators
To organize your script or separate individual embed properties, you can use $v. In greed's engine, this acts as a newline separator, allowing the parser to clearly distinguish between different nodes.
{title: Hello World}$v{description: This is a custom embed!}Available Parameters
Most parameters take a simple text or URL value.
| Key | Description | Example |
|---|---|---|
content | Plain text message outside the embed. | {content: Hello {user}} |
title | The main title of the embed. | {title: Server News} |
description | The body text of the embed. | {description: Join our Discord!} |
color | The sidebar color (Hex or Decimal). | {color: #ccccff} |
url | Makes the title a clickable link. | {url: https://greed.best} |
image | A large image at the bottom. | {image: https://.../img.png} |
thumbnail | A small image in the top right. | {thumbnail: https://.../icon.png} |
timestamp | Adds the current time to the footer. | {timestamp} |
Advanced Parameters
Some parameters support multiple values separated by &&.
Set the name, icon, and an optional link for the author section.
- Syntax:
{author: name && icon && url} - Example:
{author: {user.name} && {user.avatar}}
Add organized rows of data. You can include inline at the end to place fields side-by-side.
- Syntax:
{field: name && value && inline} - Example:
{field: User ID && {user.id} && inline}
You can add up to 25 fields per embed. Each field name has a 256-character limit and each field value has a 1024-character limit.
Configure the small text and icon at the very bottom.
- Syntax:
{footer: text && icon} - Example:
{footer: Sent by {user.name} && {guild.icon}}
Add interactive buttons to your message. You can add up to 5 buttons per message.
- Link buttons:
{button: label && url: https://...} - Custom buttons:
{button: label && custom_id: name && style: style} - Styles:
primary(orblurple),secondary(orgrey/gray),success(orgreen),danger(orred) - Example link button:
{button: Support && url: https://discord.gg/greed} - Example custom button:
{button: Click Me && custom_id: action_name && style: primary}
You can use positional arguments for simplicity: {button: label && https://url} creates a link button.
Building an Embed with Buttons
Run ,embed create (or /embed create) with no script to open the embed builder. It shows a live preview of your embed with buttons underneath, and each button opens a form:
- Edit basic information (color / title / description): title, description, hex color (like
#c0eeff) and a link for the title. - Edit author: author text, icon link and link.
- Edit footer: footer text, icon link, and a checkbox to show the current time.
- Edit images: thumbnail link and image link.
- Edit message text: plain text sent above the embed.
- Add field and Remove last field: fields take a name, a value and an optional Show inline checkbox, up to 25 per embed.
Leave a box empty to remove that part. Variables such as {user.name} and {user.avatar} work in every box, and the preview fills them in for you.
- Save stores the embed in your saved embeds under a name. Tick Overwrite if it exists to replace one you already have.
- Send posts the embed in the current channel. You need Manage Messages.
- Show script gives you the script text, so you can paste it into a welcome message, autoresponder or any other feature that takes a script.
- Cancel closes the builder.
The builder closes itself after 15 minutes without changes.
Importing Discord JSON
Anywhere greed accepts a script, you can paste Discord message JSON instead, such as an export from Discohook or another embed tool. greed accepts:
- a message with
content,embedsand optional link buttons incomponents, - a single embed object,
- a Discohook export or share (
{"messages": [...]}); the first message is used.
Colors can be numbers or hex strings. A timestamp shows the time the message is sent. Only link buttons are kept. In the builder, Import JSON loads JSON into the editor (the first embed, if there are several) and Export JSON gives you the embed as Discord JSON.
If the JSON is broken, has more than 10 embeds, or goes over Discord's limits below, greed tells you what is wrong and nothing is saved.
Mixing Text and Embeds
By default, greed attempts to identify if you are sending a raw text message or an embed script. If you want to ensure the bot parses your script correctly, especially when including variables, begin your message with {embed}$v.
{embed}$v{title: Welcome!}$v{description: Glad you joined us, {user.mention}!}Tips & Tricks
- New Lines: You can create real new lines in your
{description}by simply pressingEnterwithin the script. - Multiple Embeds: Want to send more than one embed in a single message? Just start a new
{embed}block (up to 10 per message). - Zero-Width Spaces: If you need an empty field or title, you can use a zero-width space character.
Discord Embed Limits
Be aware of these hard Discord limits when building embeds:
| Element | Limit |
|---|---|
| Embeds per message | 10 |
| Title length | 256 characters |
| Description length | 4096 characters |
| Fields per embed | 25 |
| Field name length | 256 characters |
| Field value length | 1024 characters |
| Footer text length | 2048 characters |
| Author name length | 256 characters |
| Total content across all fields | 6000 characters |
| Buttons per message | 5 |
If you exceed these limits, your embed script will fail to render. The parser will report the specific limit that was exceeded.
Mentions in Embeds
When your embed contains role or user mentions (e.g., {guild.owner_id} rendered as a mention), they will only ping if your server has the appropriate allowed mentions configured for the bot's message. By default, @everyone and role pings are disabled in Discord for security reasons.
If mentions in your scripts aren't pinging users, check your server's permissions for the bot and any custom role mention settings configured through greed's moderation features.
Parsing Rules
- Keys are case-insensitive:
{Title: ...}and{title: ...}work the same way. - Whitespace after colon is optional:
{title:text}and{title: text}both work. - Separators: Use
$vto explicitly separate nodes (it becomes a newline), or{node1}{node2}to chain without space. - Spaces between nodes:
} {is automatically converted to}{so spacing doesn't break parsing. - Unknown keys are ignored: If you use a key like
{unknown: text}, it simply won't appear in the output. - Unresolved variables: If a variable like
{undefined.value}doesn't exist, it renders as the literal textundefined.value.
If you have an unclosed brace (e.g., {title: hello without a closing }), the parser will skip it and continue with the rest of your text.
Saved Embeds
Save a script once and reuse it anywhere a script is accepted with {embed:name}. You can save one with ,embed save (name) (script) or from the dashboard: open your User settings, go to Your embeds and choose New embed. Each saved embed has an Edit button for the script and a shortcut that opens it in the embed builder, where Save to name writes your changes back.
Both places apply the same rules:
- Names are 1 to 32 characters of lowercase letters, numbers,
-and_, and start with a letter or number. Names are not case-sensitive, soWelcomeandwelcomeare the same embed. - Scripts must be valid. If greed can repair a broken script, it saves the repaired version and tells you what changed.
- There is no limit on how many embeds you can save.
- On Discord,
,embed savewith a name you already use replaces that embed. On the dashboard, New embed refuses a name you already use; edit the existing one instead.
To share a saved embed with everyone, see Publishing.