CURRENT DATABASE // RELICS
Relics are where a build becomes a system. They can turn a generic weapon event into a status engine, convert a shop decision into permanent growth, or protect a fragile route long enough to reach its payoff. They can also look excellent in isolation while doing nothing in the run that actually exists. This guide focuses on the gap between a relic's text and its practical value.
The item library records current effects, tags, evidence labels, and related entries. Read those fields as a route map. A relic is worth a slot when its trigger can happen repeatedly, its payoff arrives before the run ends, or it directly fixes the reason the run is failing. If none of those statements is true, rarity is not enough.
Trigger first, payoff second
Every relic question starts with its trigger. Does it activate on Embarkation, Destination, Ultimate, dismantle, a critical hit, a status application, a reload, or a weapon event? Then ask how often that trigger happens in the current loadout. A huge payoff attached to a trigger you rarely create is a future promise, not current power.
After the trigger, read the payoff as a job. Some relics add direct damage, some change the economy, some make a status more frequent, and some buy survival. The job determines what it should replace. A damage relic should not automatically replace survival if the run is dying; an economy relic should not replace the route's only engine component just because it can scale later.
Timing decides whether economy is value
Economy and growth relics are sensitive to when they arrive. A relic that pays at every checkpoint needs enough checkpoints left to repay its slot. A dismantle relic needs spare objects and a reason not to keep them. A starting trigger may be strongest early because it gets more time to compound, while a boss relic may become correct only when the boss window is close enough to matter.
When a relic arrives, write down the next place where it can pay back. If you cannot name that moment, treat it as a conditional experiment and preserve a fallback. This keeps the run from spending several more choices supporting a relic whose reward is always one room away.
Forged text is not a free ranking
A forged effect can change the value of a relic, but it does not erase route fit. Compare the normal and forged records, identify what the extra effect changes, and then check whether the run can activate both parts. A forged relic that supports the current engine can be a strong anchor; a forged relic with an unrelated condition can still be the wrong slot.
The database calls out forged text when it is recorded. If a number or interaction has not been measured, the page says so instead of turning the forged version into an invented tier claim. That distinction matters for patch reviews: official text tells you what to test, while a route recommendation explains why the test belongs in this build.
Use relics to solve the actual failed-run link
Review the last failed run before picking the next relic. Did the run lose because the weapon could not clear rooms, because the boss window took too long, because reload gaps were unsafe, or because the economy never converted into power? Match the relic to that failure. A relic that improves a problem you do not have is not a solution, even if its tags match the Hunter's general theme.
The Planner helps here by showing route fit, element coherence, and conflicts. Use it to compare the relic you want with the relic that repairs the run. The goal is not to fill every slot with the same category; the goal is for every slot to have a job that the rest of the loadout can actually feed.
Keep a lower-ceiling relic ready
A safe fallback relic often has a better expected value than a perfect relic that appears once in ten runs. Keep one reliable elemental match, reload answer, survival answer, or direct engine support in mind. The fallback protects the run while you wait for a core item and prevents the common mistake of dismantling a working slot to chase a more exciting name.
Recheck the current effect after patch 1.0.479. When a patch changes a trigger, the right replacement can change too: an old support relic may no longer fire often enough, while a previously quiet tag may become the new bridge. The page's evidence label tells you how strongly to trust the route note while you retest.
Five questions to ask before you commit
- What exact event activates this relic in the current run?
- How many times can that event realistically happen before the next checkpoint or boss?
- Which failed-run problem does the relic fix, and what does it replace?
- Does the forged effect change the route or only increase a number you cannot yet verify?
- What reliable relic remains useful if the ideal trigger never arrives?
Start with the most connected entries
These are starting points from the current planner database, not a promise that one entry wins every run. Open the entry for its effect text, route notes, related picks, and a direct Planner link.
Turn the guide into a live decision
Browse the full relics index, open the object you actually see, and send it into the Planner. The best choice depends on the Hunter, weapon, stage, and missing trigger in front of you.
Open the full item library Open a Planner example