Plugins

Embed Messages

Standalone embeds authored in the dashboard and kept in sync with Discord — edit here, updated there.

Design an embed in the builder, pick a channel, and Cloudy posts it. Edit it later and the same Discord message is updated in place — no delete-and-repost, no broken links, no lost pins.

This is the right tool for rules, FAQs, role explanations and anything else that has to look good and change occasionally.

LicenseFree — no premium needed
Limit100 embed messages per server

Fields

Name

1–60 characters · required

An internal label so you can find the message in the list — and the fallback embed title if you do not set one in the builder.

Channel

Text or announcement channel · required · fixed after posting

Where the bot posts the message.

The channel cannot be changed after the message exists. A Discord message cannot move between channels — to relocate it, delete the entry and create a new one.

Text above the embed

Up to 2000 characters · optional

Plain message text rendered above the embed card. The usual use is a role ping (@Announcements) so the embed itself stays clean.

The embed

The card itself, designed with the full embed builder: title, description, colour, author, images, footer, timestamp and up to 25 fields.

Lifecycle

Create

Saving shows a posting… badge; the bot posts the message to the channel within about 30 seconds.

Edit

Saving shows an updating… badge and the bot edits the existing Discord message in place — same message, same id, same position in the channel, same pins and links. If the message is temporarily unreachable, the bot retries a few times before giving up until the next edit.

Delete

Deleting removes the Discord message and the entry. This is not undoable and the message cannot be recovered.

Why not just post it by hand

Three reasons:

  • Editable forever. A message posted by a human can only be edited by that human. An embed message can be edited by anyone with dashboard access, from anywhere.
  • Consistent design. The builder produces the same structure every time and enforces Discord's limits before you hit send.
  • Survives staff turnover. Nobody has to find whoever posted the rules three years ago.

Behaviour notes

  • Placeholders like {user} do not make sense here: the message is not sent in response to anyone, so there is nobody to substitute. Server placeholders — {server} and {server.memberCount} — are filled in inside the embed, but not in the text above it.
  • Cloudy needs Send Messages, Embed Links and, for edits, Read Message History in the channel.
  • If someone deletes the Discord message by hand, the bot notices and removes the dashboard entry as well. Create it again from the dashboard.
  • While the plugin is switched off, nothing is posted or updated; deletions still go through.
  • Resetting the server removes every embed message, including the Discord messages.
  • Clearing the text above the embed in the dashboard clears it in Discord too.
  • A message deleted in Discord (or whose channel was deleted) is removed from the list. If Cloudy cannot post or edit (missing access), it retries with a growing pause instead of every 30 seconds.

Related

Custom Games

Match queue and stats panels for Valorant and CS2 — staff roles, entry requirements, point values and match logging.

Automations

When something happens, check conditions, run actions — the full list of 12 triggers, 13 conditions and 19 actions.