- We Are So Dead relic locations should be recorded by area, enemy, chest, and drop condition.
- Verify each relic through an in-game pickup, reward screen, or repeatable encounter.
- Prioritize repeatable routes over unconfirmed rumors about rare one-time rewards.
- Keep a backup route because drop tables and encounter conditions may vary.
- Use the checklist before marking any relic location as confirmed.
How to Read We Are So Dead Relic Locations
When searching for We Are So Dead relic locations, separate confirmed discoveries from useful leads. A location is confirmed only when the relic has been obtained or clearly displayed in the game. A message, screenshot without context, or unverified claim can suggest where to investigate, but it should not be treated as a final drop location.
This distinction matters most when a relic can appear from several sources. Some rewards may be tied to an enemy, while others may come from a chest, stage-clear reward, event objective, or hidden interaction. Record the source rather than labeling an entire area as the answer.
| Evidence type | Reliability | How to use it |
|---|---|---|
| In-game reward screen | High | Record the stage, difficulty, encounter, and reward condition. |
| Relic pickup screenshot | High | Confirm the item name and location before publishing. |
| Repeatable drop confirmation | High | Test the encounter more than once when possible. |
| Map marker without item proof | Medium | Treat it as a lead requiring verification. |
| Unidentified chest or enemy claim | Low | Do not mark it as confirmed yet. |
Use “reported,” “suspected,” and “confirmed” as separate labels. This keeps the relic index useful without presenting uncertain information as fact.
Confirmed Location
- The relic name is visible
- The source is identified
- The result can be reproduced or independently checked
Reported Location
- A player has provided a lead
- The exact condition may be unclear
- More testing is needed before confirmation
Unresolved Lead
- The area or encounter is only suspected
- No reliable item evidence is available
- Keep it outside the confirmed route
Step-by-Step Relic Search Route
A consistent search route is more valuable than moving randomly between locations. Begin with content that can be entered repeatedly and completed quickly. Check obvious chests, elite enemies, reward screens, and optional objectives before spending time on difficult encounters.
Do not reset a run immediately after one unsuccessful attempt unless the route is known to be short. First, verify whether the relic is tied to a specific enemy, chest, difficulty, or completion condition. A failed attempt may indicate an incorrect trigger rather than a low drop chance.
Choose One Test Area
Select a location with a clear entry point and a repeatable encounter. Record the area name, difficulty, recommended level, and whether the run contains chests or elite enemies.
Map Every Reward Source
Inspect visible chests, named enemies, optional fights, stage objectives, and the final reward screen. Do not assume the first item source is the only possible source.
Record the Exact Result
Write down the relic name, source, encounter condition, and whether the reward appeared during combat or after completion. Screenshots are useful for later comparison.
Repeat the Same Condition
Run the encounter again without changing the relevant variables. If the result changes, label the relic as chance-based or conditional rather than guaranteed.
Update the Route Status
Mark the location as confirmed, reported, or unresolved. Add the date of the test so future players can identify older information.
| Search phase | Primary action | Record this |
|---|---|---|
| Entry | Select a repeatable area | Area name and access condition |
| Exploration | Check chests and interactable objects | Object position and trigger |
| Combat | Defeat named or elite targets | Enemy name and battle condition |
| Completion | Review stage-clear rewards | Reward screen and completion result |
| Verification | Repeat the same run | Whether the relic appears again |
Change only one variable at a time. If you change difficulty, party setup, route, and target simultaneously, you cannot identify what caused the relic to appear.
Best Farming Priorities and Route Choices
The best farming location depends on the relic’s source and the cost of each attempt. A fast route with a lower visible reward may be more efficient than a long challenge that provides several possible items. When the drop source is unknown, start with the shortest repeatable content and expand only after obvious sources have been checked.
Use the following priority order when building a farming route:
- Known enemy source: Focus on the encounter containing the target enemy.
- Known chest source: Route directly to the chest and leave if the reward condition is satisfied.
- Stage-clear source: Complete the entire activity and inspect the final reward panel.
- Unknown source: Check optional enemies and rewards before committing to the longest content.
- One-time content: Complete it only after confirming that the reward cannot be obtained elsewhere.
| Route type | Time cost | Best use | Main risk |
|---|---|---|---|
| Short repeatable encounter | Low | Testing an enemy or chest drop | May offer a narrow loot table |
| Standard stage clear | Medium | Checking completion rewards | Requires finishing the full stage |
| Elite or challenge route | High | Rare or condition-based relics | Longer attempts can reduce efficiency |
| One-time objective | Variable | Unique rewards and progression items | Mistakes may require a later reset |
| Unknown-area sweep | High | Initial investigation | Poor efficiency without a clear hypothesis |
Fast Test Route
Use when the suspected source is nearby and repeatable. Test the same target several times before expanding the search.
Reward Route
Use when the relic appears tied to stage completion. Track objectives, difficulty, and final reward screens.
Deep Search Route
Use only after simple sources are ruled out. Clear optional encounters and inspect less obvious rewards.
Do not spend repeated runs on a location solely because it contains a chest or powerful enemy. Without a confirmed relic result, it remains a lead rather than a farming destination.
A useful route log should contain enough detail for another player to reproduce the test. Avoid vague notes such as “found in the ruins” or “dropped from a boss.” Instead, identify the stage, path, target, condition, and reward timing.
| Route log field | Example format |
|---|---|
| Area | Named location or stage |
| Source | Chest, enemy, objective, or completion reward |
| Condition | Difficulty, optional objective, or encounter trigger |
| Result | Relic obtained, different item, or no relic |
| Status | Confirmed, reported, or unresolved |
| Test date | 2026-08-18 or the actual test date |
Relic Preparation and Inventory Management
Before farming, prepare a loadout that reduces failed attempts rather than maximizing damage alone. A reliable defensive setup can save more time over several runs, especially when the suspected route includes elite enemies or optional battles.
Prioritize preparation in this order:
- Bring enough healing or recovery resources for the full route.
- Equip defensive options that reduce the most common damage type.
- Keep inventory space available for unidentified or duplicate rewards.
- Note the current relic count before beginning the test.
- Save or record progression when the game permits it.
If a relic is believed to come from a specific encounter, avoid changing your setup between tests unless the change is part of the experiment. Different equipment, characters, or difficulty settings can make results difficult to compare.
Relic Search Checklist:
- Choose a repeatable area with a clear reward source
- Record the difficulty and encounter conditions
- Check chests, elite enemies, objectives, and completion rewards
- Confirm the relic name on the pickup or reward screen
- Label the location as confirmed, reported, or unresolved
Keep a simple duplicate log. Multiple copies can reveal whether a relic is a repeatable drop, a one-time reward, or part of a wider loot table.
| Preparation item | Why it matters | Recommended record |
|---|---|---|
| Recovery supplies | Prevents failed long runs | Starting and ending supply count |
| Defensive gear | Reduces restart risk | Main damage type resisted |
| Free inventory space | Prevents missed rewards | Available slots before entry |
| Test notes | Makes results comparable | Date, route, source, and result |
| Backup route | Maintains progress when testing fails | Second suspected location |
Building a Trustworthy Relic Index
A strong We Are So Dead relic locations page should function as a living index rather than a list of unsupported guesses. Each entry should answer four questions: where is the relic found, what produces it, what conditions apply, and how certain is the result?
Use concise entries so readers can scan the page while farming. If a condition is unknown, say so directly. It is better to leave a field unresolved than to invent a guaranteed drop requirement.
| Relic entry status | Meaning | Publishing rule |
|---|---|---|
| Confirmed | Obtained with a documented source | Include in the main location table |
| Repeatable | Obtained more than once under the same condition | Add farming guidance |
| Conditional | Appears only after a specific trigger | Explain the trigger clearly |
| Reported | Supported by a player lead but not tested | Place in a separate reported section |
| Unresolved | No reliable item evidence | Do not present as a location |
When updating an entry, preserve the previous status until new evidence is checked. A single failed run does not disprove a location if the drop is chance-based, but it should prevent claims that the reward is guaranteed.
Include the test date, but avoid treating an old result as current proof when the game has received balance changes or content updates.
The most useful final page structure is:
- A quick table of confirmed relics.
- A separate table for reported locations.
- Farming routes grouped by source type.
- Conditions and preparation notes.
- A change log showing when entries were tested.
This structure helps new players find actionable routes while giving experienced players enough detail to verify uncertain claims.
FAQ: We Are So Dead Relic Locations
Q: What counts as a confirmed We Are So Dead relic location?
A location is confirmed when the relic name and its source are visible in the game, and the result has been tested or documented clearly enough for another player to reproduce.
Q: Should I farm an area if someone reports a relic there?
You can test it as a lead, but do not treat it as guaranteed. Record the exact route, encounter, difficulty, and reward result before adding it to the confirmed list.
Q: How can I improve relic farming efficiency?
Use the shortest repeatable route that matches the suspected source. Change one variable at a time, track failed attempts, and leave long challenge content for cases where simple sources have been ruled out.
Q: What should I do when a relic location is unknown?
Mark the entry as unresolved, list the areas already tested, and continue checking enemy drops, chests, optional objectives, and stage-clear rewards without claiming a guaranteed source.
A careful relic index is more valuable than a longer list. Confirm the source, document the condition, and keep uncertain locations clearly labeled.