Pilgrim

Pilgrim sounds as though someone put three rather different designs on a workbench, joined them with wire, and waited to see whether they would start. It has 18xx-adjacent route building, an engine-building layer, and a mancala sequence with Trajan in its family tree. Remarkably, the assembly holds: it produces decisions that are properly interesting.

That mancala engine sets the tempo, determining which actions become available and how they can be combined. Around it, you develop a personal engine, while the route-building layer supplies the economic and spatial pressure. The interesting decision is when to feed the future efficiency of your machine and when to do the thing the map needs desperately now.

Interaction is not ornamental, because routes and the limited ways of developing them constrict the board for everyone. The two narrow trade routes in particular too often feel like a single prescribed corridor rather than a field of competing plans. Workers and resources are perpetually short, so each round becomes a chain of hard choices: take one thing, leave another exposed, and hope nobody exploits the gap before you return.

That is also my reservation. The scarcity is so comprehensive that it sometimes makes the game more draining than it needs to be, rather than merely sharper; a few more workers and a more open route structure would give it room to breathe. Even so, Pilgrim is a very interesting oddity for players who like their trains in different overalls.