Employees and crops solve different bottlenecks, and neither is safe to run on assumptions. Personnel candidates have separate levels for Storekeeper, Farmer, Stablehand, and Ranch Hand work. Crop tiles move through visible preparation states. Training automation is the exception—it comes from upgrading a Training Ground, not from assigning one of those four employee roles. Build the operation one verified handoff at a time, especially while valuable horses are exposed to automatic selling.
This workflow reflects the retail build checked on August 18, 2026, one day after release. The developer is already collecting bug reports and promising updates, while no semantic version was available in the checked metadata. Treat wages, construction prices, job speed, and recipe quantities as live UI values.
Name the bottleneck before paying another wage
The Personnel panel shows each candidate’s level in all four roles, not one permanent class. Compare the job that is failing with the candidate’s relevant level and wage. A cheap worker with the right strength can be more useful than a higher-priced portrait whose best role you do not need.
| Role shown by the game | Assign it for this operating area | Verify after assignment |
|---|---|---|
| Storekeeper | Store handling and sale-side work | Only intended goods move into the shop flow; protected stock remains present |
| Farmer | Crop-field workload | Field tiles advance rather than remaining in their previous visible state |
| Stablehand | Stable-side care | The specific stable task you meant to delegate actually resolves |
| Ranch Hand | Ranch and animal work outside the store | The targeted ranch task changes; do not infer success from the worker merely walking |
The official achievements have separate maximum-level milestones for all four roles plus a Star Employee requirement covering every role. That confirms independent progression tracks. It does not tell us a universal fastest hire order, and it does not prove that two workers with the same role level have the same wage or availability in every save.
Hire, assign, then observe one complete handoff
- Open Personnel and select the candidate card.
- Read all four role levels and the current wage. Choose against the task you named, not the candidate’s best unrelated number.
- If hiring is blocked, inspect employee-cabin capacity; the retail prompt ties more hires to upgrading that cabin.
- Set the role from the assignment dropdown.
- Watch one task from start to finish. Confirm the field, stable, ranch area, or store inventory changed as intended.
- Only then hire a second worker or advance the day. This isolates assignment errors from capacity and pathing problems.
Use Idle as a diagnostic state. It appears alongside the four work roles and gives you a reversible way to stop a worker while checking whether that employee was causing an unwanted transfer or sale.
Horse trainers are attached to their grounds
If the blocked task is Courage, Speed, Strength, or Stamina training, do not search Personnel for a Trainer role. In a developer-marked Steam reply, the studio explains that upgrading a Training Ground automatically hires trainers for it; its level controls concurrent horses and training speed.
That distinction prevents two expensive mistakes: hiring extra Stablehands for a training queue they cannot own, and upgrading the employee cabin when the actual capacity limit belongs to the ground. Build and manually test the correct ground, then upgrade it. The full setup and failure checks are in the training guide.
Build renewable feed supply before wild grass runs out
Grass gathered from the map does not grow back in the current build, according to a developer reply. That makes indiscriminate early harvesting a one-way resource decision. Preserve wild patches as a reserve and establish crop fields before your fodder plan depends on constant grass collection.
The official achievement list shows four fodder tiers and a Fodder Shed progression path. In the recorded save, the first pasture-fodder recipe consumed grass and the interface rated it as only partly effective for adult horses. Its exact quantity and percentage belong to that observation, so read your current recipe before crafting a large batch.
Move each field tile through its visible states
A crop field is not finished when its fenced footprint is built. Each usable tile must be worked. The retail sequence shows separate actions for soil preparation, fertilizer, seed, and water; prompts and tile markers provide the reliable state check.
- Build the crop field in accessible space. Leave room to face every tile without another fence or structure blocking the tool ray.
- Plow the soil. Work tile by tile until the texture changes. If a square does not highlight, reposition rather than clicking the neighboring tile again.
- Fertilize when the tile prompt requires it. A completed plow state is not automatically a completed fertility state.
- Select a seed you actually own. The retail hotbar showed several crop slots; an empty seed stack produces a shortage message rather than planting.
- Plant the highlighted tile. Confirm the seedling or planted-state marker appears.
- Water the planted soil. Water-drop markers distinguish tiles still needing attention. Sweep the field in a consistent row so no corner is skipped.
- Recheck after time advances. Growth is proven by the tile’s next visual state, not by the worker being assigned nearby.
If the current prompt orders fertilizer differently from the sequence above, follow the live tile prompt. The important rule is that each square has independent state; a field-wide assumption is how dry or unplanted gaps survive until the next day.
| Field symptom | Most useful check | Correction |
|---|---|---|
| Tool will not affect a square | Does that tile highlight, and are you facing it within range? | Move to its open edge and reacquire the tile |
| Seed action does nothing | Does the selected seed stack contain any units? | Obtain that seed or choose an available crop |
| One tile lags behind the row | Compare its soil, plant, fertilizer, and water markers | Apply only the missing state |
| Assigned farmer appears inactive | Is there a valid pending field job and a clear path? | Create or expose one task, then watch a full handoff |
| Fodder production stalls | Which ingredient does the current recipe require? | Match fields and reserves to that recipe instead of clearing more wild grass blindly |
Product exclusions do not protect individual horses
The store tutorial includes product exclusions: if you do not want a store employee to stock or display a particular product, exclude that product. That is useful for tools or crafted goods. It must not be stretched into a horse whitelist.
A separate release-day question asked whether an employee could sell only some horses. The developer answered that there is currently no such control and logged the suggestion. Another player report described a valuable foal being sold despite the stand being closed. The safest current workflow is therefore procedural:
- Before assigning a sale-capable employee, record the names and horse count of stock you refuse to lose.
- Sell intended horses manually while breeding stock or foals are present.
- If you need to test automation, set the suspected worker to Idle first, save or record the state, then enable only one role.
- Watch inventory through a single transaction or day transition.
- Stop the worker and investigate immediately if the protected list changes. Closing the visible stand alone is not verified protection.
This is especially important during breeding. A newborn stays with its mare for one day and becomes assignable afterward, so day transitions already contain enough moving parts. The breeding and foal guide gives the capacity and handoff checks.
Use a daily operations rhythm that exposes failures early
- Morning inventory: count horses, protected names, fodder, seed, and open stable slots.
- Assign one bottleneck: give each new worker one observable job before stacking responsibilities.
- Field sweep: walk rows and fix missing soil, fertilizer, planting, or water markers.
- Feed check: read trough capacity and current recipe effectiveness; do not rely on a remembered percentage.
- Sale gate: manually confirm which horses and products may leave.
- Pre-transition record: note pregnancies, newborns, stable capacity, and protected stock before advancing the day.
- Next-morning readback: compare employee results, crop states, horse count, and new notifications with that record.
The operation is ready to scale when a worker completes the intended role task, every planted tile displays the right state, the feed plan no longer depends on non-regrowing grass, and a day transition preserves every protected horse. Extra cabins, employees, or fields come after those readbacks—not before them.
Sources & credits: release status, system scope, achievements, and original JPGs were checked against the official Steam page and the official achievement list. Trainer automation, non-regrowing grass, and the lack of selective employee horse sales are supported by developer-marked replies in verified Steam discussions. Local retail footage supplied for this package was used for interface checkpoints and was not embedded.