Starboard
Feature popular messages after they receive enough star reactions.
How it works
Starboard watches eligible messages for star reactions and reposts qualifying content to the configured showcase channel.
Before you start
- Create a starboard destination channel.
- Allow Airwavy to read message history in source channels and send embeds or attachments in the destination.
Configure it
- Open Starboard in the dashboard.
- Choose the destination, reaction threshold, and any available channel restrictions.
- Save and add stars to a test message until it crosses the threshold.
Threshold and eligibility
- Choose a reaction threshold from 1 through 100.
- Free servers use the star emoji and allow self-stars with the standard presentation.
- Premium can choose a custom emoji, allow or block self-stars, and apply source-channel and member-role allowlists or blocklists.
- Airwavy reads the current eligible reaction total instead of treating every reaction event as a separate permanent vote.
Entry lifecycle
- Crossing the threshold creates a starboard entry; later reactions update its count and presentation.
- Falling below the threshold removes the corresponding starboard entry.
- Premium presentation can use role color and choose how avatar and message content appear.
- Deleting or restricting the original message can prevent Airwavy from keeping the showcase entry current.
Expected result
- A qualifying message is mirrored to the starboard channel.
- Further reaction changes update or remove the starboard entry according to configured behavior.
Common errors
A message reaches the threshold but is not posted
Check source-channel eligibility and Read Message History, then confirm the destination allows Send Messages, Embed Links, and Attach Files.
Saved changes do not take effect
Reload the feature page and confirm the saved values. Then verify that the selected Discord channel or role still exists and that Airwavy can access it.
Discord reports missing permissions
Check the permission on both the server role and the target channel. Channel overwrites and role hierarchy can deny an action even when the server-level permission is present.