Starts with a reaction

Starboard

A message that collects 5 ⭐ reactions is reposted in #starboard with its author and a link back, so the funniest post of the week is still easy to find on Friday.

Illustration. The real interface may look different.

How it works

  1. The bot counts the ⭐ reactions on a message.

  2. When the count reaches your threshold, the message is posted in #starboard, exactly once.

  3. A button under the post jumps to the original message.

How to make a starboard on Discord

A starboard is one flow and two stored values per message: a star count and a marker that it has been posted.

Describe it to your AI assistant

The best messages on our server disappear in the scroll. Build a starboard flow: when a message gets its 5th ⭐ reaction, post it once in #starboard with the star count, the author's mention, the first 300 characters of the text and a "Jump to message" link button. More stars after that should not post it again. Ignore reactions from bots.

Copy it and swap in your own channel and role names. Your assistant has a tested version of this example to start from.

Build it in the editor

One flow with a "Reaction added" trigger, set to the ⭐ emoji, and seven steps. The threshold and the channel are values inside the flow.

The flow, step by stepStep names are the ones the editor shows.

Flow 1A star is added

Trigger: Reaction addedwith "Specific Emoji" set to ⭐ and "Ignore Bots" on.

  1. Increase a stored numberAdds 1 to the star count of that message.
  2. Greater or equalCompares the count with your threshold. Below it, the flow stops.
  3. Set stored value if (atomic)Claims the message. Only the first run to reach the threshold gets through, so it is posted once.
  4. Build message linkBuilds the link back to the original.
  5. Truncate textCuts the text to 300 characters.
  6. Create messageBuilds the post: star count, author, the quote and the "Jump to message" link button.
  7. Send messagePosts it in your starboard channel.

Test it, change it

What it stores

  • Star countBy custom keyOne number per message, filed under the message ID.
  • StarredBy custom keyA marker per message once it is on the starboard.

How to test it

  1. Open a flow in the editor and click "Test run". Choose the member under "Run as" and click "Run test". The run uses your real server data but sends, changes and deletes nothing, and shows what each step would have done.
  2. A new flow is a "Draft" and does not run in Discord. Switch it on and click "Save & activate".
  3. Set the threshold to 1 for the test, star a message in Discord and star it again with a second account. One post should appear in the starboard channel.
  4. Each real run then shows up under "Executions", with the reason if it failed or was skipped.

What to change

Threshold
The number in the "Greater or equal" step. Our tested flow uses 3, this page uses 5.
Channel
Picked in the "Send message" step.
Emoji
"Specific Emoji" in the trigger. Any emoji works, a custom one too.
Source channels
"Channels" in the trigger limits where stars count. Leave it empty for every channel.

Watch out for

  • The flow counts stars as they are added. A member who removes a star and adds it again counts twice, and authors can star their own message.
  • The post quotes text. A message that is only a picture arrives as an empty quote with the link.
  • The count on the post is the count at the moment it was posted. Later stars do not update it.

Questions about this build

Can authors star their own messages?

In this build, yes. To stop it, compare the member who reacted with the author of the message as the first step and end the flow when they match.

Can the starboard show the image of a message?

This build quotes the text and links back to the original. The picture is one click away there. The community module that comes with your bot has a starboard too.

How many stars should a starboard need?

Start at 3 on a small server and raise it when the channel fills up too fast. On Lantern Lounge, the example server on this page, it takes 5.

Chceš svůj server do bety?

V3 je velký systém a pořád se rychle vyvíjí, proto servery přijímáme postupně, ne všechny najednou. Každou přihlášku čte člověk a ozveme se ti do pár dní.

Servery, které už v betě jsou, rozhodují o velké části toho, co budeme stavět dál. To, co vytvoříš, je tvoje: flows a moduly zůstanou i po skončení bety.