Overview
Keep rules, links, or welcome notes at the bottom of a channel. The bot removes the old sticky and reposts it whenever a new message arrives.
What Sticky Messages can do
- Always visible - the sticky is reposted at the bottom of the channel when new messages push it up.
- Three formats - plain text, a rich embed, or a Rune script.
- Per-sticky controls - set the repost delay, mention policy, channel, and enabled state independently.
- Dashboard management - create and edit stickies from the Stickies page without using commands.
Permission required
Manage Guild
Creating a sticky
Open the editor in the current channel:
f!sticky createOr choose the target channel when you start:
f!sticky create #rulesThe editor asks you to choose a type. React with 1 for a plain message, 2 for an embed, or 3 for a Rune script. Type stop at any time to cancel an open editor.
Run f!sticky with no subcommand to see the command overview.
Sticky types
| Type | Best for |
|---|---|
| Message | Rules, links, welcome text, or a short announcement. |
| Embed | A formatted card with a title, description, color, image, footer, and author. |
| Rune script | Dynamic content built with values, conditions, loops, and the Rune API. |
Message and embed fields support placeholders: {community}, {members}, {user}, {username}, {channel}, and {count}.
Mentions and delays
Sticky messages do not ping anyone by default. Use f!sticky mentions <number> none to keep it that way, or allow users, roles, or everyone.
The repost delay controls how long the bot waits after the triggering message before it removes the old sticky and posts a fresh one. Delays can be between 1 and 60 seconds.
Limits
- Up to 10 stickies per community.
- Only one sticky per channel.
- Delays can be between 1 and 60 seconds.
- The bot needs permission to send messages and manage its old sticky messages in the channel.
Dashboard
The Stickies page in the dashboard supports creating and managing stickies without commands. It is available from your community's dashboard sidebar.