Pax Autocratica How to Give Soldiers Food Guide

To give soldiers food in Pax Autocratica, build the Kitchen and Food Hall, choose a recipe in the Kitchen, confirm ingredients can follow the current build's storage path, then allocate prepared food in the Food Hall. The available evidence is two player videos and corroborating logistics notes, not an official feeding manual. Treat menu labels, keys, recipes, and quantities as version-sensitive; where a current-build detail is not corroborated, it is 待确认.

Buildings Required for Soldier Meals

The reported chain has three visible purposes: a place for soldiers to live, a Kitchen that prepares food, and a Food Hall where people eat. The second collected beginner video presents the Barracks, Kitchen, and Food Hall as early research and construction priorities, then shows the Food Hall as the eating location. It also says the player helped finish the Kitchen and Food Hall after placing them. That is useful opening-order context, but it is a player report, not a published build order or proof of a mandatory research sequence.

Start by checking whether the buildings exist and whether the Kitchen and Food Hall are actually complete in the current save. A Barracks alone is not evidence that meals are available. Likewise, placing a Kitchen and Food Hall does not establish that a recipe is running or that food has been assigned for service. Keep the two food buildings close enough that you can inspect both sides of the chain without a long trip, preferably near the people who use them and the storage route that feeds them. This is a logistics recommendation supported by the base-layout material, not a fixed placement radius.

Recipe and Production Modes

One video shows cooking being changed from the Kitchen and mentions a starting recipe; another shows selecting a recipe in the Kitchen before starting production. Those observations support the basic sequence: open the Kitchen's current recipe or production interface, select a recipe available in this save, and begin production. Whether the current interface identifies recipe inputs is 待确认. The exact key, interaction prompt, recipe name, unlock condition, and screen layout are also 待确认 because they are not independently corroborated and can change between builds.

The two videos disagree on the preferred production mode. The first creator says they use Continuous for food and presents Stock as an available alternative. The second creator demonstrates Stock and describes using a numeric target. Neither preference is an official recommendation, and the fixed targets shown in either video are not a safe universal setting. Do not copy a number simply because it appears in a recording.

Treat the modes as observed alternatives. Continuous is the reported choice for repeatedly cooking while the creator expects food demand and inputs to continue. Stock is the reported choice for maintaining a player-selected reserve. Use only a mode shown in the current build; its limits and any current differences are 待确认. A mode called Order is discussed in the logistics material, but its current availability and behavior are 待确认; do not rely on it for this food procedure unless it appears in the game.

Ingredient and Storage Flow

A Kitchen cannot resolve hunger if ingredients never reach the place from which it draws them. The first video reports collecting output at a Resource Transport Station and manually depositing goods into warehouse or inventory storage. The corroborating logistics notes make the same distinction: production at a pad is not yet usable supply until transport and storage connect it to the consumer. Both are player-reported evidence, so do not read them as a guarantee that every current build behaves identically.

Follow the storage path instead of guessing. If the current Kitchen interface names an ingredient, trace it from where it is produced or collected through transport and storage. Whether the Kitchen displays ingredient requirements or available quantities is 待确认. If the chain stops at any point, fix the visible transport or storage link before changing recipes or increasing production. A full-looking producer pad does not prove the Kitchen can access its contents.

The first video reports manual collection and manual deposit in its build. Confirm the current on-screen prompt rather than assuming a particular key works; that control is 待确认 outside the reported video.

Staffing and Food-Hall Use

After ingredients are accessible, check people before moving buildings. The videos describe worker or soldier management and assignment to work locations; the layout notes also warn that an unstaffed Kitchen or transport post cannot recover because it is closer to storage. If the current build presents an assignment view, check whether the cooking and hauling work has coverage. The exact tab, right-click behavior, and job-lock control are single-source observations and therefore 待确认 as universal controls.

Prepared food must also be made available at the Food Hall. The second video shows a Food Hall dashboard where food types are allocated for residents to eat. It reports a limited set of early options, but the exact number of slots, available meal types, and allocation interface are not corroborated. Use the current Food Hall panel to allocate food if that option is present. Do not substitute an unverified claim about beds, automatic serving, a fixed food assignment limit, or Food Hall staffing.

Symptom-Based Troubleshooting and Version-Sensitive Controls

Soldiers are hungry and the Food Hall has no meal to allocate. Check the Kitchen first: is a recipe selected, and does the current interface show a production state or ingredient requirement? Those UI details are 待确认. Then trace the storage and transport route. This is more useful than placing another hall, because a hall cannot serve a meal that was never prepared.

The Kitchen is idle. If the current interface names an ingredient, follow its route from producer to transport to Warehouse or inventory. Whether the Kitchen reports a missing ingredient or exposes an access rule is 待确认. The first video specifically reports manual collection and manual deposit in its build; the reported key is not a durable instruction. Do not assume an invisible shared inventory.

Ingredients exist but no meals appear. Inspect staffing and the selected production mode. Continuous and Stock are both observed choices, but they are not interchangeable promises of output: both still depend on inputs and workers. Use the mode offered by the current interface, avoid copied fixed quantities, and observe whether the recipe completes after the change.

Meals are prepared but soldiers still do not eat. Reopen the Food Hall panel and repeat the food allocation observed in the second video. The reported interaction keys, dashboard details, access behavior, and schedule rules are version-sensitive and 待确认, so do not invent a further control or eligibility rule.

Sources

This guide separates player observation from confirmed game documentation. No official Kitchen, Food Hall, or soldier-feeding manual was included in the collected source set, so specific controls, quantities, and current behavior remain version-sensitive.

• Beginners Guide to Pax Autocratica, collected transcript: Kitchen recipe change, Continuous and Stock as alternatives, transport collection, and manual storage observation.
• Beginner Guide For Getting The Best Start In Pax Autocratica!, collected transcript: early Barracks, Kitchen, Food Hall, Stock demonstration, and Food Hall allocation observation.
• Collected base-layout logistics guide: external third-party context for warehouse, transport, and staffing observations; it does not establish fixed food quantities or current controls.
• Collected independent base-layout field manual: external third-party context for short routes, functional zones, and food-service flow; its build-specific claims are not treated as current authority.