Choose fertile ground and a field your workers can service before spring cultivation starts. Plot quality is chosen at construction, spring establishes the crop, and summer water, fertilizer, and weeding determine how much of the visible estimate survives to harvest.
For the Early Access farmland system, check the field panel against official updates through August 14, 2026. The launch rework merged spring actions, removed the old consecutive-planting fertility penalty, added a live autumn estimate, and changed how fallow land recovers. Older rotation advice should not override the current field panel.
Choose the plot by land quality and service cost
When you draw a new field, its initial land quality is based on the average fertility across the selected area. Dragging the boundary over a weak patch can lower the whole field’s starting state. Read the construction preview and the final Summary or Planting tab instead of judging the soil by color alone.
A large fertile field can still overrun your spring labor and summer supplies. It also creates more spring work, summer care, and autumn harvesting. Before confirming the boundary, locate:
- a working well or other water source that laborers can reach;
- the fertilizer production and holding point;
- the housing and food route used by the farm workforce;
- the kitchen or storage destination that will receive the crop;
- a road that does not force every trip through a city gate or industrial doorway.
If one of those routes is already overloaded, reduce the field or repair the route first. A field that is theoretically fertile but cannot be serviced through summer is a bigger risk than a smaller field whose inputs and harvest can move on time.
Spring now has one cultivation job
The launch system combines the former reclamation and sowing steps into a single spring cultivation action. New farmland defaults to millet, which prevents an empty crop selection from silently wasting the season. Still open the Planting tab and confirm the crop; a default is a safeguard, not a reason to stop checking the field.
Assign enough labor to finish cultivation while spring remains useful, then watch progress rather than the animation. If progress is slow, separate three causes:
- Too little farm labor: the assigned groups cannot cover the chosen area.
- Too much walking: workers spend the season reaching housing, food, water, or the field.
- Competing city work: recruitment, construction, hauling, or personal needs pull the same population away at the wrong time.
Canceling a crucial construction project or delaying recruitment can be safer than building a second field. Spring time cannot be stored for later.
Use summer as the control window
An active field consumes water and fertilizer through summer while laborers perform weeding. The three inputs jointly advance crop ripening and affect the estimated autumn output. Open that estimate at the start of summer, after each supply change, and before transferring farm labor elsewhere.
If the autumn estimate stalls or falls after a supply change, inspect these causes:
- If water is failing, inspect the well’s labor and local stock before building another well.
- If fertilizer is failing, trace waste or other accepted input into the fertilizer recipe, then follow the output to the farm.
- If weeding is behind, return labor from non-seasonal work before adding a larger agricultural district.
- If all three are present but the estimate barely moves, check land quality, progress, selected crop, pathing, and the latest client version.
The official launch rules provide a guaranteed base yield even when summer care is absent. That prevents every mistake from becoming an automatic zero, but it does not make care optional for a growing settlement. Compare the estimate with the number of people who must eat through winter and the processing capacity that can turn the crop into food.
Water is a working service, not warehouse stock
The launch rework keeps water inside wells. Kitchens, housing, and farmland use it on demand, and the well itself requires workers. If a farm shows a water shortage, a territory-wide inventory total may not explain it.
Open the well and verify that it is staffed and producing. Check the route from the well to the field and whether other consumers are competing for the same service. Watch one laborer complete a water trip. If they turn around, take a long detour, or spend most of the cycle on personal needs, fix that route before assuming the groundwater is insufficient.
Do not wait for water to appear in a general storage building. The current rule intentionally destroys stored water when its source building is demolished, another reason to finish a replacement before removing or moving the existing well.
Fertilizer is both a recipe and a delivery problem
Latrine waste can be processed into liquid fertilizer through the available recipe chain. It can also compete with siege-related output, so confirm which recipe is selected and which branch currently has priority. A fertilizer total elsewhere in the city does not care for a field until the material reaches the farm during summer.
Set a practical reserve before opening non-food uses. If summer is already under way, temporarily pause the branch that consumes the same input. Then monitor the field estimate after delivery. If the fertilizer indicator changes but yield does not, check whether water or weeding is now the limiting input rather than continuing to send more fertilizer.
Fallow restores land without consuming farm labor
Land quality is deducted gradually after autumn harvest. A field set to fallow recovers quality gradually during summer, and the launch rules do not require workers on that fallow field. This creates a useful release valve: rest the weaker plot and transfer its groups to an active field, construction, food processing, or defense.
The old consecutive-planting fertility penalty was removed in the August 12 rework. Do not rotate crops solely because a fan guide says repeating the same crop increases the penalty. Rotate or change crops when the live client shows a useful output reason; use fallow when the land-quality panel shows that recovery is worth more than another weak harvest.
At the start of summer, compare each active field with any field you could leave fallow:
- active field with good land quality and full service;
- active field with weak quality but an essential crop;
- active field whose water, fertilizer, or labor cannot be supplied;
- fallow field that can recover while releasing its workforce.
Keep only the active acreage the city can actually care for. Four neglected fields can produce less useful food than two fully supported fields while consuming far more travel and management attention.
Autumn is a progress check, not a waiting season
When autumn harvest begins, the field panel displays current harvest progress and remaining quantity in real time. Use both values. A good estimated yield can still be lost operationally if too few workers collect it before the season closes or if output cannot leave the field.
Inspect the destination before harvest peaks. Make sure the accepting food location and the kitchen route are ready, and pause lower-priority carrying work if crops accumulate. Do not pull farm labor into the army merely because the plants look mature; wait until the progress and remaining values show the field is actually cleared.
The August 14 patch blocked the interface from changing an already-sown field into Fallow. If your current field enters an impossible state, verify the latest update, preserve a save, and report the exact season, crop, and panel state through F9 rather than treating the bug as a hidden farming rule.
Turn the harvest into winter meals
Millet is not the end of the food chain. It must reach a kitchen and become the accepted staple meal before it satisfies the population. Retainers can require richer food, which brings hunting, slaughtering, and meat preparation into a separate chain.
Before winter, track standing crop, raw harvest, cooked food, and reachable reserve separately:
| State | What to verify | Failure risk |
|---|---|---|
| Standing crop | Autumn estimate, progress, remaining quantity | Season ends before collection |
| Raw harvest | Field output and accepting destination | Field fills or carriers never clear it |
| Cooked food | Kitchen water, recipe, labor, and output | Large grain total but no edible meal |
| Reachable reserve | Population access and winter consumption | Food exists but needs remain unmet |
Winter also raises fuel demand. Do not spend the entire autumn labor pool processing food while firewood or charcoal sits unfinished. The successful harvest is the one that becomes reachable meals without breaking the heating and defense loops needed to survive the same season.
Diagnose a weak harvest from the earliest failed season
The field never established: confirm it was built in time, millet or another crop was selected, cultivation progress completed, and labor could reach the plot during spring.
The summer estimate stayed near its floor: inspect water, fertilizer, weeding, land quality, and active-versus-fallow state. Correct the missing input while summer remains.
The estimate was good but little entered storage: check autumn labor, remaining quantity, local output, routes, and destination acceptance. This is a harvest logistics failure, not a fertility failure.
The granary looked full but morale still fell: distinguish raw millet from cooked food, then verify kitchen water and population access. Count what people can eat, not what the territory can display.
Land quality keeps declining: read the post-harvest value and give weak fields a summer fallow period. Do not add an obsolete continuous-crop penalty that the launch build removed.
Before winter, check spring completion, summer inputs, the autumn estimate, harvest progress, food processing, and actual meal consumption in the current client.