Collectible database
Collectible Tracker
Potions, relics, events, and unlocks
The collectible tracker collects pages that are not pure strategy: unlocks, potions, event outcomes, relic discovery, and completion notes.
Potions, events, relic discovery, and unlock notes
Configurable by section
How this page should grow
Start with discoverability and spoiler controls. Later, each collectible type can become a filtered table with location, unlock condition, patch, and related builds. The tracker should help players move from broad completion questions into the exact page they need: potions, relics, events, unlocks, achievements, or hidden progression.
Tracker structure
The tracker should not mix every collectible into one long list. Group items by player intent: completion goals, unlock routes, run tools, and spoiler-heavy discoveries. That makes the page useful before the database is complete and keeps it maintainable as Early Access changes.
- Route gameplay-changing relics to the relic database.
- Route completion goals to achievements and unlocks.
- Keep spoiler-heavy outcomes below clear labels.
Common mistake
The common mistake is treating the collectible tracker like a complete checklist before the current build is verified. Exact unlock conditions, hidden rewards, potion lists, event outcomes, and completion requirements are needs verification during Early Access.
Evidence to collect next
The next collectible pass should record the source type, patch version, unlock or discovery condition, spoiler level, related page, and whether the item changes strategy or only completion tracking. That structure keeps the tracker useful without pretending every hidden item is finished.
Release priority
Prioritize collectibles that change player decisions first: potions, unlocks, event rewards, and relic discovery. Pure completion notes can wait until the strategy-impacting tracker rows are verified.