In brief: A hidden achievement conceals some or all of its requirement until the member earns it. Done well, it creates a story worth sharing. Done poorly, it feels like an arbitrary counter the community had no chance to understand.
Hide the surprise, not the standards
A hidden card is fair when members can discover its path through a clue, an event rule, community lore, or a reasonable experiment. It is unfair when a private counter rewards a behavior nobody could know mattered. The excitement should come from recognition, not from a gotcha.
Atom supports hidden manager-assigned achievements. That makes it a good fit for subjective or story-based recognition where staff can verify the moment, rather than trying to derive it from an opaque automation rule.
Prevent abuse and frustration
Do not make members post repeatedly, stay awake, or join empty voice channels to hunt a secret. Scope activity triggers, preserve the same eligibility rules you use elsewhere, and rate-limit announcements. For staff-assigned cards, write a private rubric so awards are consistent without publishing every surprise.
After an event, reveal enough about the hidden card that the community can appreciate the story. A collection is part of the community archive; members should eventually understand what their card represents.
anti-farming controls and design · give rare cards visual prestige · create a hidden achievement in Atom
Build a collection with intent