Keep a living scoreboard inside the channels where activity happens.

A live leaderboard begins with an enabled state and a destination channel. Atom needs a stable place to publish and update the embed; moving or deleting the message outside the dashboard can interrupt the board’s lifecycle. Use a channel where the competition is relevant and where the bot can send, embed, and update messages.

Track one activity mode—text, voice, or reactions—per configured board. Separate boards are easier to explain than a blended score whose units cannot be understood. A weekly message leaderboard and a monthly voice leaderboard can coexist while preserving the meaning of each count.

The refresh strategy supports a first start, a repeat interval, and time units from weeks down to seconds where the configuration permits them. Count-based scheduling can also use target and current counts. Choose a cadence that reflects the activity being measured; refreshing a slow monthly competition every minute creates noise without adding useful information.

Minimum count removes members who have not crossed a meaningful participation threshold, while display count limits the length of the public standings. Together they keep a large server from producing an unreadable embed and prevent a single token action from looking like an earned placement.

Normal and reward rows can use supported variables for rank, member mention, count, label, reward, and line breaks. The surrounding embed can carry a title, description, footer, footer icon, image, and color. Customize these fields to explain the period and unit; do not remove the information members need to understand why they appear where they do.

A reward row can grant bounded XP, levels, add roles, or remove roles at a chosen rank. Verify role hierarchy and decide how ties or repeated periods should be handled before enabling continuous repetition. A scoreboard is visible motivation; its rewards are still privileged server operations.

Publish the activity measured, start and end times, exclusions, reward logic, and how suspected farming will be reviewed. Pair the board with Blacklist, Cooldown, and Experience settings so members cannot win by exploiting a channel or pattern that the progression system was not designed to reward.

Start with one board and watch an entire period before adding more. The editor makes multiple leaderboards possible, but community attention is finite. A small number of understandable competitions creates healthier behavior than a wall of constantly changing standings.