> For the complete documentation index, see [llms.txt](https://ludo-cities.gitbook.io/ludo-cities-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ludo-cities.gitbook.io/ludo-cities-whitepaper/game/quickstart.md).

# Game Play

### Overview

{% embed url="<https://youtu.be/7XvCgg1PY5k>" %}

***

## **Game Mechanics (MDA Framework)**

### **Mechanics (Rules & Core Systems)**

* Up to **four players**, each controlling **four tokens** starting in their home area.
* **2v2 mode** also available, allowing teammates to strategize together.
* Players take turns rolling a **six-sided die**.
  * Rolling a **6** allows a token to leave home and grants an **extra turn**.
* Tokens move clockwise on a **52-tile path** plus a color-coded **home column**.
* An **exact roll** is required to enter the final home triangle.
* **Win Condition:** First player to bring all four tokens to the centre home wins.
* **Extra Turns:**
  * Upon reaching home.
  * Upon capturing an opponent’s token (unless it is in a protected safe zone).
* **Entry Rule:** Players must roll a **6** to enter the main board.

***

### **Dynamics (Player Actions & System Behaviour)**

* **Turn Order & Movement Strategy:**\
  Players alternate turns in a clockwise rotation. Decision-making emerges when choosing which token to move—especially when multiple are available.
* **Risk vs Reward Trade-offs:**\
  Players must evaluate whether to advance a vulnerable token toward home or deploy a safer token for map control.
* **Blocking & Capturing:**\
  Players can form **blocks**, defend positions, or capture opponents, shifting momentum and turn sequences.
* **Stochastic Flow:**\
  Dice rolls introduce uncertainty, encouraging adaptive strategies and real-time risk management.

***

### **Aesthetics (Player Experience & Emotions)**

* **Tension & Excitement:**\
  Suspense peaks during near-capture moments or final home entries. Captures trigger emotional spikes—triumph for the capturer, frustration for the target.
* **Social Interaction:**\
  Turn-based gameplay cultivates friendly competition, banter, and team coordination.\
  Integrated **voice chat** adds a lively, social layer to every match.
* **Satisfaction & Mastery:**\
  Guiding a token safely home is inherently rewarding. Strategic risk-taking provides depth and long-term engagement.

### Application Asthetics

{% columns %}
{% column %}

<figure><img src="/files/GuUuFZ7iAR6SxwHH6FRH" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/sqwOHyiBvYqfF2lmvCzt" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/vIXOnyluuhdaoFiarCRl" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/bDp9uciErabqryHEtmil" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ludo-cities.gitbook.io/ludo-cities-whitepaper/game/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.