Choose the entity type before the expedition
Use Items & Gear for carried slots, Patron Saints for route coverage, and Threats & Responses for behavior cues. This entrance keeps the three entity types separate instead of duplicating them in one mixed table.
Cross-entity field reference
This is the database entrance, not a mixed table. The expedition planner decides the contract and six-slot plan; these four focused references keep Items, Saints, Threats, and Weapons separate so each result has the right fields, image coverage, and next action.
Fast database route
Use the picture where one is available to confirm the named entity, then read its route job and verify the live item or weapon panel after a patch.
Use this page when the question names a carried item, price, effect, weather answer, recovery option, or Ox-wagon storage decision.
Open focused reference →
Use this page when the route needs rain, madness, fatal-hit, attrition, blade, or firearm coverage before leaving the galleon.
Open focused reference →
Use this page when a named threat, scream, isolation cue, hallucination, or field behavior changes the safe response.
Open focused reference →
Use this page when weather, noise, reach, rank, cost, or an Anvil branch decides which weapon can complete the next contract.
Open focused reference →Use the references in order
Treasure, weather, madness, recovery, or a specific field threat should decide the first lookup.
Do not mix unrelated rows. The focused page keeps its own filters, image set, and fields visible without JavaScript.
Keep the objective space open, choose the blessing or item that covers the named failure, and avoid a blind damage race.
Return to the contract route when the item, Saint, or threat decision is complete so the crew can protect the Ox-wagon path.
Start from the blocker
The quickest route is not to scan every record. Name the failure that could end the expedition, then open only the entity type that can change that decision.
Open Items & Gear when the question is about carry space, weather coverage, recovery, known effects, or Ox-wagon storage. The item page answers what the object does and what it protects; it does not decide the contract for you.
Choose an item →Open Patron Saints when rain, madness, a fatal hit, attrition, blade pressure, or firearm coverage is the blocker. Match the Saint to the failure first, then return to the expedition plan and spend the blessing where it removes the named risk.
Choose a Saint →Open Threats & Responses when a cue, scream, isolation pattern, hallucination, or field behavior changes the team call. Read the signal before spending damage, then use the regroup rule if the view is not confirmed.
Read a threat →Open Weapons when rain, noise, reach, rank, cost, or an Anvil relationship decides the firing lane. Filter to a condition, compare one same-family row, and keep the contract space open while testing.
Choose a weapon →Cross-entity handoffs
A named item, Saint, threat, or weapon is rarely the whole answer. The useful lookup starts with the failure, then crosses to the second entity only when that relationship changes the expedition decision.
| Observed failure | Start with | Cross-check | Safe handoff |
|---|---|---|---|
| Rain removes the Matchlock plan | Saint Eulalia | Crossbow, Longbow, or Flintlock | Restore one ranged option before pushing deeper; do not keep a disabled firearm as the whole damage plan. |
| A player is isolated or the route feels split | Prowler response | Buddy-pair contract plan | Stop the push, name the last shared landmark, and reform the pair before searching for a kill route. |
| A crewmate is down and the body is becoming dangerous | Ammonia Salts | Y'm-bhi | Choose the closest defensible recovery point; keep the Horn/Ox-wagon call separate from the revive decision. |
| Treasure movement attracts a pursuing threat | Hound of Tindalos | Horn and storage route | Protect the carrier and firing lane, then move the haul to shared storage instead of widening the personal loadout. |
| Team information cannot be trusted | Hallucination | Saint Dymphna | Stop movement and require a second player or stable landmark before firing, splitting, or changing route. |
| Rain or noise invalidates the planned weapon | Weapon lane | Saint Eulalia or weapon support | Filter to a usable lane, compare one same-family alternative, and keep the objective slot open while testing. |
Before leaving the galleon
The database is strongest when it removes one repeated failure from the next contract. Use the tables in this order, then stop when every remaining slot has a named job.
Decide whether the run is most likely to fail from weather, isolation, sanity, damage, recovery, storage, or an unknown landmark.
Open the item, Saint, threat, or weapon table that owns the immediate answer. Do not spend a slot on a second answer before the first problem is covered.
Cross-check the weapon, blessing, storage route, or buddy rule only when it changes the action. A stronger label without a different action is not a better loadout.
Carry the chosen answer back to Contracts & Loadouts and define when the group retreats, calls the Wagon, or stops to verify a cue.
Coverage boundaries
Counts describe the current public snapshot. Unknown prices, effects, or behavior remain unknown instead of being filled from a different entity type.
| Question | Open | First answer | Do not assume |
|---|---|---|---|
| What earns a slot? | Items & Gear | Category, known price/effect, weather, recovery, and slot job. | A current field price is permanent after a patch. |
| Which blessing covers the failure? | Patron Saints | Named weather, sanity, weapon, or recovery coverage. | A Saint is a universal tier ranking. |
| Fight, avoid, or verify? | Threats & Responses | Behavior cue, current response, and safe regroup action. | Every threat follows a normal kill route. |
| Which weapon fits the weather or upgrade budget? | Weapons | Family, damage, reach/durability, cost, rank, Anvil path, and route lane. | A listed number is a permanent tier ranking or every row has a verified icon. |
Share this guide
Share the current The Mound route, or copy the link for Discord and group chat.
Player questions
Use the current game panel before spending rare resources on a value that can change.
No. It is the database entrance. Items, Patron Saints, and Threats remain on separate focused pages so each table can keep its own fields, image set, and response.
Open Items & Gear. The current bounded set contains 24 visual item records with known price or field-found status, effects, and route guidance.
Open Patron Saints. The current table contains nine named blessings matched to weather, sanity, weapons, and recovery jobs.
Open Threats & Responses. The current bounded set contains 26 visual threat records with behavior cues and safe field responses.
Use Contracts & Loadouts after the entity lookup to confirm the six-slot plan, party split, weather coverage, Ox-wagon call, and retreat trigger.
