- Plan B: Terraform farm layout works best when farms connect to a shared silo network.
- Gateway silos provide seeds and collect harvest for the entire connected farm system.
- Depots should generally be placed around silos, not directly beside individual farms.
- Large farm zones are expected because food production competes with other land uses.
- Annual harvest data helps you expand production without relying on guesswork.
Plan B: Terraform Farm Layout Basics
A strong Plan B: Terraform farm layout separates field production from cargo handling. Farms create harvest through the farm network, while silos receive seeds and release harvest containers. Depots then move those containers into the wider transport system.
The most important design rule is to treat farms and silos as one connected production network. A farm does not need a direct road or rail connection to a depot. Instead, it needs a valid link to a silo network. The silo acts as the network’s gateway for incoming seeds and outgoing harvest.
Video Highlights:
- Multiple supply centers reduce delivery distance around a growing city.
- Shorter routes make train and depot traffic easier to manage.
- Strategic depots can prevent one central logistics point from becoming overloaded.
- Landmark towers make large production zones easier to locate later.
| Building | Main function | Best placement |
|---|---|---|
| Farm | Produces harvest from field seeds | Inside a connected farm zone |
| Silo | Supplies seeds and gathers harvest | At the edge or center of the farm network |
| Depot | Loads and unloads containers | Around the silo gateway |
| Landmark Tower | Marks important production areas | Near farms, rail hubs, and industrial zones |
A useful starting pattern is one gateway silo with several farms linked around it. Add depots close to that silo so containers can enter and leave the farm network without forcing transport vehicles to cross the entire agricultural area.
Build the logistics hub around the silo, not around each farm. Farms pass resources through the connected network, while the silo provides the practical loading and unloading point.
Farm Zone
- Broad field coverage
- Connected to the silo network
- Expanded as city demand rises
Silo Gateway
- Receives field seeds
- Collects harvest
- Connects agriculture to transport
Depot Hub
- Handles containers
- Supports nearby rail routes
- Keeps logistics concentrated
How Farms, Silos, and Depots Connect
The farm system becomes easier to manage once each building’s responsibility is clear. Silos consume containers of Field Seeds and push them into the silo network. Farms draw from that network and return Harvest through the same connected structure. The silo then makes those harvest containers available to nearby depots.
This means a farm can be several links away from the gateway silo. A chain of connected farms can pass resources through the network until the cargo reaches a linked silo. The arrangement is more flexible than a one-silo-per-farm design, but the network still needs a reliable gateway.
| Network element | Input | Output | Layout implication |
|---|---|---|---|
| Gateway silo | Field Seeds | Harvest containers | Needs access to depots |
| Farm | Field Seeds through network | Harvest | Prioritize connection over depot access |
| Connected farm chain | Seeds from linked network | Harvest toward linked silo | Useful for expanding fields |
| Depot cluster | Harvest or seeds | Transport containers | Place near the silo |
Follow this sequence when building a new agricultural district:
Choose the Agricultural Zone
Select a broad area with enough room for expansion. Farms can occupy a surprisingly large surface area compared with the city they support, so avoid placing the first fields in a narrow corridor.
Place the Gateway Silo
Build at least one silo where transport can reach it efficiently. This silo should become the visible front of the farm network rather than being hidden deep inside the fields.
Add Initial Farms
Place several farms within practical linking distance of the silo or another connected farm. Confirm that the network links appear before adding large numbers of fields.
Build Depots Around the Silo
Add depots near the gateway silo. Farms generally do not need their own depot because the silo handles network access for seeds and harvest.
Connect the Transport Route
Link the depot area to the city or industrial network. Keep the first route short, then add more depots or additional silos when the district grows.
A common mistake is placing a depot beside every farm. This adds visual clutter without addressing the actual network structure. A better approach is to make farms dense enough to use productive land while keeping cargo handling concentrated near one or more silos.
A farm that is not connected to a silo network cannot participate properly in seed delivery or harvest collection. Check the visible network links before expanding the field zone.
Three Farm Layouts for Different City Stages
There is no single ideal agricultural shape for every colony. The best design depends on city scale, transport distance, available fertile land, and how often you expect to expand. Start compactly, but reserve space for a wider farm footprint.
| Layout | Best use | Strength | Main limitation |
|---|---|---|---|
| Compact hub | Early city growth | Easy to inspect and supply | Limited expansion room |
| Linear farm belt | Long, narrow land area | Simple staged expansion | Longer network edge |
| Distributed districts | Large or separated cities | Shorter local routes | Requires more silos and planning |
Compact Hub Layout
The compact hub places a gateway silo near the center or front of a dense farm group. Depots sit directly around the silo, and farms spread outward in a broad ring or block.
This is the easiest arrangement to understand during early development. It also makes seed and harvest movement easy to inspect because the entire production zone has one obvious logistics center. Leave a clear side for future farms rather than filling every usable tile immediately.
Linear Farm Belt
A linear farm belt works well when fertile land follows a long strip or when a city occupies one side of the available terrain. Put the gateway silo at the transport-facing end, then extend farms in a connected chain.
This design keeps the main cargo interface close to the city while allowing the agricultural zone to grow away from urban construction. As the belt becomes longer, watch the network and transport flow. A second silo or a second depot cluster may be useful if the original gateway becomes too distant from the newest fields.
Distributed Farm Districts
Large colonies may benefit from multiple farm districts instead of one enormous agricultural block. Each district can use its own silo and nearby depots, with the districts connected through the wider transport network.
This approach follows the same principle used for other production chains: multiple supply centers can shorten routes and prevent one location from handling every container on the planet. It costs more planning, but it gives you better control over city-specific food demand.
Early Expansion
Use one silo, nearby depots, and a compact farm block. Prioritize clarity over maximum land coverage.
Midgame Growth
Extend farms in a belt and keep the transport-facing silo easy to reach.
Large Cities
Split production into districts when routes become difficult to inspect or manage.
A layout is scalable when you can add farms without rebuilding the original transport hub. Leave expansion space beside the first district and reserve a route for another silo or depot cluster.
Harvest, Seeds, and Food Demand
Farm expansion should be based on observed output rather than a fixed farm count. The available discussion does not establish one universal number of farms for one city. City size, production efficiency, food demand, and the current balance of the game can all affect the result.
The most useful practical measurement is the harvest amount shown for each farm over the previous year. Check several farms instead of judging the entire district from one building. If harvest remains below demand, add farms or improve the network before assuming that transport is the only problem.
| Production question | What to check | Recommended response |
|---|---|---|
| Is the city short on food? | City demand and annual farm harvest | Add farms and verify seed delivery |
| Are farms producing? | Individual farm harvest history | Compare several farms |
| Are seeds reaching the network? | Gateway silo input and links | Inspect silo connections and depots |
| Is transport slow? | Depot distance and route congestion | Add a nearby depot or district hub |
| Is land running out? | Available fertile area | Plan a second agricultural district |
Field Seeds also require careful handling. The documented conversion is one Harvest into one Seed, while a 100% efficient hexagon can produce three Harvest from one Seed. This makes seed recycling potentially valuable, but it does not remove the need for a large farm area. Farms are designed to occupy substantial land, and agricultural zones may compete with forests or other terrain uses.
“Quality food” also depends on more than farm harvest alone. It requires classic food plus farm harvest, so a farm district should be treated as one part of the broader food chain rather than the only food source.
Check each farm’s previous-year harvest before expanding. This gives you a better production signal than counting farms or assuming that every field performs identically.
Farm District Checklist:
- Place a gateway silo with a clear transport connection
- Confirm every farm belongs to the silo network
- Build depots around the silo instead of every farm
- Check annual harvest on multiple farms
- Reserve land for additional farms or a second district
Layout Optimization and Troubleshooting
The most efficient layout is not always the densest layout. A farm district should be easy to read, easy to expand, and easy to reconnect if the transport network changes. Use landmark towers to label agricultural areas, rail construction zones, and other major production sites. Clear markers become increasingly valuable as cities and industrial systems spread across the planet.
Short delivery paths also matter outside the farm network. When a city relies on a single overloaded supply center, every material may compete for the same routes. Multiple strategically placed supply centers and depots can reduce the distance between production and consumption. Apply the same logic to farms by keeping the silo gateway close to the transport route while allowing fields to spread outward.
| Symptom | Likely cause | Fix |
|---|---|---|
| Farms show no useful output | Missing seed supply or broken network link | Inspect the silo and farm connections |
| Harvest exists but city remains short | Insufficient farm area or transport delay | Add farms and shorten the route |
| Depots seem inactive near farms | Depot is not connected through a silo | Move depot coverage toward the silo |
| One hub handles too much traffic | Single-center bottleneck | Add a second silo or supply center |
| District is hard to find later | Poor visual organization | Add landmark towers and clear zones |
Use this troubleshooting order:
- Select the farm and inspect its network connection.
- Select the gateway silo and confirm it receives Field Seeds.
- Check whether harvest reaches the silo network.
- Inspect depot placement and nearby transport routes.
- Review annual harvest before adding more infrastructure.
- Expand the farm area only after the network is functioning.
Do not solve every shortage by immediately adding more farms. A disconnected farm district can become larger without becoming more productive. Likewise, adding depots far from the silo may not improve the farm network if those depots cannot load or unload the relevant containers.
Use separate zones for fields, silo access, depots, and outbound transport. A layout that is easy to inspect usually makes supply problems easier to solve.
The best long-term pattern is modular: one agricultural district, one clear gateway, a nearby depot cluster, and open land for expansion. When that module reaches its practical limit, repeat the pattern instead of stretching every route across the planet.
Farm Layout FAQ
Q: How many farms does one city need in Plan B: Terraform?
There is no universal farm count. City size and food demand vary, and farms can require a large land area. Check each farm’s annual harvest, compare it with city demand, and expand the district gradually.
Q: Does every farm need its own depot?
No. Farms connect to the silo network, while depots load and unload that network through a silo. Place depots around the gateway silo or another dedicated silo hub.
Q: Can farms connect through other farms?
Yes. A farm can pass resources through connected farms until the network reaches a linked silo. Direct farm-to-silo placement is not required for every building.
Q: What is the best farm layout for a growing city?
Start with a compact silo hub, nearby depots, and an expandable farm block. For larger cities, use a linear farm belt or multiple districts with separate silo gateways to keep routes manageable.
Start with one clear silo hub, verify the network, measure annual harvest, and expand farms in modules. This approach keeps food production readable while leaving room for larger cities and additional districts.