Research Tree: Read Prerequisites, Queue, and Time

The research tree is easier to use when you stop reading it from left to right. Start with the capability that clears your present constraint, then trace its dependencies backward until you reach nodes you can act on now.

Backward-planning method

1. Name the capability. Examples: a government option, a production building, more reproduction capacity, or a weapon path.
2. Select the target node. Read its prerequisite edges and any policy or building dependency in the detail panel.
3. Trace to the nearest available node. Do not count an attractive side branch as progress unless it connects to the target.
4. Compare points and time. Use the displayed research rate, required points, and remaining time to align the unlock with your colony or expedition.
5. Queue deliberately. A queue prevents idle research; it does not correct a poor order.

One current readable node

The current tree screenshot shows [Blueprint] Reproductive Allocation Facility under Planetary Architecture / Base Building.

The final three values describe the state shown in that screen, not a universal rate or duration. Your workforce, balance version, and current progress can produce a different time.

Read prerequisite edges as commitments

A prerequisite is more than a research cost. It can require:

• an earlier research node;
• a policy at a civic building such as Victory Square;
• a physical building and the workers to operate it;
• materials and transport for construction;
• a colony condition that makes the new capability worthwhile.

That means the actual cost of a research target may span Policies and Laws, Jobs and Production, and Buildings and Layout.

Queue rules that preserve intent

Use a short queue with explicit roles:

1. Constraint clearer: the first node directly removes the present block.
2. Enabler: the second provides material, staffing, or policy support.
3. Option: the third opens a useful branch but is safe to delay.

Rebuild the queue when the colony changes. A newly discovered shortage or expedition reward can make the old order obsolete.

Common research traps

Chasing the visible endpoint

The exciting building at the end of a branch may need policy and production support you do not have. Trace the whole commitment before paying the first node.

Comparing only point cost

The smaller node can be slower to exploit if its building needs a new material chain. Compare time-to-capability, not only research points.

Filling the queue

A full queue looks efficient but reduces responsiveness. Keep it short enough to change after an expedition or citizen crisis.

Treating one screenshot as the whole tree

The current sample is useful for learning the interface and one exact dependency. It does not establish every node, connection, or cost in the game.

Research decision checklist

• What player task will this unlock complete?
• Which prerequisite is the true next action?
• Does a policy or physical building sit between research and use?
• What production and staffing will the result require?
• Will the node finish before or after the next planned expedition?
• Which queued node should move if the colony changes?

For the equipment side of progression, continue to Resources and Recipes or the Core Combination Planner.