Skip to content

Configuration: Badges Overview

ccpk1 edited this page Mar 8, 2026 · 3 revisions

Use this page to choose the right badge model before configuring details.

Note

ChoreOps may use more kid-friendly dashboard wording for badge families. In dashboards and examples, Rank Badges map to Cumulative Badges, and Quest Badges map to Periodic Badges. Home Assistant configuration screens still use the original setup terms.


Badge models

Cumulative badges (Rank badges)

Best for long-term progression.

  • Driven by lifetime points
  • Supports multiplier-based progression boosts
  • Can include maintenance windows for ongoing rank health

Periodic and daily badges (Quest badges)

Best for short-cycle habits and accountability.

  • Driven by cycle-based targets
  • Resets on daily/weekly/monthly/custom schedules
  • Can include failure penalties and tracked-chore filters

Special and linked badges

Best for event or integration-based rewards.

  • Special badges: date/occasion-driven moments
  • Linked badges: triggered by achievement/challenge outcomes

Decision guide

Choose Cumulative when:

  • You want persistent rank identity
  • You want multipliers tied to progression
  • You want milestone-driven motivation

Choose Periodic/Daily when:

  • You want recurring missions
  • You need strict cycle windows
  • You want contracts with optional penalties

Choose Special/Linked when:

  • You need one-off event rewards
  • You want rewards tied to external milestones

Strategy patterns

Pattern 1: Rank + mission stack

  • Use cumulative badges for long-term status and rank identity
  • Use periodic badges for weekly habit pressure and quest loops

Pattern 2: Strict accountability mission

  • Use no-overdue target types
  • Limit tracked chores to high-priority tasks
  • Keep penalties proportional and recoverable

Pattern 3: Seasonal campaigns

  • Use periodic badges with explicit end dates
  • Pair with simple reward payouts

Common traps

  • Mixing competitive shared-first chores into completionist missions without filtering tracked chores
  • Overusing penalties and creating low-motivation loops
  • Using too many badge themes at once, making progression unclear

Keep pages scoped

  • Use Configuration pages for setup steps and field meaning
  • Use Advanced pages for strategy and tradeoffs
  • Use Technical pages for entity and attribute contracts

Related docs


Last Updated: March 2026 (dashboard terminology bridge for Rank and Quest badge wording)

Clone this wiki locally