Configuration

How refreshing works#

Every glued message has two thresholds, and whichever fires first wins:

• Message count (messagecount, default 5) — as soon as this many new messages arrive, the glue immediately refreshes to the bottom.
• Time (refreshtime, default 15 seconds) — if fewer messages than that arrive, the glue refreshes this many seconds after the first new message since the last refresh.

So with defaults, a burst of chat refreshes the glue almost instantly, while a single stray message refreshes it within 15 seconds. If nothing is posted, no refresh happens at all — and if the glued message is already the last message in the channel, the bot skips the refresh entirely rather than bumping it redundantly.

Tuning with /refreshconfig#

View the current settings for a channel:

/refreshconfig

Or change one or both thresholds:

/refreshconfig messagecount:10 refreshtime:60

• messagecount accepts 5–50 messages.
• refreshtime accepts 15–3600 seconds (15 s to 1 hour).
• The optional channel argument lets you configure another glued channel without leaving the one you're in.

After you change settings, the very next message in the channel triggers an immediate refresh so you can confirm the glue is alive. Full option details are in the command reference.

Per-channel settings#

• Settings belong to the channel's glued message, not the server — every glued channel can have its own thresholds.
• Each channel holds exactly one glued message; gluing again replaces it (with default thresholds, so re-tune after re-gluing).
• Editing with /editglue keeps the channel's thresholds.
• Threads count as their own channels, with their own glue and settings.

Recommended settings#

• Busy general chat — raise both (e.g. messagecount:15, refreshtime:60) so the glue isn't refreshing constantly.
• Announcements / rules channels — the defaults are fine; traffic is low, so the glue rarely moves.
• Event or support channels — keep messagecount low so the key message snaps back quickly during activity spikes.