Keep a Shared Village Base Running with Specialist Roles

Design a cooperative village loop where a grower, builder and healer contribute to one shared stock before daily food upkeep and shelter checks.

Seele Editorial TeamUpdated November 19, 2026

In Shared Root, three players choose a Grower, Builder or Healer role, but nobody owns a private pantry. Every harvest, timber cost and herb goes through the same settlement stock. Each player commits one specialist action per day, then the base resolves production, repairs, treatment and the shared food bill in a fixed order.

The two-day cold snap starts with food 2, water 2, timber 2, herbs 1, shelter 0 of 2, and morale 3. Three residents each need one food per day. A grower can add three food for one water, a builder repairs one shelter point for one timber, and a healer can spend one herb to restore two morale or gather an herb. The team can meet upkeep, finish the shelter and keep morale at 5 by sharing every resource.

Three village specialists gather around one shared hearth beside a farm, herb garden and unfinished shelter.
Each specialist works in a different part of the same village base.

Make the shared base the team’s real inventory

Build Shared Root as a two-day cooperative village planner. Three player roles share one base stock and three residents consume one food each at night. Start with food 2, water 2, timber 2, herbs 1, shelter 0/2 and morale 3. Each role submits exactly one action during planning. Grower: Harvest adds 3 food and costs 1 water. Builder: Repair adds 1 shelter and costs 1 timber. Healer: Treat adds 2 morale (maximum 8) and costs 1 herb; Gather adds 1 herb at no cost. All role outputs and costs change the same shared stock, never personal inventories. On commit, validate that one action is assigned to each role; if a required cost is missing, reject the whole day without advancing time. Otherwise resolve Grower, Builder and Healer actions, then consume 3 food. If stock is short, spend what remains, record missing meals and end in shortage. Clear after Day 2 if all six resident meals were served, shelter reaches 2 and morale is at least 5. Restart restores the opening stock and day. Show shared stock before and after each role, upkeep, shelter progress, morale and the commit result.

SystemPrototype rule
TeamThree player roles: Grower, Builder and Healer; all contribute to one village base.
Opening stockFood 2, water 2, timber 2, herbs 1, shelter 0/2, morale 3.
Grower actionHarvest adds 3 food and spends 1 water.
Builder actionRepair adds 1 shelter and spends 1 timber.
Healer actionsTreat adds 2 morale (cap 8) and spends 1 herb; Gather adds 1 herb at no cost.
Daily commitmentAssign exactly one action per role; reject the full commit if any assigned action cannot pay its cost.
ResolutionApply Grower, Builder, Healer actions to shared stock, then serve 3 food for the day.
ShortageSpend available food, record missing resident meals and end the scenario.
ClearAfter Day 2, all six meals are served, shelter is 2 and morale is at least 5.
RestartRestore opening stock, shelter, morale and Day 1 assignments.
InterfaceDisplay roles, shared stock, costs, day, upkeep, shelter and morale.
A grower, builder and healer add food, timber and herbs to one communal storehouse.
Role actions feed one shared ledger rather than separate player inventories.

Define specialist actions and daily upkeep

Start Day 1 with food 2, water 2, timber 2, herbs 1, shelter 0 and morale 3. The Grower harvests: food 2→5, water 2→1. The Builder repairs: timber 2→1, shelter 0→1. The Healer treats: herbs 1→0, morale 3→5. Night upkeep serves three food, leaving food 2; no shortage occurs. Start Day 2 with that shared stock. The Grower harvests again: food 2→5, water 1→0. The Builder repairs: timber 1→0, shelter 1→2. The Healer gathers one herb: herbs 0→1. Night upkeep serves the remaining three residents’ food, leaving food 2. Across both days the team serves six meals, reaches shelter 2 and morale 5, and clears the cold snap. All resources remain in the shared base stock; none is assigned to a private player inventory. This is an authored state trace, not a playable or user test.

Day and roleExpected shared state
Start · Day 1Food 2; water 2; timber 2; herbs 1; shelter 0; morale 3.
Grower · HarvestFood 2→5; water 2→1.
Builder · RepairTimber 2→1; shelter 0→1.
Healer · TreatHerbs 1→0; morale 3→5.
Night 1 · UpkeepServe 3 food; shared stock food 5→2.
Grower · Day 2 HarvestFood 2→5; water 1→0.
Builder · Day 2 RepairTimber 1→0; shelter 1→2.
Healer · GatherHerbs 0→1.
Night 2 · UpkeepServe 3 food; food 5→2; all goals pass.

Trace the two-day settlement plan

Tell the generator that specialization changes what each role can do, while the base remains the only inventory. Resolve a day once after all three players commit. A failed cost check must leave every stock, role and the calendar unchanged.

Create a two-day cooperative village planner called Shared Root with three roles and one shared inventory. Start with food 2, water 2, timber 2, herbs 1, shelter 0/2 and morale 3. Three residents consume one food each every night. Grower Harvest adds 3 food and costs 1 water. Builder Repair adds 1 shelter and costs 1 timber. Healer Treat adds 2 morale (cap 8) and costs 1 herb; Healer Gather adds 1 herb free. Each day require one action from each role. Validate all actions and costs before changing state; if any cannot pay, reject the full commit without advancing. Otherwise apply Grower, Builder, Healer actions to shared stock, then serve 3 food. Record shortages without negative stock. Clear after Day 2 with six meals served, shelter 2 and morale at least 5. Replay: Day 1 Harvest, Repair, Treat; Day 2 Harvest, Repair, Gather. Show opening and closing shared stock, action costs, upkeep, shelter, morale and day. Restart restores the initial state. Do not create private inventories.

Prompt AI to build the role loop

The first draft gave each specialist a personal food or material bag, so the village could show enough total food while another player’s residents went hungry. The revision removes those private inventories: every role action reads and writes the same settlement stock. The commit validates costs before anything changes, and nightly upkeep then consumes the shared food. This is a design revision in the authored specification, not a measured playtest.

The repaired communal shelter and stocked pantry support the village team after two planned days.
The team ends the cold snap with a repaired shelter and two food in stock.

Revise the ledger before the cold snap

Create the shared stock ledger before adding village art. Apply the three role actions in a fixed order, validate costs atomically, then charge nightly food upkeep. Replay both days and compare food, water, timber, herbs, shelter and morale after every step. Godot Resources can hold reusable structured game data, while the SEELE colony-management guide offers a compact way to reason about shared stock and worker jobs. Those references do not imply a built multiplayer prototype. Use AI Game Maker to draft the two-day scenario.

Read SEELE’s colony-management resource loop.

Review Godot’s official Resource data reference.

Frequently asked questions

Why give players different specializations?

The Grower creates food, the Builder improves shelter and the Healer trades herbs for morale. Each role has a clear contribution, but the results go into one shared base, so the team has to coordinate around the same daily needs. That keeps daily planning focused on the group.

Why should resources stay in a shared base?

A shared ledger makes village survival depend on the team’s total stock instead of private bags. The same food pays for every resident, and a failed cost check can be explained before the day advances. The visible total also makes shortages easier to explain.

Open SEELE AI Game Maker.

How can a day commit avoid partial updates?

Validate all three role actions and their costs before resolving any of them. If one action cannot pay, reject the full commit and leave the calendar and stocks unchanged. Otherwise apply the fixed role order, then charge upkeep once. Treat it as one transaction.

Has Shared Root been tested with multiple players?

No. The three specializations, shared stock, action costs, food upkeep, shelter target and two-day sequence are authored prototype specifications. This package does not claim an implemented multiplayer game, browser test, user test or measured balance. Its local previews are static HTML and the result is an authored state trace.

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating