Nightwater Resources and Buildings

Quick answer: Steam confirms more than 20 resources, more than 60 constructible buildings and over 100 combined buildings, crafts and buffs.

What to do

1. Resources should be tracked by name, source biome, manual collection method, automation option and milestone unlock.
2. Buildings should be tracked by category, function, inputs, outputs and unlock condition.
3. Crafts and buffs should stay tied to the resource milestone that unlocks them.
4. Rows should appear only when a source confirms the fields, so players do not build around guessed recipes.

Why this matters

This is the reference foundation for launch week, not a fabricated complete database.

Sources

• Steam Store: https://store.steampowered.com/app/3983860/Nightwater/
• Steam Community: https://steamcommunity.com/app/3983860
• SteamDB: https://steamdb.info/app/3983860/

Fact levels

• Official confirmed: Steam or publisher-facing material names the feature or count. Use this for scope, such as resources, buildings and automation existing.
• Community observed: repeated player reports or walkthrough footage show the same result. Use this as a launch-week lead, then verify in your own build.
• Direct gameplay: a player can reproduce the input, output, location or unlock condition. Use this for recipe rows, building rows and route steps.
• Not verified: the field is expected but not yet backed by a source. Keep it out of build plans until confirmed.

Current confirmed scope

• Resources: more than 20 resources are part of the game scope. Launch-week rows still need names, source biome, collection method and milestone use.
• Buildings: more than 60 constructible buildings are part of the game scope. Each row still needs function, inputs, outputs and unlock condition.
• Crafts and buffs: the combined building, craft and buff set is over 100. Each entry still needs the resource or building that unlocks it.
• Automation: farmers, assemblers, storage units and pipes are public features. Exact chains, connection rules, rates and bottlenecks still need gameplay verification.

How to track resources

A useful resource row needs a name, source, biome or unlock context, manual collection method, automation option and the milestone it supports. Steam confirms more than 20 resources, but launch-week rows should still be added only when the field is observed or confirmed. That makes the reference slower to fill, but much more useful for players making real build decisions.

How to track buildings

A building row should explain what the building does, what it consumes, what it outputs and what unlocks it. Steam confirms more than 60 constructible buildings and over 100 combined buildings, crafts and buffs. Those counts are useful for scope, not for inventing a full database before the game can be checked.

Player workflow

When you find a new resource, ask what it unlocks before stockpiling it. When you unlock a new building, test it beside storage and one input source before merging it into a larger chain. When you find a buff or craft, note whether it changes gathering speed, automation capacity, exploration or Lighthouse progress.

Mistakes to avoid

Do not copy recipe tables without a source. Do not mix a resource source with a building output unless both are confirmed. Do not assume every biome resource is required for the same stage of progression.

Second-screen notes

Keep this page open while playing and update your own notes in small, testable pieces. A reliable Nightwater note should say what you saw, where you saw it, what changed after the action, and whether the result repeated. That style is slower than copying a claim, but it helps avoid bad factory layouts and misleading route advice during launch week.

When two sources disagree, prefer the source closest to the game state: the Steam store for store metadata, developer news for launch timing, Steam Community for current player reports, and direct gameplay for recipes or ending steps. If a detail changes after launch, keep the older note only when it explains a version difference.

Use the related pages as a loop. Release status tells you whether the build is live, Starter Guide gives the first route, Automation explains how to reduce repeated work, Resources and Buildings organize the reference data, Biomes and Minigames track expansion, Lighthouse and Endings keeps story goals spoiler-safe, and Help covers demo or controller issues.

FAQ

Should I use exact recipe tables yet? Use them only when the entry names a source or direct observation.

What should I record first? Record unlock conditions, resource source, machine purpose, output result and any Lighthouse-related clue.

Can community posts answer support issues? They can show that players are seeing a problem, but official news or repeated reports are stronger for broad status.