Equipment Database

Distinguish tools, stations, and references

A tool travels with the player or performs an action, a station provides a place for crafting or processing, and a reference explains a system such as spells. Those categories can overlap in casual conversation, but keeping them separate makes a lookup more useful. The current database includes the grimoire, cauldron, and fishing gear as broad records because official descriptions confirm spell-casting, potion-making, and fishing.

A confirmed activity does not establish every associated item. Fishing in the official feature list is evidence that the activity exists, not a complete list of rods, upgrades, bait, prices, or acquisition steps. Likewise, potion-making confirms the cauldron concept without verifying every recipe or ingredient. Each precise value needs its own source or current-build observation.

Verify function before planning an upgrade

Read the current in-game description and identify the repeated action the equipment changes. A useful upgrade decision connects that effect to a bottleneck you have already observed. Buying an item because it is expensive, magical, or newly available does not guarantee that it improves the route consuming most of your time.

Keep acquisition, function, and cost as separate notes. A shop location may be verified while the price changes, or an item may be received through progression rather than purchased. When recording an upgrade, include the before and after descriptions, platform, version, and any visible prerequisites. Avoid applying one tier's effect to every later tier.

• Identify the exact equipment label shown by the current build.
• Record where it was obtained separately from what it does.
• Attach currency, material, and tier costs to a platform and version.
• Test the repeated route before deciding that the upgrade removed the bottleneck.

Fit equipment into the nightly route

Prepare only the equipment required for the primary activity and leave unrelated valuables in known storage. This keeps inventory readable and makes a failed route easier to diagnose. If an activity fills inventory faster after an upgrade, the next bottleneck may be storage or travel rather than another tool tier.

For magic and potions, confirm the pattern, recipe, effect, and resource requirement in the current reference before leaving home. The equipment record can explain what the grimoire or cauldron is for without claiming unverified costs. Exact spell and recipe data should remain in a verified guide or future structured record when it can be maintained reliably.

Report equipment changes precisely

When a patch changes equipment behavior, identify the item, tier, action, old result, new result, platform, and version. A screenshot of the description is useful, but a repeatable action shows whether the text and behavior agree. Do not generalize a changed animation into a changed stat without measuring the actual result.

For missing or inaccessible equipment, include the visible objective and progression context. An item that is unavailable in one save may be locked behind a condition rather than removed. The database will mark the acquisition field partial until that condition can be reproduced.