API Credentials Find your credentials ↗

Privacy & Data

Habitica Party Analyzer runs entirely in your browser. No data you enter — including your User ID, API Token, or any snapshot files you upload — is sent to any server other than Habitica's own API. Your credentials are only stored if you explicitly click Remember on this computer, and only in your browser's localStorage. The source code is MIT-licensed and can be audited in full by viewing the page source.

Snapshot Files

Each snapshot is a point-in-time export of your party's data from the Habitica API. It captures member profiles, quest achievement counts, pet and mount collections, egg and potion inventories, and quest scroll inventories. Snapshots are named with a timestamp so the tool can sort them chronologically. Collection and scroll analysis works from a single snapshot. Participation analysis compares consecutive snapshots to infer quest activity over time — the tool never modifies or re-uploads your data.

Quest Participation

Habitica only exposes cumulative lifetime quest completion counts — it does not expose a log of when each quest was completed. Participation is inferred by diffing the counts between consecutive snapshots. A positive delta means the member completed at least one run of that quest in that interval.

Eligibility works as follows. For each snapshot interval, the tool infers the party's total completions for each quest type as the maximum delta observed across all members present in both snapshots. A member is only held eligible for quests that ran while they were in the party. Members who appear for the first time in snapshot N are not counted as eligible for any quest that completed before snapshot N.

Est. Join date is the timestamp of the earliest snapshot in which a member appears. If they were already present in the first snapshot you uploaded, the date is prefixed with ≤ because their actual join date may be earlier than your oldest file.

Last Quest is the number of days between the member's last confirmed quest activity and the final snapshot. It cannot detect activity that happened before your earliest file, or activity that happened between two snapshots where the member's total count didn't change.

Pet & Mount Collection

The hatchable pet universe is inferred from the party's combined collection rather than from a hardcoded master list. The tool identifies which quest animals and quest potions have been seen across all party members, then builds the full set of possible combinations: Standard animals × Standard potions, Standard animals × Quest potions, Quest animals × Standard potions, and a small set of exception combinations. All combinations listed in the scroll maps are always included, even if nobody in the party has hatched them yet.

Shortfall for a given combination is the number of hatches still needed. Most combinations require two hatches (one for the pet, one to raise it to a mount). Quest × Quest combinations are treated as binary — either owned or not. Shortfall is reduced by the member's current inventory of the relevant egg or potion.

Special pets (Veteran, Gilded, Hopeful, RoyalPurple variants, and others that cannot be hatched normally) are excluded from shortfall calculations entirely.

Quest Recommendations

Recommendations are only shown for quests that reward a hatchable egg or potion. Each quest run rewards 3 copies of the item. The three ranking modes are:

• Total Shortfall — ranks by the sum of shortfall across all party members. Prioritizes the quest with the most total hatches still needed.
• Prioritize Unowned — ranks by the number of members who have neither a pet nor a mount of this variety. Useful for ensuring everyone gets their first hatch before duplicates are accumulated.
• Effective Yield — ranks by the sum of min(shortfall, 3) per member. Since each run gives exactly 3 items, any shortfall beyond 3 requires multiple runs. This mode maximizes the number of hatches actually satisfied per quest run.

Scroll holders are party members who own at least one copy of the relevant quest scroll. The "Scroll owned" filter limits results to scrolls that at least one party member can actually run.

Scrolls Needed in the Scrolls tab is ceil(maxMemberShortfall / 3) — the number of quest runs needed to satisfy the most-behind party member. Scrolls to Buy is the difference between that number and the party's current total copies of that scroll.

Limitations

• Quest completion counts are cumulative totals. If a member's count decreases between snapshots (account reset or data anomaly), the delta is clamped to zero and treated as no activity.
• The eligibility algorithm assumes the member with the highest delta in an interval represents the true party total. If a member ran the same quest type privately many times, their delta could overstate how many party quests were completed.
• Party quest participation data (quest.members in the API) reflects who accepted the quest invitation, not necessarily who was present and contributing for its entire duration.
• Last Quest and Est. Join calculations are bounded by the snapshot window. Activity and join dates before your earliest file are not visible to the tool.
• Pet classification relies on the party's observed collection. If a combination has never been seen by any party member, the tool still includes it via the scroll maps — but truly novel combinations from future Habitica content may require a tool update.
• The tool reads from the /api/v3/members/:id endpoint, which is rate-limited by Habitica. Fetching a large party may take a minute or two due to the required delay between requests.