In brief: An achievement recognizes a defined accomplishment. A reward is what follows it. In Atom, select a reward type first, configure its amount or roles, and add other distinct types only when they serve the milestone. Rewards can add or remove XP, levels, and roles; the same reward type cannot be selected twice.
Achievements, XP, levels, rewards, and currency are different tools
Achievements preserve a named milestone. XP measures ongoing contribution. Levels summarize progress against a curve. Rewards change something after a threshold: they can add or remove XP, levels, or roles. Currency is a spendable economy and should not be implied by a badge system unless you actually operate one.
| Tool | Best job | Common mistake |
|---|---|---|
| Achievement | Remember a specific accomplishment | Using it as another anonymous XP counter. |
| XP and levels | Show continuous progress | Treating every level as a unique story. |
| Role reward | Signal status or enable appropriate access | Granting permissions without hierarchy testing. |
| Perk | Make a milestone feel useful | Creating permanent support burden for trivial activity. |
Choose rewards by the behavior they reinforce
Recognition-only works for most early cards. A cosmetic role can fit a seasonal event. Access to an opt-in showcase channel can fit a demonstrated contribution. XP or level awards can accelerate a member after a special event, while removal rewards can implement intentional tradeoffs or transitions. Neither should make an achievement an easy way to distort the progression system.
In Atom, use the reward menu to select a type before its amount or role input appears. Add more types when needed; each of Add XP, Remove XP, Add levels, Remove levels, Add roles, and Remove roles can appear once. Green verbs mark additions and red verbs mark removals. Keep role permissions least-privilege and remember that a Discord bot can only manage roles below its highest role.
Discord permission hierarchy reference · configure Atom reward roles
A reward ladder that stays credible
Use early milestones for acknowledgement, medium milestones for cosmetic identity, and rare milestones for durable community status. Avoid a large prize for a message target: it creates an incentive to manufacture activity. If a role unlocks a sensitive channel or permission, make the achievement only one part of the qualification process.
Review rewards after real use. A role nobody recognizes is not a reward; an access role that creates moderation work needs a stricter standard.
test the whole unlock flow · build a balanced achievement system · configure achievement outcomes in Atom
Build a collection with intent