Relic database
Darv Relics
Relic-family tracker and support-density check
Darv Relics is a family page for long-tail relic searches where the useful question is which deck jobs the family supports.
Family value depends on deck support
Identify the payoff before ranking high
Family note
Relic-family pages should not pretend every relic in the family has the same tier. Darv-style relics need a support-density note: what they reward, which characters or builds can use that reward, and whether the payoff appears before the next elite or boss pressure window.
- Describe the family job before assigning a global tier.
- Link narrow relic value to the character or build that can use it.
- Downgrade family claims that need too many future rewards.
Support-density checklist
Darv Relics should be scored by how much of the deck already uses the family payoff. A single compatible card is not enough to raise the entire family; the deck needs repeatable triggers, draw or energy to use them, and a fight plan that benefits before the next elite or boss. Individual trigger names and exact values are needs verification until current-patch footage confirms them.
- Count existing support before calling the family a build direction.
- Check whether the payoff helps bad hands or only already-winning turns.
- Move individual relics separately when one Darv relic outperforms the family.
Best partners
Darv-style relics belong near character and build pages that can actually use the shared mechanic. If the support appears mainly in one character pool, route readers to that character instead of implying universal value. If the payoff is generic, connect the page to best builds and the relic tier list.
Common mistake
The common mistake is ranking the whole Darv family from one highlight relic. Family pages should teach the shared decision pattern, while individual relic pages handle exact tiers once enough evidence exists.
Evidence to collect next
The next evidence pass should capture the reward screen, the first fight where the Darv relic matters, and the first fight where it fails to matter. That contrast is important because a family can look powerful when every support piece appears early and still be unreliable in ordinary runs. Keep any exact trigger wording, relic counts, and numerical payoff claims marked needs verification until a readable current-patch tooltip and repeated run examples agree.