Embed Messages
Design a rich message once and post it anywhere. Several embeds, images, buttons and a dropdown, published from the dashboard, editable afterwards, and schedulable.
Embed Messages is the studio for anything you want to say: rules summaries, announcements, partner posts, self-service menus. You build it on the dashboard, publish it to a channel, and edit it later without deleting and reposting.
Add a message above everything… (optional)
Welcome to Nebula Collective
Start in #rules, then pick your roles below. Events are announced every Friday.
Need help?
Open a ticket in #support
Events
Fridays at 8 PM
Read the rules
Pick rolesLive preview of the published message. The pinned text and every element post as their own messages, so the stack appears under one bot header in Discord. Click a button or dropdown option to see its configured response.
Elements
A message is an optional plain-text message on top, which always stays first, plus an ordered list of up to 10 elements, added with Add element. A server holds up to 20 messages, each started with New message.
| Element | What it publishes as |
|---|---|
| Embed | A bordered card with the full slot set, optionally a fresh random color every time it is sent |
| Text message | A plain message |
| Image | An uploaded image, edge to edge |
| Separator | A divider line or a gap. Components V2 only |
- Drag to reorder. Duplicate and delete appear to the right of an element when you hover it; the pencil and the color button sit in its left gutter.
- With more than one embed, the color popover asks whether a pick applies to This embed or to All of them, for a stack that should read as one thing.
- An embed holds up to 6,000 characters of text in all, Discord's own limit. Publish names the element that is over.
Buttons and a dropdown
- Up to five buttons: a link button opens a URL, a response button replies privately to whoever clicked with a message you designed.
- One dropdown with up to ten options, each carrying its own private response.
- Placeholders: the message takes
{server},{channel},{member_count}and{bot_avatar}, and a response adds the member who clicked:{user},{username},{display_name}and{user_id}. - The preview is interactive. Click a button or an option and the actual configured response is rendered.
- Buttons keep working indefinitely, including across restarts.
Publishing
Pick a channel
Under Channel. Anywhere Arclo can send messages and embed links.
Publish
Arclo posts the stack and remembers what it posted. Save draft keeps your changes without touching what is live.
Edit and publish again
Only what actually changed is edited in place. Adding, removing or reordering elements changes the shape of the stack, so it is reposted.
Traditional Embed or Components V2
Traditional Embed publishes a stack of messages, one per element, with the buttons and the dropdown on a last message of their own at the bottom. Components V2 publishes the whole thing as one message with containers and native separators. Pick per message, with the switch at the top of the Message section.
Discord's Components V2 caps
40 components and 4,000 characters of text per message. Arclo blocks a publish that would exceed them rather than letting Discord reject it.
Scheduling
Switch on Send at a specific time under Schedule, pick the date, time and time zone, and Publish becomes Schedule message: the announcement is written now and posted at the hour you picked. Arclo checks every 30 seconds, so it may post a moment late. A queued send shows above the builder with Cancel scheduled send, and a send that failed says why in the same place.
A schedule sends once. For a message that repeats (every few hours, daily, weekly, or rotating through several versions), use Automations with the On a schedule trigger.
Commands
/embed-create [style] [channel] [color] [name]Manage MessagesWrites an embed (or a plain message) in a popup and posts it. Saved to Embed Messages, so it can be opened in the studio afterwards.
/embed-edit <message>Manage MessagesRe-opens a message made with /embed-create and rewrites it in place. Messages built in the studio are edited there.
A message written in Discord opens in the studio
/embed-create writes an ordinary configuration, so anything typed into the popup can be reopened, restyled and given buttons later. /embed-edit only accepts the simple shape it can honestly edit: one embed (title, description, footer and image) or one text message, with no buttons, dropdown or message above it. Anything richer is sent to the studio rather than silently flattened.
The Logging card under your messages records them being created, updated, published, scheduled and deleted, scheduled sends that went out or failed, and both commands.
Still stuck? Ask in the support server: somebody there has almost certainly configured this before.