Maps Database

Separate a named place from a route through it

The family farm is a confirmed home base, and official descriptions establish a town shaped by seven supernatural families. Those broad facts do not define every district boundary, service location, or path. A verified map record should use the label shown by the game or an official source. An editorial route should describe turns and landmarks without inventing a new location name.

When two sources use different wording, preserve the exact context instead of forcing a match. A storefront may describe a general area while the in-game map uses a specific label. Regional localization can also change displayed names. The current game language, platform, and version belong with any precise transcription.

Learn maps in small loops

Choose one destination and one return landmark before leaving the farm. Follow the main path, note a service or family area on the route, and add side branches on later nights. A small repeated loop teaches travel cost and orientation better than crossing several unfamiliar regions while checking the map at every turn.

Record landmarks that remain visually clear in the game's night setting. A path description should explain direction from a stable point rather than from a temporary character, weather effect, or quest marker. If an obstacle changes with progression, state the required context and keep the route partial until both states are checked.

• Start from an in-game label or stable service, not an invented area name.
• Describe one decision point at a time and include the return path.
• Keep resident schedules separate from the location record.
• Attach progression context to blocked paths and changing landmarks.

Prepare for a location, not only the journey

Before a distant trip, identify the objective, required equipment or spell shown by the game, available inventory space, and the time needed to return. Carry a small reserve instead of every valuable item. A gathering route should leave room for unknown materials, while a service visit should keep the required currency or quest item easy to find.

A service location does not verify its hours, inventory, or resident schedule. Record those fields independently and expect story or patch context to matter. If a service is closed or a resident is absent, return under a controlled change before publishing a universal schedule.

Report map corrections with reproducible directions

A useful location correction names the starting point, each stable turn or landmark, the destination label, platform, language, and relevant progression. Include a screenshot when possible, but write the route so it can still be followed without the image. State whether the map was viewed before or after a quest changed the area.

This database will not publish a separate thin page for every rock, tree, shop, or pickup. Locations should become independent guides only when they solve a distinct search task and have enough verified context for preparation, access, and related objectives. Until then, the category page and guide anchors remain the stable route.