1. Scripting Structure
Understanding the syntax is the first step to building perfect embeds. Every parameter in a @curse script is a key-value pair wrapped in brackets.{: Every parameter begins with an opening curly bracket.:: This separates the parameter name (the “key”) from the actual content (the “value”).$v: Use this symbol to separate different parameters within the same message.}: Every parameter must be closed with a curly bracket.
2. Core Parameters
These are the foundational building blocks used to construct the main body of your embed.Field
Field
Organize your information into structured, easy-to-read sections rather than a single block of text.
- name
Required: The bolded title or header of the field. - value
Required: The main text content or data within the field. - inline
Optional: Add this keyword at the very end to place multiple fields side-by-side horizontally.
3. Frequently Asked Questions
3. 1. How do I add a new line to my description?
To create a line break within your script, simply press SHIFT + ENTER. The script will recognize the visual gap as a new line in the final embed.3. 2. Why isn’t my embed code working for some commands?
Some @curse commands support both plain text and embeds. To tell the bot you are using a script, you must start your code with the{embed}$v prefix.
3. 3. Can I use multiple fields in a single embed?
Yes, you can use multiple{field: ...} tags within one script. To organize them side-by-side, ensure you include the inline keyword at the end of each field argument.
3. 4. What happens if I don’t provide an icon for the author or footer?
Theicon argument for both the author and footer objects is optional. If left blank, the embed will simply display the text or name without a small image next to it.