Fontebrac does not pay you for painting a huge field. It pays when a Farmer Residence is assigned to the right crop, the harvest reaches a granary, and a crop-powered building can consume the exact inputs shown by the current client. If Farm Points are barely moving, trace that chain from the consumer backward before adding land.
This route was reviewed on August 23, 2026, with v1.0.4 as the newest named build. The two supplied farming references give a detailed Early Access crop order, but the Steam crop-input list explicitly labels itself “Not Updated for 1.0.” For that reason, this guide uses the old list to identify relationships—not permanent quantities. Read every recipe and capacity from the building panel in your current game before sizing fields.
Open Fontebrac only after Belvau can spare attention and labour
The supplied campaign captures open Fontebrac when Belvau advances from Village to Small Town. Check the world map and current objective because campaign gates can change. More important than the exact unlock is the state of the town you are leaving: Belvau should still be attracting families, its essential services should remain staffed, and its warehouse warnings should be understood.
Fontebrac is a second town with its own residents and happiness pressures, not a remote field painted for free. Opening it while Belvau is already short of workers creates two half-functioning systems. Before changing maps, record:
- which Belvau buildings are essential and who staffs them;
- whether average happiness is safely supporting new arrivals;
- which crop-powered building you intend to operate first;
- which research and Farm Point unlocks that first loop requires.
If you cannot name the first consumer, do not choose a crop yet. “Grow everything” spreads farmers, fields, granaries, and research across outputs that may have nowhere useful to go.
Build one auditable lane from residence to consumer
A working first lane has five owners:
- Farmer Residence: houses the farming family and exposes the crop assignment.
- Field: produces the crop selected for that residence.
- Granary: receives and transports crop output.
- Crop-powered building: consumes one crop or a recipe of several crops.
- Town services: keep the farmer family and supporting workers happy enough to continue operating.
Lay a readable road from the station to a compact residential-and-service block, then branch to the first farming lane. Place the Farmer Residence where its field has room to expand. Put the granary where the field and the intended consumer are both practical to serve. A granary beside a beautiful field but far from the building that needs the harvest turns transport into the hidden bottleneck.
Assign the crop inside the Farmer Residence or its associated farm control. Unlocking grapes in research does not automatically make every field grow grapes. After assignment, watch a full cycle: the field should show the correct crop, the granary should recognize stock, and the consumer should see its required input. Those are three separate checks.
Do not count Farmer families as spare shop workers
Farmer Residences exist to operate farmland. Plan ordinary residents for the granary, Research Center, market stalls, and crop-powered commerce where the client requires them. If the map looks populated but every service shows an empty labour slot, compare the resident classes instead of building another house blindly.
When ordinary labour is short, temporarily reduce research staffing before disabling food or granary transport. Research accelerates the next unlock; food and logistics keep the current loop alive.
Use the crop tiers as a dependency map
The readable Early Access sources agree on four crop groups. They are useful for planning which chains depend on which plants, even though their old quantities require a current-client readback.
| Historical farm tier | Crops identified in the supplied references | First planning question |
|---|---|---|
| Tier 1 | Grapes, Corn, Wheat | Can Winery or Bakery receive every input its live panel requests? |
| Tier 2 | Rose, Cotton, Beeswax | Is the Hattery chain supplied without starving the first food loop? |
| Tier 3 | Hops, Potato, Tomato, Lettuce | Can the Pub’s multi-crop recipe stay balanced? |
| Tier 4 | Pumpkin, Lavender, Medicinal Herbs | Which city-tier consumer justifies each crop? |
Start with the simplest complete consumer visible in your research tree. The supplied sources use grapes → Winery as the first single-crop loop, then corn + wheat → Bakery as the first paired-input loop. That sequence teaches two different failure patterns. A Winery can fail because its one crop is absent or cannot travel. A Bakery can have a full store of corn and still stop because wheat is missing.
Do not copy the old numeric recipe values into a field plan. Open the building, record every current input and quantity, then calculate field allocation from observed consumption. Version 1.0 added major campaign and tourism content, and the community input list itself warns that it was not updated. A live readback takes seconds and prevents an obsolete ratio from becoming the foundation of the town.
Granaries need zones, not one-per-field superstition
The supplied walkthrough repeatedly suggests placing a granary for each farmland. That is a safe beginner pattern, but it is not a reason to spam granaries. The actual question is whether the granary can move the crops produced in its zone to the consumers that need them with enough workers and a usable path.
Design a granary zone around a measurable job:
- a small Tier 1 zone serving grapes and the first Winery;
- a paired-crop zone whose corn and wheat both feed one Bakery;
- a multi-crop zone where Pub ingredients can be inspected separately;
- a late-crop reserve that feeds only the city buildings currently unlocked.
Keep unrelated crops in separate visual lanes even if they share a granary. Use road shape, field boundaries, or distinctive farm decoration so you can identify the crop without opening every residence. This is not cosmetic busywork: when a consumer lacks one ingredient, a readable lane tells you which residence, field, and granary to inspect.
Granary and warehouse failures are different
The granary owns crop movement. Warehouses support the broader shop and goods network. When a crop-powered building says an input is missing, begin at the crop lane and granary. When an ordinary shop cannot sell or a distant district lacks service support, inspect the warehouse network. Building one of each beside every shop hides which system was actually failing.
The official v1.0.4 patch corrected saved custom links for homes and shops that could revert after a load. If connections appear to change on an older client, update first, then test one link across a save-and-load before rebuilding the agricultural layout.
Farm Points come from a completed economy, not from acreage
The supplied farming guides describe Farm Points as the result of operating crop-powered commerce. That explains why a huge field can feel unproductive: growing a crop is not the same as using it in the chain that advances farming research.
Use a four-check Farm Point test:
- Confirm that the Farmer Residence is assigned to the intended crop.
- Wait until the granary shows that crop rather than an empty or unrelated store.
- Open the crop-powered building and verify every required input, worker, and connection.
- Observe whether the Farm Point readback changes after the building completes work.
If points do not change, do not add another field until you know which checkpoint failed. If the building is short one crop, fix that crop. If the granary is full but the consumer is empty, fix transport. If the consumer has inputs but no worker, fix labour. If all four pass and the counter still does not respond, record the client version and reproduce the cycle once before reporting it.
Keep one “control” crop chain unchanged while experimenting with a second. The stable lane proves that Farm Points and general logistics are still working. When only the new lane fails, the fault is local to its assignment, inputs, granary zone, worker, or consumer.
Scale multi-crop buildings from the scarcest input
Later consumers combine several crops. The old references associate the Hattery with the Tier 2 trio, the Pub with the four Tier 3 crops, and higher city buildings with combinations drawn from roses, grapes, hops, lavender, medicinal herbs, beeswax, tomato, potato, and pumpkin. Use those relationships to decide what must coexist, then take the quantities from the live building panel.
For each multi-crop consumer, make a current recipe card:
| Field on the card | What to record | Decision it supports |
|---|---|---|
| Client build | The version shown when the recipe was read | Prevents a patched value from silently becoming permanent |
| All inputs | Crop name and current required quantity | Identifies the missing member of a recipe |
| Stock before cycle | Granary amount for each input | Separates production shortage from transport shortage |
| Observed consumption | How much each input falls after one completed job | Shows which field needs more capacity |
| Observed wait | The first input that reaches zero or delays the next job | Names the scarcest input instead of guessing from field size |
Expand the field feeding that scarcest input, then watch another completed job. Do not enlarge all four fields together. One-at-a-time changes reveal whether the bottleneck moved; simultaneous expansion only proves that you spent more land.
Protect farmer happiness before increasing surface area
Farmer families still have needs and placement traits. The supplied references warn that weak farmer happiness can interrupt the availability of crops for commerce. Before increasing field surface or adding another Farmer Residence, inspect the current farmers’ food, decoration, services, and individual preference.
Keep homes and fields close enough to operate as a district, but leave room for services and decoration. Farm-themed decoration can help the area read clearly; it is not a replacement for a missing food, apparel, leisure, or Public Service category. Match the fix to the panel.
Some community trait notes describe Fontebrac-specific preferences such as bees, lavender, farm decoration, or crop-powered shops. Those notes predate 1.0, so use the family’s current tooltip and visible placement radius rather than reproducing old bonus percentages. The reliable action is to select the family, reveal the relevant radius, and move the home or matching feature until the live panel confirms improvement.
A crop shortage has five distinct signatures
| What you see | Likely checkpoint | Next action |
|---|---|---|
| Field shows the wrong crop | Farmer Residence assignment | Select the residence and set the intended unlocked crop |
| Correct crop exists but granary stays empty | Path, granary zone, labour, or farmer operation | Inspect the route and worker state; then check farmer happiness |
| Granary has crop but consumer does not | Transport or connection | Trace the exact granary-to-building link without adding another field |
| Consumer has most inputs but never starts | Missing recipe member or worker | Read every live input and the labour slot |
| Consumer works but Farm Points remain flat | Point-producing condition or current-version fault | Observe one clean control cycle and record the version/readbacks |
If ordinary workers or new families are also failing, use the separate arrival and logistics diagnosis. If Fontebrac is healthy but the campaign stage will not advance, return to the settlement progression roadmap and compare the exact class, happiness, and special-condition lines.
What this route deliberately leaves to the current client
The official Steam listing confirms that agriculture, multiple towns, research, worker assignment, and connected economies are current game systems. The official update history places this guide after the May 2026 full release and the July 2026 v1.0.4 patch.
The supplied Fontebrac walkthrough and farming guide support the crop order, Farmer Residence assignment, granary role, Farm Point loop, and consumer relationships. The supplied Steam Community crop list is readable but explicitly says it is not updated for 1.0; it was used only to cross-check which crops belong to which historical building chains. Its numeric recipes are intentionally not republished. No fixed field yield, building capacity, recipe quantity, Farm Point rate, price, or “best” ratio is claimed.