> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/leisure/cuxial-domino.md).

# Cuxial Domino

Multiplayer domino for FiveM with physical tables, bets, classic and All Fives matches, and an admin tablet.

Cuxial Domino adds domino tables that players sit at and play on, with real tiles on the table. Staff place the tables in game from a tablet, and each table keeps its own rules and bet limits.

## What it does

* **Physical tables.** Three table styles, placed in game and saved in the database. They survive restarts.
* **Tables for 1 to 4 players.** Solo against the AI, 2, 3 or 4 players, and 4 players in teams.
* **Two game types.** Classic domino and All Fives, each with its own target score.
* **Bets between players.** One player proposes an amount, the rest accept, and the winner takes the pot. Paid from bank or cash.
* **Optional bonuses for classic matches**: round pass, opening pass and capicúa.
* **Turn timer** with a forced move when it runs out, and removal after repeated inactivity.
* **Three cameras**: board view, first person and third person, with zoom.
* **Drag and drop or keyboard** to play tiles.
* **Admin tablet** to list, create, teleport to and delete tables.
* **Server exports and events** to create tables and react to matches from other resources.

## Requirements

| Resource             | Required | Used for                                                                   |
| -------------------- | -------- | -------------------------------------------------------------------------- |
| `ox_lib`             | Yes      | Commands, callbacks, notifications and locales                             |
| `oxmysql`            | Yes      | Saved tables and bet pots                                                  |
| `cuxial_bridge`      | Yes      | Connects to your framework (QBox, QBCore or ESX): character name and money |
| `sleepless_interact` | Yes      | The "Sit down" interaction on each chair                                   |

{% hint style="warning" %}
`sleepless_interact` is a hard requirement. Cuxial Domino uses it directly for the chairs; `ox_target` and `qb-target` do not replace it here.
{% endhint %}

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Installation</strong></td><td>Dependencies, start order and the first table.</td><td><a href="/scripts/leisure/cuxial-domino/installation.md">Installation</a></td></tr><tr><td><strong>Configuration</strong></td><td>Every option in <code>shared/config.lua</code>.</td><td><a href="/scripts/leisure/cuxial-domino/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>The admin tablet, calibration tools and in-game keys.</td><td><a href="/scripts/leisure/cuxial-domino/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Create tables and follow matches from your own resources.</td><td><a href="/scripts/leisure/cuxial-domino/developers.md">Exports &amp; events</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and how to fix them.</td><td><a href="/scripts/leisure/cuxial-domino/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cuxial.com/scripts/leisure/cuxial-domino.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.