Agricola: Family Edition cover
2016BGG rank #1,674

Agricola: Family Edition

by Uwe Rosenberg · Lookout Games

Browsing is free. Ask BoardGameBrain about this game when rules coverage is ready.

Players1–4
Time45m
ComplexityMedium-Light
Age8+

About the game

What is Agricola: Family Edition?

In Agricola, you're a farmer in a wooden shack with your spouse and little else. On a turn, you get to take only two actions, one for you and one for the spouse, from all the possibilities you'll find on a farm: collecting resources; building meadows; and so on. You might think about having kids in order to get more work accomplished, but first you need to expand your house. And what are you going to feed all the little rugrats? Agricola is a turn-based game. There are 14 game rounds occurring in 6 stages, with a Harvest at the end of each stage (after Rounds 4, 7, 9, 11, 13, and 14). Each player starts with two meeples that can each take an action per round. There are multiple options, and while the game progresses, you'll have more: each round a (fixed) additional option becomes available. Each action can be taken by only one player each round, so it's important to do some things with high preference. In comparison with the family game of the predecessor, much has changed: the new action each round is fixed, and the game has been simplified by removing stone and vegetables. Similar to 'Agricola: All Creatures Big and Small', there are now buildings (replacing the major improvements) that score points for leftover resources at the end of the game. Also, there are no building restrictions (nor player boards). And finally, there are no negative points or point limits anymore, each player simply scores for all he has achieved.

How it plays

Mechanics

Automatic Resource GrowthWorker Placement

On the shelf

Categories

AnimalsFarming

Questions players ask

Questions to bring to BoardGameBrain

  • How do setup and the first turn work in Agricola: Family Edition?
  • When does scoring happen and what ends the game?
  • How should the table resolve an unusual timing or rules interaction?