Skip to content

Sticky messages ​

Keep an important message at the bottom of a busy channel. SnowstormBot reposts a sticky message after a set number of new messages, so it never scrolls out of sight, perfect for channel rules, a current event, or a "read this before posting" note. Each channel can have one sticky.

The Sticky messages feature is off by default and depends on your plan. Turn it on from the Features page, then open Sticky messages in the sidebar.

Adding a sticky ​

  1. Open Sticky messages in the sidebar and click New sticky.
  2. Pick the channel it should stay in.
  3. Type the message.
  4. Set Repost after N new messages, how many messages can go by before SnowstormBot reposts the sticky (so it returns to the bottom).
  5. Make sure Enabled is on and click Save.

When you edit a sticky that already exists, the Save button stays greyed out until you actually change something, so you can always tell whether there is anything left to save. In the list of stickies, tags show the name of the role, member or channel (like @Tom) instead of the code Discord uses behind the scenes.

SnowstormBot posts it straight away, then reposts it as the channel stays active. When it reposts, it deletes the previous copy so the sticky never piles up.

Reposts happen about 5 seconds after the message that triggers them. If more people chat during those 5 seconds, they all share that one repost, so a busy channel doesn't make the sticky jump around after every single message (and doesn't run into Discord's limits). Whether it's 1 message or 100, the sticky ends up back at the bottom a few seconds later.

One sticky per channel

A channel can have a single sticky at a time. To change it, edit the existing one. How many stickies you can have across the whole server depends on your plan.

Managing stickies from Discord ​

Server admins (anyone with the Manage Server or Administrator permission, which includes the server owner) can manage the current channel's sticky straight from Discord, without opening the dashboard. If you pick manager roles (below), people with any of those roles can do it too:

CommandWhat it does
/sticky set <text>Set or replace this channel's sticky message.
/sticky enableTurn this channel's sticky back on.
/sticky disableTurn this channel's sticky off.

All three act on the channel they're run in.

Manager roles ​

On the Sticky messages page you can pick one or more manager roles. Members with any of those roles can use the /sticky commands, on top of your server admins. Click Save roles after picking them.

Leave it empty to keep the commands admin only

If you don't pick any manager roles (or you only pick @everyone), only server admins can use the /sticky commands. Picking @everyone does not open them up to everybody, so nobody can accidentally let just anyone change a sticky.

Good to know ​

  • Stickies never ping anyone: any role or user mentions in the text are shown but won't notify.
  • Disabling or deleting a sticky stops future reposts; the last copy already in the channel stays until you delete it yourself.

Plan limits ​

How many stickies you can have across the server depends on your plan. If your plan includes zero, the feature shows Requires plan upgrade on the Features page and can't be turned on. See Plans & limits.

Tagging roles, members and channels ​

In the Sticky message box you can type @ to tag a role or member, or # to link a channel, the same way as on Send a message. Each role and member tag gets a Ping switch underneath. Ping means Discord sends those people a notification, and Tag only shows the tag without notifying anyone. @everyone and @here start on Tag only, so nobody pings the whole server by accident.

If a member leaves, or a role or channel is deleted, the tag keeps showing its old name when you edit the message, but you can no longer pick it again. In Discord it then shows as a broken tag.

A pinged tag pings on every repost

The sticky is posted again every time the channel gets busy. A tag set to Ping notifies people again on every one of those reposts, so keep tags on Tag only unless that is really what you want.