How Conduit works
The current public localization string reads as a triggered effect: when Conduit activates, it activates up to a set number of other buildings within range. Two details matter. First, it targets other buildings, not itself. Second, the string describes another activation; it does not say that Conduit copies a score, extends adjacency or changes a building's Guild.
How to place Conduit
- Choose the effects worth repeating. Read the candidate buildings before committing Conduit. A second activation is only useful when the target's own trigger advances your score, economy or removal plan.
- Use the live range preview. The public string contains unresolved variables for both target count and range. Do not plan around a radius copied from an old run or another site.
- Avoid low-value targets. If more buildings are in range than Conduit can trigger, target selection may matter. The public string does not explain whether selection is random, ordered or player-controlled.
- Confirm the trigger that starts Conduit. The extracted description explains the output, not the event that activates Conduit. Read the first line of the card in your current build.
What Conduit does not prove
A Google summary currently describes Conduit like an adjacency or range extender. That wording is not supported by the public game string we could inspect. Conduit may be part of a larger range strategy, but its documented effect is to trigger buildings already in range.
Why the exact number is missing here
The community localization archive exposes placeholders named ActivationCount and InRange instead of resolved values. Those values may be supplied by the live card, upgrades or run state. This page leaves them open instead of turning a placeholder into a fake number.
