Add daily usage counter for custom Rewards

[ghoztti]

Description:

Currently, custom (user-created) Rewards lack any form of usage tracking. Unlike Habits and Dailies, which provide clear feedback and history, Rewards offer no visibility into how often they are redeemed.

This creates a gap in the feedback loop and makes it difficult for users to self-regulate reward consumption—especially for behavior-based rewards (e.g., limiting social media use).

Proposed Feature (Core):
Introduce a simple daily usage counter for custom Rewards, allowing users to see how many times each reward has been redeemed within the day. This would bring consistency with existing tracking systems (Habits/Dailies) and improve awareness without adding friction.

Use Case:
Users who create custom Rewards to manage habits or limit behaviors often rely on memory or external tracking. A built-in counter would provide immediate feedback and reduce unintentional overuse.

Optional Enhancement:
As a further extension, consider allowing users to set an optional daily limit per custom Reward. This would support stricter self-regulation for those who want it, while keeping the system flexible.

Scope Clarification:
This applies only to custom (user-created) Rewards, not to purchasable in-game items (equipment, cosmetics, etc.).

Why This Matters:

• Restores parity with Habits and Dailies tracking
• Strengthens Habitica’s behavioral feedback loop
• Supports intentional use of rewards rather than passive consumption

[AayushM0]

Hi! I’d like to work on this issue.

From my understanding, the goal is to introduce a daily usage counter for custom Rewards so users can track how often they redeem them, improving the feedback loop similar to Habits and Dailies.

I have two options in mind and i would love your opinion on both

Option 1: Explicit Tracking on the Reward (Schema Update)

• Add a lightweight usage field to reward-type tasks (e.g., { date, count })
• Update the reward scoring logic to increment/reset the count based on the current date
• Expose this value to the frontend for display

Option 2: Derive Usage from Existing History (No Schema Change)

• Leverage existing task history/logging (if applicable)
• Compute the daily usage count dynamically by filtering reward completion events for the current day
• Avoids introducing new fields but may involve additional query overhead

option 2 prevents changing the data models but requires heavy querying while option 1 is straightforward but requires changes in the actual model

Please let me know which approach you’d recommend. Once confirmed, I’ll proceed with the implementation.

Also, if this issue is available, I would like to be assigned to it.

Thanks!