Database Editorial
Relic Lookup Only Matters If It Tells You What The Pickup Changes
Relics are run-shaping objects, not collectible trivia. This page is supposed to tell you which pool a relic belongs to, whether it is trade-friendly or owner-bound, what theme it actually serves, and when the correct next step is a more focused planning page.
Relic mistakes poison the run for longer than bad single-card picks
A relic entry is not just a passive bonus. It changes route quality, shop value, swap logic, and what future cards even count as hits. That is why this page tracks 298 relics with pool, category, trade profile, and theme instead of dumping a flat icon wall on the screen.
The whole point is to answer a boring but important question fast: does this relic belong in the shell you are building, or are you admiring text that does not survive contact with the deck, route, or owner restrictions attached to it?
Pool, trade profile, and unlock timing come from the current relic dataset
This database reads from the site relic dataset that already normalizes pool, rarity, category, theme tags, trade profile, owner state, and unlock metadata. That keeps the filters honest and prevents the page from hand-waving around whether a relic is starter-only, pickup-bound, or realistically movable.
The verification rule is simple: if the dataset exposes a stable property, the page lets you filter it. If the site does not have a clean rule for a nuance yet, this page should not pretend otherwise. It is a structured lookup first, editorial guidance second.
- Pool and rarity come from the live relic index, not display-only copy.
- Trade profile is surfaced explicitly because pickup logic changes planning.
- Unlock timing is kept visible for relics that do not belong to the default baseline.
Ownership, trade profile, and shell fit beat raw relic prestige
The strongest read on this page is usually not rarity. It is whether the relic is trade-friendly, pickup-bound, owner-bound, or starter-only. That one label immediately changes how aggressively you should plan around it, especially in co-op, swap lines, or any run where future access matters as much as current strength.
Theme tags matter for the same reason. A relic that is merely good in the abstract can still be a low-quality pickup for the current shell, while a narrower relic becomes premium the moment the deck already leans into the right theme, route pressure, or support card package.
- Read trade profile before you decide the relic is universally premium.
- Use theme notes to judge fit, not to build fake combo fantasies.
- Starter relics should be read as structural context, not draftable options.
The trap is reading relics like isolated trophies
A relic database becomes useless the moment you treat every shiny line as a generic power spike. Many relics are only strong inside the correct shell, and some are actively misleading if you ignore trade restrictions, starter ownership, or the route cost required to make them matter.
Another bad habit is sorting by rarity and stopping there. Rare relics are not automatically clean pickups, and common relics are not filler. The real question is what job the relic solves now, what it locks in later, and whether the deck or route can cash that promise.
- Do not read a trade-restricted relic as if every player can move or replace it freely.
- Do not confuse a strong abstract effect with a strong current pickup.
- Do not ignore the first theme note just because the icon looks familiar.
Use the next page that matches the actual relic question
Relic decisions spill into pathing, sustain, and deck fit. These pages handle the cases where a relic lookup should turn into a run-planning decision instead of one more list scroll.
Check sustain and slot pressure when a relic changes how freely you can spend bottles.
Open page ->Rest Site OptimizerUse this when the relic changes whether you should smith, rest, or greed a route.
Open page ->Wax Relic TrackerJump to a narrower relic planner when the question is really about wax-line progression.
Open page ->
