Kingdoms and Castles

What the game is

Kingdoms and Castles is a small medieval city builder released in July 2017 by Lion Shield. You start with a patch of land, a handful of peasants and a keep, and you build a town that has to feed itself, keep warm through winter and survive what comes for it.

The world is low-poly and cheerful, seen from above at a slight angle. You place farms, orchards, houses, quarries, granaries, taverns and churches on a grid and connect them with roads. Every villager is simulated individually, so a granary too far from a farm means food rots, and a house too far from work means an unhappy resident who eventually leaves.

Then come the seasons, the viking raids and the dragons. Walls and towers are built from stackable blocks, and their height changes how well they defend. Steam lists single-player play only, eighteen interface languages, Steam Workshop mod support and a level editor. Forests grow back if you do not clear-cut them.

What you actually do

You watch numbers and react. Food falls in winter, so you build more farms, but farms need workers, workers need houses, and houses need to be near a market. Taxes fund walls, but taxing hard makes people miserable, so you add a tavern or hold a festival. Every fix spends something that was paying for another fix.

Raids force the second half of the loop. A wall placed for defense blocks a road; a tower on the hill covers the harbor but leaves the farms open. When the dragon arrives you find out whether the height you built was enough. Getting better means anticipating next winter and the next raid while the town is still small, instead of reacting once the granary is already empty.

What it exercises

• Balances food, housing, work and money as one connected system
• Reads a shortage back to its cause rather than treating the symptom
• Plans a layout so distance between buildings does not cost output
• Weighs spending on defense against spending on growth
• Adjusts a strategy when a season or a raid changes the constraints

Why we rate it Minimal Worksheet score 35 / 100

1. FitHow much real knowledge or skill does the play itself make you use?30weight 45%

   Fit sits at 30 because the medieval theme is scenery rather than substance: dragons, taxation and plague sit side by side with no signal about which are real. What you actually do, balancing several interdependent resources, is a general systems-thinking skill in an invented setting, not work in any real discipline.

2. TransferWill what you practise here work outside the game?22weight 30%

   Transfer is the weak point at 22. Reading a shortage back to its cause and spending a limited budget across competing needs are real habits, but the model is a simple game system rather than an accurate one, and the medieval setting teaches nothing true about how medieval towns actually worked.

3. PracticeDoes the game make you use that skill again and again, as it gets harder?60weight 25%

   Practice reaches 60 because every new map repeats the same balancing act and the game has no ending, so the loop runs as long as a player wants. It does settle, though: once a workable layout is found, later games repeat it, and the thinking tips over into waiting.

What the evidence says

Editorial onlyNobody outside our desk has checked this. It is our reading of how the game plays.

The evidence level here is editorial only. The two sources, the Steam page and the developer's own site, confirm the 2017 release, the developer, the price, single-player play, eighteen interface languages, Workshop and level-editor support, and the systems themselves: individual villager simulation, taxation, food, happiness, seasons, viking raids, dragons and stackable castle walls. Neither source addresses learning. We cite no study and know of none on this game. The rating is a reading of what balancing several interdependent resources under pressure asks a player to do, not a measured outcome.

• https://store.steampowered.com/app/569480/ ↗
• http://kingdomsandcastles.com/ ↗