Traditional factory builders force players to untangle endless webs of conveyor belts and splitters. In City From Naught's post-apocalyptic simulation, you manage a mechanical workforce using plain-text instructions. Mastering Brave New Wonders robot programming is the single most important skill for scaling your airborne industrial empire across floating islands. Without conveyor belts, your supply lines succeed or fail based on how clearly you instruct your units. Understanding Brave New Wonders robot programming lets you turn chaotic bottlenecks into elegant, self-regulating logistics loops without writing a single line of actual code.
Whether you are configuring your first ore hauler or coordinating multi-tier factories across dangerous volcanic terrain, this guide covers everything you need to command your automatons effectively.
Core Mechanics: Compiling Natural Language into State Graphs
The core design philosophy of the game replaces physical belts with autonomous ground units called automatons. Instead of laying down physical tracks, you open an automaton's behavior editor and type out instructions the same way you would explain a job to a human worker. The underlying system uses a specialized natural language processing model that parses your text and automatically generates a visual behavior graph.
This generated behavior graph acts as a visual state machine. Every instruction breaks down into distinct elements:
- Action Nodes: Individual physical actions carried out by the machine, such as navigating to a mine, picking up refined metal, or depositing goods into a warehouse.
- Transition Conditions: Triggers that determine when an automaton shifts from one action to the next, including full cargo inventories, elapsed timers, or colored visual signals broadcast by nearby factories.
- Fallback Branches: Alternative routes and standby states executed when a target facility is unreachable, full, or lacking requested materials.
You are never forced to accept an imperfect AI interpretation. Once the system generates the behavior graph, you can inspect it node by node. Players have full freedom to manually drag transitions, modify trigger conditions, insert extra actions, or rephrase the original sentence. If you prefer total manual control, the developers allow you to bypass the text prompt system entirely and assemble your state machines by hand.
How to Formulate Prompts: Syntax, Brackets, and Variables
The game accepts plain language in any supported language, but achieving consistent results requires clear phrasing. The behavior editor translates everyday instructions into logical parameters, and following structured patterns prevents misunderstandings during compilation.
- Use Curly Brackets for Target Assignment: Placing brackets around facility roles, such as {storage} or {smelter}, tells the compiler to treat that term as an interactive target variable. When you assign the completed behavior to an automaton, the interface prompts you to click and assign specific structures in the game world.
- Match Exact In-Game Nomenclature: Avoid generic terminology. Player testing shows that requesting a general resource like crystal often fails to trigger proper pickup behaviors, whereas specifying the exact database item name, such as Refined Crystal or Metal Plate, compiles without issue.
- Declare Separate Variable Names for Dual Deliveries: Community reports highlight that naming two variables with generic labels can confuse the parser. For example, assigning two different items under identical variable classifications can cause an automaton to loop the first item repeatedly. Players solved this by declaring distinct labels, such as item1 and item2, ensuring independent delivery states.
- Define Idle and Fallback Conditions: Always tell the machine what to do when a condition is not met. Appending instructions such as "otherwise, stand by" prevents automatons from wandering aimlessly or locking up when resource thresholds are unmet.
The table below outlines common phrasing patterns and how the compiler processes them:
| Desired Behavior | Recommended Natural Language Prompt | Generated Behavior Logic |
|---|---|---|
| Simple Resource Route | Move to {mine}, collect Iron Ore until full, then deliver Iron Ore to {warehouse}. | Loops a two-point transit between assigned nodes based on cargo capacity. |
| Conditional Warehouse Feed | If {factory} storage drops below 5, fetch Coal from {storage} and deposit into {factory}. | Checks internal storage thresholds before triggering transit tasks. |
| Color Signal Response | When {signalSource} is Red, collect Iron Plate from {warehouse} and deposit to {signalSource}. | Listens for active broadcast frequencies to select delivery tasks. |
| Multi-Resource Priority | If {smelter} emits Red, deliver Iron Plate; if {smelter} emits Blue, deliver Refined Crystal; else wait. | Branches state transitions based on multiple broadcasting color states. |
Advanced Signal Automation and Reactive Supply Chains
Simple point-to-point delivery loops work well during the early campaign on the Americas island, but complex recipes quickly overwhelm uncoordinated haulers. For example, a smelter requiring two separate resources can easily stall if two unlinked automatons flood the input buffers unevenly. Setting up a reactive signal network solves this bottleneck completely.
Buildings and production facilities can broadcast distinct colored signals—such as red, blue, or green—based on their live inventory levels. Rather than assigning multiple haulers on rigid timers, you can configure your factory to communicate its immediate shortages:
- Access the destination factory or smelter interface and open its signal settings.
- Set the facility to broadcast a red signal when its internal iron plate storage drops below five units.
- Set the same facility to broadcast a blue signal when crystal shard storage drops below five units.
- Instruct the facility to broadcast no signal when both thresholds are satisfied.
- Assign a single mover automaton the prompt to check the smelter: fetch iron plates on red, fetch crystal shards on blue, and remain on standby when no signal is detected.
This reactive loop allows a single worker unit to balance uneven deliveries dynamically, freeing up additional automatons for defense logistics or construction projects. For players interested in checking out the factory building mechanics and community updates firsthand, you can view the official game on the Brave New Wonders Steam store page.
Known Compiler Limitations, Bugs, and Community Workarounds
While the natural language system handles direct instructions smoothly, complex automation setups push against early version constraints. Community feedback from Steam forums and playtesters reveals several recurring technical quirks that require specific workarounds.
- Counting Loops: The current parser cannot interpret numerical loop counters. Prompts asking a bot to repeat a task five times before switching to a second item will fail to compile. To handle recipes with uneven ratios (such as two parts item A and one part item B), players recommend using factory signal thresholds or setting up splitters and multi-mover fleets rather than trying to write sequential count logic.
- Prompt Length Limits: Community reports indicate that entering lengthy, paragraph-sized prompts approaching 50 lines causes the compiler to generate tangled, looping graphs with broken true/false transitions. Keep text prompts concise, ideally under three sentences per role.
- Signal State Intermissions: Players have reported instances where rapid signal switching causes an automaton to evaluate a condition while a facility momentarily emits no signal between cycles. Adding explicit branches for each color rather than relying solely on a simple true/false check ensures stable state transitions.
- Storage Timers for Delivery Fallbacks: Because direct percentage-based capacity queries are limited, experienced players create timed fallback loops. If an automaton cannot deposit materials into a primary warehouse within two seconds, the logic diverts the unit to an overflow storage facility.
Island Biome Adaptations across the Archipelago
As you expand your airborne operations beyond the temperate Americas, Brave New Wonders robot programming must adapt to hostile environmental hazards across distinct floating landmasses:
- Europe (The Frozen Archive): Power generation functions poorly on the frozen surface above the ancient Large Hadron Collider. Automaton routines must prioritize energy routing, requiring strict conditional instructions to shut down non-essential logistics when battery reserves dip.
- Africa (The Solar Oasis): Agricultural output is high, but perishable crops introduce spoilage countdown timers. Hauler routines cannot rely on passive storage queues; you must program tightly timed delivery cycles responding to greenhouse moisture and temperature sensors to prevent crops from rotting in transit.
- Asia (The Volcanic Industrial Center): Erupting lava flows destroy automatons within seconds, and operating near thermal vents degrades chassis durability. Survival demands hazard-aware behaviors, combining external warning flags with automated detour orders to pull worker fleets back to safe ground during active seismic pulses.
Frequently Asked Questions
Can you play the game without using the AI text prompt system?
Yes. The natural language compiler is entirely optional. Players who prefer traditional visual programming can bypass the text interface and construct behavior graphs manually by connecting action nodes and conditional transitions within the inspector.
What is the maximum length for a robot programming command?
While the game does not publish a rigid character ceiling, community testing shows prompts exceeding several sentences or reaching 50 lines struggle to compile accurately. It is far more reliable to write concise, multi-branch instructions focused on one or two active signals.
Why is my automaton ignoring assigned warehouse deliveries?
This usually occurs when prompt terms do not match in-game names or when variable targeting is missing. Ensure items are referred to by their exact labels, such as Refined Crystal rather than crystal, and place brackets around destination targets so the inspector allows you to link specific structures.
Does Brave New Wonders robot programming support loops that repeat a set number of times?
No. The compiler does not currently support numerical counters or finite while-loops. To supply uneven recipes, configure production structures to emit color signals based on ingredient shortages, letting the machines react to real-time warehouse needs instead of manual loop counts.