Brave New Wonders Updates Hub

The Updates Hub tracks what matters after Brave New Wonders left demo territory and shipped version 1.0 on Steam (app 2403830) around 20–21 September 2026. Developed by City From Naught Inc. with publishing support involving LoongGate, the game is a single-player factory automation title: no conveyor belts, automatons driven by presets and plain-text commands, island travel via the airship Wonder, and combat against old machines.

Featured: Launch 1.0 Notes

Start with the full article — Launch 1.0 Notes — for the release window, City From Naught + LoongGate credits, the 15% discount window cited through roughly 4–5 October, demo/playtest save carryover versus fresh-start advice, four biomes, text-command identity, 25 Steam achievements, and what Factorio-like veterans should relearn. This hub summarises the same launch spine and points you into guides; the child page is the deep read.

After that article, dive into Getting Started, Players, Achievements, and the Tier List Hub.

1.0 launch snapshot

At launch, commanders should expect the full Americas-to-archipelago fantasy promised through demos and trailers: build factories, deploy Miners and Movers, author behaviours, defend with turrets and dynamite, unlock the Wonder, and push toward Europe, Asia, and Africa. Official store framing emphasises intelligent automatons, blueprint copy/paste that preserves behaviours, and signal-aware logistics. There is no multiplayer mode and no codes pipeline to refresh — progress is save-based and mechanical.

Steam listed 25 achievements at launch. A 15% launch discount ran through early October (store/community citations through ~4–5 October; always re-check the storefront for the live price after that window). System expectations remain demanding for busy yards; keep System Requirements handy if you import a heavy demo save into 1.0.

What changed from the demo (player-facing)

Exact patch changelogs evolve with studio posts, but commanders moving from demo to 1.0 should mentally reset on these themes:

Scope and islands

The demo taught the fantasy on a constrained slice. 1.0 is built around the wider archipelago loop: stabilise Americas, bring the Wonder online, then treat other continents as escalation — new biomes, resources, and logistical stretch goals. If your demo muscle memory assumes “one island forever,” read Islands and Wonders before you overfit a starter layout that cannot travel.

Behaviours and quality-of-life

Demo updates already introduced quality-of-life such as custom key bindings. 1.0 continues the behaviour-editor fantasy: presets for simple jobs, plain-text commands for custom logic, visual graphs you can inspect, and optional manual graph assembly. If a demo prompt still works wording-wise, still re-validate destinations after buildings move. See Text Commands, Tools, and Controls.

Combat and defense expectations

Trailers and previews consistently showed that expansion is contested. Old machines, turret lines, dynamite clearance, and relic finds are part of pacing — not optional cosmetics. Players who treated the demo as a peaceful belt-less Factorio cousin should promote ammo logistics earlier; Defense and the Tier List Hub explain timing so you do not brick a pretty factory.

Blueprints as the scaling story

Launch messaging leans hard on blueprint duplicate speed with behaviours intact. That feature defines midgame tempo more than any single building unlock. Rehearse one perfect cell in 1.0 even if you “already knew” the demo version — pasted mistakes scale faster in the full game. For deeper launch narrative, return to Launch 1.0 Notes.

Demo save carryover

Demo saves can carry into the full game. That is a gift for continuity and a footgun for performance. An imported base may already contain more automatons, partial Wonder progress, or messy graphs than a clean tutorial expects. The developers still recommend a fresh start for the best 1.0 experience — details and a carryover ritual live on Launch 1.0 Notes.

Quick ritual if you import anyway:

1. Backup the save (Steam cloud / local copy habit).
2. Launch 1.0, walk the yard, and idle-watch every behaviour for one cycle.
3. Delete or rewrite loops that reference missing demo-only assumptions.
4. Confirm warehouse buffers before you paste blueprints.
5. Re-bind keys if your custom layout reset — Controls.
6. Only then resume Wonder unlock grinding.

If frames tank immediately, you did not “get worse at the game”; you imported density onto hardware near minimum specs.

Launch week priorities (post-patch mindset)

Even without a twenty-page official patch bible pinned here, the correct 1.0 opening remains stable:

1. Prove Miner → warehouse flow.
2. Add Movers as belts.
3. Learn transfers and the editor.
4. Signal-gate ammo before aggressive ruins pushes.
5. Blueprint the truthful cell.
6. Unlock and fuel the Wonder responsibly.

Details live across Automation, Tools, and Getting Started. For a critical overview of the fantasy, read the Wiki review page. For completionist habits without fake trophy names, see Achievements.

How this hub will grow

Dated child pages start with Launch 1.0 Notes. Future entries should cover major balance or QoL drops the same way. Until more patches ship, treat this hub plus that launch article as the anchor: discount window, achievement count, carryover rules, and the demo→1.0 expectation shift. When you cite numbers elsewhere on the wiki (release status, multiplayer none, platforms), keep them aligned with content/facts.json and these pages.

Commander checklist after reading

• Open Launch 1.0 Notes once for the full narrative and trailer context.
• Recheck Steam price if you waited past early October.
• Confirm 25 achievements if you are hunting completion — Achievements.
• Relearn camera and transfer habits on Controls.
• Skim System Requirements before a blueprint binge.
• Replace demo-era priority guesses with the Tier List Hub.
• Keep a prompt library on Tools.

Brave New Wonders 1.0 is less “new genre” than “demo promise delivered at archipelago scale.” Update your plans the same way you update behaviours: inspect the graph, delete stale nodes, and only then automate the next continent.