Skip to main content

Search GiselleBot's commands and docs.

Try /ban, or start with / for commands only.

Press Ctrl K anywhere in the dashboard to open this.

Starboards

A starboard turns your members' reactions into a hall of fame: whenever a message collects enough stars, the bot reposts it into a channel you choose, as a card that keeps its star count up to date. Each server can run several boards, each with its own emoji, channel and threshold.

Everything is configured from the dashboard's Starboards page - there are no slash commands for this module.

What your members see

  • A card, not a copy. The card shows the author's name and avatar, the message text (or the embed's own text for a message that has no text of its own, such as a bot post), the original timestamp, a Jump to message link, how many files the message had, the first image (re-uploaded so it keeps working), and a footer with the board's emoji and the current star count.
  • Stars count on both messages. Reacting to the original and reacting to the card are both counted, and a member who does both counts once. Taking a reaction back can drop a message back under the threshold, and its card is removed.
  • Some reactions never count: the author's own reaction, any reaction added by a bot account, and anyone your server's starrer filters exclude. Bot accounts can never star - the separate bot messages setting only decides whether messages written by bots can be reposted.
  • A message is tracked from its first counted star, and the card appears once it reaches the threshold. Stars that were already on a message before the board existed are not counted - counting starts from the next new reaction on it.
  • The card follows the message. If the original is edited, the card is edited too. If the original is deleted, the card stays with "The original message was deleted." and its star count freezes.
  • If a moderator deletes a card while the message is still popular, it comes back the next time that message gets a star (or the next time the board is reconciled).

Setting up a starboard

Open your server's dashboard, then Starboards, then New Starboard.

  1. Board channel - where the cards are posted. A text channel, an announcement channel, or a thread. A channel can host only one board, and an emoji can belong to only one board.
  2. Emoji - the reaction that counts as a star. On the free plan this is fixed to the star emoji; on Base you can pick any unicode emoji; on Power you can also use one of the server's custom emoji.
  3. Star threshold - how many stars a message needs before it is posted. Between 1 and 50, default 3.
  4. Source channels - every channel, only the ones you list, or every channel except the ones you list. Messages in a thread count with the thread's parent channel.
  5. Bot messages - off by default, so a post written by a bot is not reposted even when members star it. Bot accounts themselves can never star anything on any plan.
  6. Winner recap - optional, Power only (see Winner recaps).

Save the board and it starts working immediately; nothing needs to be re-run or re-enabled.

Note

An NSFW source channel can only feed an NSFW board channel. If the pairing does not hold, the message is skipped (and the skip is logged once per board per hour), so NSFW content cannot be reposted into a channel that minors can read.

Which stars count

The Starrers card on the same page applies to every board on the server:

  • Role filter - every member can star, only members with the roles you pick, or every member except the roles you pick.
  • Ignored members - a list of user IDs whose stars never count.

These filters apply to the people reacting, not to the authors of the messages. A member the bot has not seen yet (they are not in its member cache) is counted for the moment rather than delaying the star; the post is flagged for a later look, but that member's roles are not re-checked automatically - their next star event is what corrects the count.

Editing and deleting a board

  • Threshold, source channels, the bot toggle and the recap settings can be changed at any time; they apply to the next star.
  • Changing the channel deletes the board's existing cards when the process serving the change can still see the old channel; if it cannot, the cards are left in place and only the board's references to them are cleared. New cards appear for messages that are starred again, or are restored by the next reconciliation while they are still above the threshold.
  • Changing the emoji clears that board's collected stars: every card is removed and counting restarts from the next reaction, because stars belong to the emoji they were given with.
  • Deleting the board removes the board and its tracked-message history. Cards already posted stay in the channel, but nothing updates them any more.

Tiers and limits

CapabilityFreeBasePower
Starboards per server135
Emojifixed star onlyany unicode emojiunicode or custom emoji
Threshold1-501-501-50
Source-channel filter, bot-message toggle, starrer filters, deleted-message cardsyesyesyes
Winner recapsnonoyes
Leaderboardnonoyes
CSV exportnonoyes

Note

Downgrading never deletes anything. If a server drops below the plan it was using, boards beyond the new limit - and boards whose emoji the new plan does not allow - are marked Paused in the board list, with an explanation and an upgrade link. Paused boards stop counting, posting and recapping, and they resume exactly as they were when the server upgrades again.

See Premium Perks for the full tier comparison.

Reconciliation

Star counts are updated in real time, but reactions can be missed while the bot is offline. Each board therefore has a Reconcile button that re-reads the message and its card from Discord and repairs the stored count. Repairs are idempotent: running it twice changes nothing the second time.

  • A run can be started once every 10 minutes per board; the button shows "Cooling down" until then. While a run is going, the button shows the run kind and the board row shows its progress.
  • A board whose channel the bot cannot see (the channel was deleted, or the bot lost access) is marked Channel unavailable in the list, and its cards are skipped until that is fixed - the list is the place to notice it.
  • If Discord rate-limits the run, it waits and continues; after repeated rate limits it stops and the board row shows the reason.
  • Refreshing the page during a run does not start, duplicate or interrupt it - the page only watches the run that is already going.
  • Reconciliation also runs by itself for a day's worth of messages after the bot reconnects, so a short outage usually needs no button press at all.

Note

Reconciliation re-checks who reacted, but it does not re-read every starrer's current roles: a member whose roles changed since they reacted is corrected the next time they star something. The same run rebuilds a deleted card as text only - the image comes back the next time the original message is edited.

Winner recaps

On Power, a board can post a periodic winners embed in its own channel, ranking the authors whose tracked messages earned the most stars in the window:

  • Weekly covers the last 7 days; monthly covers the last calendar month.
  • Winners is how many authors to show, from 1 to 25 (default 3).
  • Ranks count total stars across that author's tracked messages, with the number of messages in the same line.
  • A window with no starred messages posts nothing, and the schedule moves on to the next one.
  • Preview recap in the board editor computes the current window without posting anything, so you can see what would go out before enabling it.

Note

On a very busy board, a recap window is ranked from at most the 10,000 most recent tracked messages in it. Beyond that the ranking is approximate rather than exact; weekly windows on normal servers stay well inside the limit.

Leaderboard

Power servers also get a Leaderboard card on the page: the same ranking as a recap, for this week or this month, with no message posted anywhere. It lists the top 10 authors by stars, and each row shows the author's user ID rather than their display name.

Exporting tracked messages

Export CSV downloads every tracked message on the server (or one board, through the API) as a CSV file, newest first, with these columns:

message_id, author_id, author_name, source_channel_id, star_count, first_star_at, last_starred_at, board_emoji, state, content

  • The export is capped at 25,000 rows. On a server that hits the cap, the newest messages are the ones included.
  • content is truncated to 500 characters and newlines are flattened, so each row stays on one line. Attachment links are not exported.
  • The state column tells you whether the message is currently shown on the board (active), was below the threshold or had its card removed (removed), or had its original deleted (tombstoned).
  • Export is a Power feature, and every export is written to the server's audit events.

Permissions Needed

  • View: anyone authorized for the Server Administration module can open the page and read the boards, the leaderboard and the export button's state.
  • Change: server managers (Manage Server or Administrator) can create, edit and delete boards, save the starrer filters and start a reconciliation. The page tells a view-only manager that changes require Manage Server.

Note

Starboards live under the Server Administration permissions. Disabling that module also hides and disables Starboards, and editing the Starboards row on the Command Permissions page edits the Server Administration entry it shares. See Permissions System for how module permissions work.

Good to know

  • No backfill. The bot cannot read a channel's history, so a message that already had stars before the board existed starts counting from its next new reaction.
  • Threads follow their parent. If the parent channel is in scope, so are its threads.
  • One board per channel and per emoji. Two boards on the same emoji would post every message twice, and two boards in one channel would be noise - the editor refuses both.
  • Cards are snapshots. A card shows the message as it was when it was posted or last edited, and the original is always one click away through the jump link.

See also

The full tier comparison is on Premium Perks. For who may configure what, see Permissions System.