Skip to main content

Clock & Member Count Channels

This module manages two kinds of read-only voice channels that rename themselves on a schedule: clock channels, which show the current time, and a member count channel, which shows the server's live member count.

Creating, editing, and deleting these channels is done entirely from the dashboard's Clock & Member Count Channels page - there is no chat command for any of it.

Creating a channel

Clock channels - click Add Clock Channel, then set:

  • Time Zone - a real IANA time zone name (e.g. America/New_York), or a bare UTC/GMT reference
  • Name Template (optional) - must include %date% or %clock%. Leave empty to use the default template
  • 12-Hour Format toggle

Members can't connect to the created channel. The channel's name updates roughly every 15-60 minutes.

Member count channel - click Add Member Count Channel. Only one member-count channel can be active per server; it updates about once an hour.

Editing and deleting

Once a channel exists, the dashboard lists it under Clock Channels or Member Count Channel, with an Edit link to change its settings without needing to delete and recreate it, and a Delete button to remove it:

Clock channels

  • Time zone
  • Name template - must include %date% or %clock%. Leave empty to reset to the default.
  • 12-hour format toggle
  • UTC offset

Member count channel

  • Name template - must include %count%. Leave empty to reset to the default.

Permissions Needed (Clock & Member Count Channels)

  • User: Manage Channels, Manage Server
  • Bot: Manage Channels, Connect

URL Shortener

The same Tools page also shortens a long URL, using the proprietary gisl.eu shortening service: paste the URL into the Long URL field and click Shorten to get a short link, with a Copy button next to the result. This has no permission requirement beyond access to the page itself.

Shortened URLs never expire unless deleted by whoever created them (deletion isn't available yet). The original URL is stored as an encrypted string, so it isn't exposed if the redirection database is ever breached.