Most factory management games force you to solve logistics through endless mazes of conveyor belts and splitters. In City From Naught's post-apocalyptic simulator, physical belts disappear entirely, leaving you to orchestrate an entire automated workforce through plain-language text commands. Mastering Brave New Wonders conditional logic is the single most critical breakthrough you will make to keep your floating outposts running smoothly. Without a solid command structure, your autonomous haulers will stall, idle with full inventories, or cause catastrophic production bottlenecks. By understanding how Brave New Wonders conditional logic transforms written sentences into reactive state machines, you can automate intricate production lines across the Archipelago with surgical precision.
This comprehensive guide breaks down the core architecture of the game's prompt interpreter, explores how building signals communicate resource states, and provides solutions for complex logistical puzzles like the Sky Pillar.
How Conditional Logic and the AI State Machine Operate
At its foundation, the game replaces physical belts with autonomous robots known as automatons. Instead of balancing conveyor belt ratios or placing mechanical sorters, you direct miner and mover units using natural language instructions. Behind the scenes, the game features a dedicated AI language model developed specifically to parse plain text and compile it into a visual finite state machine.
When you open the behavior editor and input a command, the parser does not execute code blindly. Instead, it generates a transparent behavior graph where every node represents an action—such as moving to a facility, collecting materials, or depositing cargo—and every connector represents a conditional transition. You can inspect this graph in real time, manually tweak individual nodes, add branches, or completely rewrite conditions if the automaton misunderstands your intent.
While the developers emphasize that no coding knowledge is required, writing effective Brave New Wonders conditional logic still demands an understanding of conditional flow. The AI parser understands spatial journeys from location A to B, but it cannot process fuzzy instructions such as roaming around an area or tracking persistent mathematical variables in memory. Complexity is instead offloaded to the interaction between robots and the signals broadcast by base facilities.
Building Signal Networks: Turning Factory States into Triggers
As your base expands beyond basic single-item hauling, relying on independent delivery loops creates massive deadlocks. For instance, assigning one mover to ferry iron plates and another to carry refined crystals to a single smelter often leads to full inputs of one item while the other runs dry. Full signal automation, which unlocks roughly three tiers deep into the technology tree, resolves this problem by allowing buildings to announce their operational needs.
Production facilities, warehouses, and hazard sensors can broadcast colored signals based on user-defined storage thresholds or physical conditions. When you link automaton behavior to these colors, a single mover can manage multiple supply chains dynamically, prioritizing whichever resource is currently depleted.
| Feature | Conventional Factory Games | Brave New Wonders |
|---|---|---|
| Material Transit | Fixed conveyor belts, underground belts, splitters | Autonomous flying/ground automatons |
| Routing Logic | Physical line balancers and circuit network wires | Plain-language prompts compiled into state graphs |
| Building Feedback | Binary enable/disable toggles via wire circuits | Multi-color signal broadcasts based on threshold rules |
| Expansion Method | Laying parallel tracks and duplicating physical belts | Blueprints that preserve saved automaton instructions |
| Failure States | Physical belt saturation or power brownouts | Logic stalls, route hazards, and unhandled signal states |
To construct a responsive logistics loop, configure your consuming facility to broadcast distinct colors based on remaining inventory. For example, instruct a smelter to emit a red signal when iron plate storage drops below five, a blue signal when refined crystals fall below five, and no signal when adequate supplies are present. From there, you can instruct a single mover automaton to check the smelter: fetch iron plates on red, collect refined crystals on blue, and enter a standby state whenever no signal is emitted.
Advanced Scenarios: The Sky Pillar and Continent Hazards
The true test of your command architecture arrives during Wonder expeditions and continental exploration. When investigating the Sky Pillar on the starting Americas continent, players encounter a delicate atmospheric regulation puzzle. The platform requires keeping its internal temperature strictly between 25°C and 70°C for 60 consecutive seconds to stabilize the ancient structure.
In this trial, delivering coal raises the chamber temperature by 10°C, while inserting thermal plates lowers it by 20°C. Attempting to manage this manually or using naive boundary triggers will fail. Because gas eruptions cause abrupt temperature spikes, waiting until the temperature hits the lower bound of 25°C or the upper bound of 70°C means the system will breach safety tolerances before a mover completes its journey.
According to community Let's Play walkthroughs, the most reliable setup involves establishing tighter safety buffers. By configuring the storage monitor to broadcast a red signal when temperatures dip below 29°C (demanding coal) and a green signal when temperatures rise above 45°C (demanding thermal plates), your automatons have sufficient transit time to counteract sudden thermal swings before the core fails.
Beyond the Americas, environmental hazards demand even tighter integration of Brave New Wonders conditional logic:
- Africa's Spoilage Deadlines: Agricultural greenhouses yield perishable crops governed by strict decay timers. Automaton delivery scripts must monitor greenhouse output thresholds and moisture signals simultaneously to haul crops to storage before they rot.
- Asia's Volcanic Flows: Active eruptions routinely destroy automatons and sever supply pathways. Players must wire emergency retreat logic to hazard flags, forcing mining bots to abandon lava zones the moment seismic warning signals trip.
- Europe's Power Crisis: Sub-zero temperatures severely restrict basic power generation around the buried Large Hadron Collider, requiring pulse-based delivery routines that synchronize fuel inputs with sporadic power draws.
Troubleshooting Syntax Bugs, Variables, and Logic Limits
While the natural language parser is flexible, players on the official Steam discussion forums have documented specific syntax hurdles and structural limitations that can derail automated routines.
A common issue reported in player findings involves variable naming conflicts within custom prompts. When referencing generic categories, using variable tags like {ItemType} can collide with the engine's internal data structures. If the interpreter confuses a temporary variable with a global object definition, the automaton may continuously pick up the first assigned item (such as metal plates) even when a signal condition specifies an alternate resource (like refined crystals). Community members recommend using distinct, custom parameter names like {itemA} and {itemB}, or typing exact in-game terms directly into the prompt without curly brackets.
Another recurring issue involves strict vocabulary matching. Omitting specific prefixes—such as typing "crystal" instead of the exact recipe name "refined crystal"—can cause the state machine to generate incomplete action nodes. Furthermore, buildings occasionally experience a split-second gap between signal transitions where no color is emitted. If your automaton script lacks a designated fallback or idle state for unhandled signals, the unit may branch into a false state and deliver the incorrect cargo.
It is equally important to understand what the system cannot do. Players frequently attempt to write looping prompts such as "deliver coal five times, then deliver iron once." As documented in Steam community discussions, the engine does not support internal mathematical counters, dynamic arrays, or arbitrary state loops within a single mover. If you require uneven ratios (such as two parts coal to one part ore), you must balance the line by using multi-building splitters or by letting output building signals dictate deliveries based on consumption deficits.
For players building complex logistical networks, checking the latest patch notes on the Brave New Wonders Steam store page provides useful updates on recently expanded condition operators like greater-than and equal-to symbols.
Best Practices for Reliable Automaton Prompts
Building a flawless automated production chain requires structuring your written commands to prevent pathing freezes and deadlocks. Follow these proven implementation steps when drafting custom instructions:
- Assign Exact Resource Names: Always reference items by their complete in-game catalog names rather than generic shorthand to ensure the parser binds the correct item ID.
- Define Unambiguous Fallback Conditions: Never end an instruction on an unhandled state. If a building emits neither red nor blue, explicitly instruct the automaton to wait at an idle marker or stand by.
- Implement Transit Time Buffers: Factor in robot travel duration when setting sensor boundaries. In high-stakes puzzles like temperature regulators or spoilage lines, set signal thresholds several units inside the failure margin.
- Isolate Overly Complex Routes: If a single mover is tasked with managing three or more conditional drop-offs, consider splitting the duties across two simpler automatons to avoid lengthy state validation stalls.
- Inspect the Behavior Graph Before Confirmation: Always review the compiled visual state machine in the inspector. Confirm that outgoing conditional edges match your intended triggers before applying the behavior to your fleet.
Frequently Asked Questions
Why does my automaton deliver the wrong item when the signal changes?
This usually stems from a variable naming collision or an unhandled neutral signal state. If your prompt uses {ItemType} as a custom variable, community reports show that the parser may override secondary inputs with the first selected item. Replace generic tags with distinct names like {item1} and {item2}, ensure you are using exact names like "refined crystal", and verify that an intermediate "no signal" tick is not defaulting your automaton to an unintended branch.
Can I write counting conditions like repeating an action five times?
No. Brave New Wonders conditional logic does not currently support internal iteration counters or dynamic numeric arrays. The AI model will fail to compile prompts that instruct an automaton to loop an action a specific number of times before switching tasks. To achieve uneven delivery ratios, rely on building inventory signals that trigger deliveries only when specific material thresholds run low.
How do I bypass the AI text prompt system entirely?
If you prefer not to use natural language prompts, you can build and modify your automation routines manually. The game includes a visual node-based editor that displays every action and conditional transition. You can add action blocks, link conditional edges, and set building targets directly through the graphical user interface without typing a single prompt.
At what point in progression do signal commands become available?
While basic A-to-B transport presets and single-item movement commands are accessible early in the Americas starting region, full building-to-building signal automation and advanced Brave New Wonders conditional logic unlock approximately three tiers into the campaign technology tree after analyzing relics recovered from old-world ruins.