PRE-RELEASE · DEMO LIVE · SOURCE-CHECKED SEP 4
Nightwater Wiki — Automation, Resources, Buildings & Progression
Build the factory. Read the signals. Follow the light at the edge of reality.
Demo available · Full release not yet verified live
20+
resources confirmed
60+
buildings
100+
buildings, crafts & buffs
5
minigames
4
endings
8
local-first tools
FIELD INSTRUMENTS
Eight planners. No hidden math.
Local-first tools turn your own observations into a clearer factory, route, or completion plan. Unknown official values stay unknown.
TOOL 01
01
Production Chain Planner
Create source, building and storage nodes, connect the flow, record observed rates and find disconnected stages.
TOOL 02
02
Pipe Network Planner
Sketch sources, machines, storage and junctions, then flag disconnected machines and dead ends without fake capacity math.
TOOL 03
03
Resource Milestone Tracker
Track discovered resources, observed milestone progress and known unlocks while unknown thresholds stay unknown.
TOOL 04
04
Factory Layout Planner
Place generic gatherers, assemblers, storage, pipes and utilities on a collision-checked planning grid.
TOOL 05
05
Automation Readiness Checklist
Audit source, gathering, transport, buffering, processing, output, bottlenecks and expansion room with explicit reasons.
TOOL 06
06
Minigame Progress Tracker
Track five minigame slots with Dark Thicket pre-seeded and every unverified name left blank.
TOOL 07
07
Endings & Secrets Checklist
Track four endings and discovered secrets in a spoiler-safe local checklist without invented requirements.
TOOL 08
08
Progression Route Planner
Choose an automation, exploration, milestone, minigame or story priority and receive a transparent suggested focus order.
PROGRESSION RIBBON
From the first resource to the Lighthouse
A systems map, not a fixed walkthrough: follow what the current build actually reveals.
RESOURCE SIGNALS
Milestones turn gathering into progression
Official descriptions connect each resource to its own milestone progression, unlocking buildings, crafts and buffs. Exact thresholds remain gated.
AUTOMATION CHAINS
Make every handoff readable
Farmers, assemblers, storage and pipes are verified systems. Model their relationship before trying to optimize numbers the evidence does not expose.
CHAIN 01
Production chains
Draw the source, transport, storage, processing and output as one legible system.
CHAIN 02
Farmers
Plan automated collection as a named stage without inventing coverage or rates.
CHAIN 03
Assemblers
Structure inputs and outputs while recipes and timing stay evidence-gated.
CHAIN 04
Storage
Turn buffers into visible diagnostic points between production stages.
BUILDING CODEX
Sixty-plus ways to shape the factory
The Store confirms more than 60 constructible buildings and preserves items when a building is moved or deconstructed. The public registry waits for verified identities before creating entity pages.
- Verified roles: farmers, assemblers, storage.
- Layout guidance uses generic functional zones.
- No empty building pages and no guessed capacities.
PIPE TOPOLOGY
Design the network before chasing capacity
Official copy confirms that pipes link machines. The topology planner finds disconnected machines and dead ends without inventing direction or throughput.
BIOME FIELD DESK
Map the confirmed world before it expands
The demo fully exposes The Woods and previews Mountains. Later areas remain unpublished until they have a verified identity and useful decision data.
TECHNOLOGY ARC
Primitive tools. Bronze. Industry. The future.
The named eras frame a dramatic progression, while exact unlock graphs wait for current-build verification.
FIVE SIDE SYSTEMS
Minigames feed discoveries back into the factory
Each minigame has its own items, upgrades and progression. Dark Thicket is the only named slot in the current launch registry.
OPTIONAL MYSTERY
The Lighthouse waits beyond the factory.
Official sources confirm a mystery, secret areas and four endings. Requirements and locations stay closed until repeatable release-build evidence supports them.
CURRENT BUILD
A real issue desk, not a rumor wall
Community posts surface symptoms worth monitoring. They do not become global bugs without stronger evidence.
Controller navigation gaps
COMMUNITY-REPORTEDCachyOS demo launch report
MONITORINGInvert mouse request
MONITORINGSimple Pipes confusion
COMMUNITY-REPORTEDRECENTLY VERIFIED
Every claim carries a clock
The source gate records what changed, where it came from, and which pages need another look.
| Checked | Signal | Source | State |
|---|---|---|---|
| Sep 4 | Store remains prerelease; Demo available | Official Steam Store | PRE-RELEASE |
| Sep 4 | Sep 18 at 15:00 UTC target | Official Steam News | PATCH-SENSITIVE |
| Sep 4 | First commercial game; Amar is current studio | Studio Ashty | VERIFIED |
| Sep 4 | Four community support signals | Steam Community | MONITORING |
OFFICIAL GALLERY
Factories beneath a strange sky
Locally optimized imagery from the official Steam gallery and Studio Ashty, used as contextual evidence—not decoration detached from the guide.
FIELD QUESTIONS
What to know before launch
Clear answers, visible uncertainty, and a source link when the current state matters.
Is Nightwater released?
Not at the Sep 4, 2026 source check. Steam lists Sep 18, 2026, and official news gives an expected 15:00 UTC unlock. The site remains PRE-RELEASE · DEMO LIVE until Steam confirms the game is actually available.
What is included in the Nightwater demo?
Official sources describe the full first biome, The Woods; the full first minigame, Dark Thicket; and a preview of Mountains. They estimate about one hour to the demo ending or around four hours for deeper exploration.
Does this wiki publish recipes and milestone numbers?
Only when a value has reliable evidence. Unknown names, rates, thresholds, capacities, recipes and hidden requirements are shown as Not verified yet rather than guessed.
Are the planning tools official calculators?
No. They are independent local planning aids built around verified systems and user-entered observations. They do not simulate hidden game rules.
Will demo information be treated as release-build data?
No. Demo-derived claims move to Recheck Needed until they are verified in the full release build.