Official visual references
Screenshots and trailer frames are used as visual anchors for the guide. Gameplay stats, locations, drops, boss routes, and build rankings remain labeled until they can be verified in the playable Early Access build.
Relic database design
Relic pages win when they connect passive effects to decisions. A player does not only need to know what a relic does. They need to know which build wants it, where to find it, whether it stacks, and whether it changes combat behavior.
Before launch, this section shows which relic fields matter and what needs testing.
| Field | Purpose | Verification |
|---|---|---|
| Passive effect | Core function | Needs exact in-game text |
| Location | Turns data into a guide | Needs screenshot or route |
| Best build | Connects to build hub | Needs testing |
| Stacking or conflicts | Prevents bad combinations | Needs repeat tests |
How to test relic strength
The strongest relic is not always the one with the flashiest text. It may be the one that solves a build's weakness, reduces resource pressure, improves safety, or changes a breakpoint.
Every relic recommendation needs the build used, enemy or area tested, and patch version.
How to use database pages before entries are complete
Database pages are useful before launch when they show exactly what will be tracked and what remains unknown. For Fatekeeper, players will look for weapon scaling, spell cooldowns, relic effects, enemy weaknesses, boss rewards, and world locations as soon as Early Access is live.
Use these pages as a verification ledger. Official facts, trailer observations, and hands-on discoveries are separated so you can decide whether a data point is safe to use in a build or route.
| Data type | Useful field | Trust requirement |
|---|---|---|
| Weapons | Damage, scaling, moveset, location, upgrade cost | In-game item text or repeated testing |
| Spells | Cost, cooldown, cast safety, damage type, combo | Hands-on combat tests |
| Relics | Passive effect, stacking, build synergy, location | Screenshot or exact menu text |
| Enemies and bosses | Patterns, weakness, drops, rewards | Repeatable encounters and patch version |
How reliable is this information?
This relic data guide separates confirmed information from hands-on findings. If a detail is not playable or testable yet, it is marked clearly instead of being presented as finished advice.
Exact stats, boss routes, hidden loot positions, drop rates, and final balance notes stay unverified until there is direct evidence from the playable version.
| Claim type | Evidence needed | Reader takeaway |
|---|---|---|
| Official facts | Steam and official site copy | Use now |
| Trailer analysis | Gameplay and announcement trailers | Label as analysis |
| Community findings | Player testing after Early Access unlocks | Do not publish as fact yet |
Sources and verification status
Confirmed details come from official, storefront, publisher, video, community, or media references. Exact gameplay data is held back until it has direct evidence from the playable build.