Plan a breeding workflow around verified access and a shared cake budget
Updated
A farm layout is useful when the intended workflow can run through it. A diagram alone cannot establish that parents remain assigned, preparation is accessible or incubation can proceed. Start with a bounded batch and the actual handoffs between stages, then change a layout only when an observed obstruction gives you a reason.
Map the handoffs before adding more facilities
List the steps you intend to perform: select and check parents, prepare cake, allocate it to the intended breeding work, observe progress and handle incubation when available. Note where you need access and which condition each stage depends on. This is a workflow map, not a claim about automatic behaviour or a universally efficient layout.
Separate an existing reusable facility from a consumable. Building demand belongs to preparation when that facility is missing; it is not automatically charged again for every chosen cycle. Adding farms before finding the blocked handoff can multiply assignments and shared-stock demands without fixing the original obstacle.
Allocate prepared cake before planning new cake
Choose 3 planned cycles and suppose you have 1 prepared cake. Allocate that cake once. The remaining preparation is 2 cakes, not 3. This is a resource plan chosen by the player; it does not forecast how many eggs or desired offspring the work will produce.
For each standard cake the guide lists 5 flour, 8 red berries, 7 milk, 8 eggs and 2 honey. The new batch therefore requires 10 flour, 16 berries, 14 milk, 16 eggs and 4 honey. Combine this demand before subtracting loose inventory, so every shared ingredient is used only once.
Subtract loose inventory from the combined batch
Suppose loose stock is 6 flour, 8 berries, 10 milk, 8 eggs and 2 honey. Compare each ingredient with the combined batch demand. Additional direct ingredients are 4 flour, 8 berries, 4 milk, 8 eggs and 2 honey. This list does not expand flour or other ingredients into upstream production requirements.
Do not subtract the same flour separately from each cake's bill. That would allocate existing stock more than once. Keep completed cake separate as well: its ingredients have already become a prepared item and must not also appear as loose stock. Recount if some stock is consumed by another plan before you craft this batch.
Test the actual space with the intended assignments
Inspect access to the intended facility and observe the selected parents after assignment. Record a visible obstruction or interrupted workflow before changing the surrounding arrangement. A layout that looks symmetrical does not prove that the intended work runs, and an obstruction observed here does not establish a universal rule about every location.
Change the relevant arrangement and repeat the same intended handoff. Keep unrelated changes separate where practical, so the observation answers a useful question. This article does not supply a minimum distance, optimal orientation or guaranteed speed improvement; those would require evidence for the actual construction and game conditions.
Keep preparation and incubation bottlenecks visible
A checked pair cannot replace missing cake preparation, and prepared cake cannot replace the pair check. Incubation readiness is a later dependency rather than proof that every earlier stage works. If you intentionally prepare breeding work before that stage is available, mark the remaining dependency instead of calling the complete workflow ready.
Record what is waiting and why: an unchecked assignment, missing consumable, unavailable facility or an unfinished later step. Do not assign an exact completion time from the ingredient budget. Duration and desired offspring are outside this calculation, and adding facilities is not evidence that the specific blocking condition has been removed.
Reconcile the batch before expanding the workflow
After preparation, compare the actual prepared stock with what the plan reserved. Before beginning another batch, count the remaining cake and loose ingredients again. If the game conditions or recipe differ, stop applying the worked quantities and rebuild the budget from the verified current requirements.
Review the workflow observations separately from breeding outcomes. A functioning handoff demonstrates that handoff under the checked conditions; it does not validate an inheritance forecast. Expand only after the small batch answers your operational question, and keep an explicit resource limit so repeated work does not become an unbounded response to an uncertain result.
Trace the handoffs, allocate prepared cake first, combine new ingredient demand and subtract shared stock once. Test the actual layout against an observed obstruction, then reconcile resources before expanding. Reusable facilities, consumed cake and uncertain offspring outcomes belong to different parts of the plan. Keep the next unresolved handoff visible in the plan.