Preparing your design workspace

Loading the problem and your saved attempt…

Ludo Game Object Model

Design the in-memory domain model for a complete Ludo match, including legal moves, captures, turn progression, victory, and configurable rule variants.

For this exercise, assume you are designing the in-memory domain model for one complete Ludo match. Two to four players each control four tokens. The board has a shared cyclic track, marked safe cells, and a player-specific home path. On a turn, the active player rolls one six-sided die and may move one eligible token.

A token leaves its yard only on a six. Landing on a single opponent token on a non-safe shared cell returns that token to its yard; multiple tokens may share safe cells, and blockades are out of scope. A token needs the exact remaining roll to finish.

A six grants an extra turn only after a legal move; if no legal move exists, the turn passes. A player wins as soon as all four of their tokens finish. The match is single-process and commands are handled serially. Persistence, networking, matchmaking, computer players, and user-interface behavior are out of scope.

Produce a design only: clarify requirements, define the object model and contracts, and walk through important interactions. No implementation is required.