Ur: 1830 BC cover
2001BGG rank #7,189

Ur: 1830 BC

by Jeroen Doumen, Joris Wiersinga · All-Aboard Games

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

Players3–6
Time180m
ComplexityMedium-Heavy
Age14+

About the game

What is Ur: 1830 BC?

This game isn't a true 18xx game, in the sense that it's officially sanctioned by Francis Tresham. However, it shares a good number of characteristics with the 18xx series of games, while still being different enough to be a different game. The game is about diverting water from rivers into irrigation channels and supplying the life-giving water to sections of land. In 18xx, there are private companies; in Ur, there are independent nations. In 18xx, there are companies with shareholders and a majority-controlling president; in Ur, there are countries with landowners and a majority-controlling King. Once a Kingdom has enough land purchased in it, it begins to build water infrastructure in the form of reservoirs and pumps. These structures draw the water away from the rivers into irrigation channels which are drawn straight on the board. Like 18xx, the technology increases as the game progresses, making channel diggers obsolete and bringing out more efficient waterworks. When a section of land is irrigated, the owner earns a small degree income and the kingdom it's located in earns a much larger income, which can then be given to the landowners or kept in the Kingdom's coffers for future upgrades. The game is finally over when all the incoming water is used, forcing the southern tribes to invade, or a kingdom cannot fulfill it's obligation to buy more ditch-diggers and falls into revolution. The player with the largest personal holdings (land and money) is the victor.

How it plays

Mechanics

Auction / BiddingTile Placement

On the shelf

Categories

AncientCivilization

Questions players ask

Questions to bring to BoardGameBrain

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