# ZJH Road Chart Format

## Explaination of each keys

* rt0：Bead Plate
* rt1：Big Road

## Data format of each keys

Each checker represents a single cell within the grid, identified by its Row and Col using 0-based indexing (meaning the first cell is Row: 0, Col: 0).

* rt0 and rt1 use checkers as data points (e.g., 0,1,1,256,0). The string data consists of 5 parts:
  * 0 => Row (int, required)
  * 1 => Col (int, required)
  * 1 => Winner (int, required)
    * 1 = Banker (紅色)
    * 2 = Player（藍色）
    * 3 = Tie（綠色）
  * 256 => Bitwise Combination Data:

    * CntFties => First Tie status. (rt1 only; 0: None, >0: Number of first ties, Max: 15)

    * CntTies => Tie status. (rt1 only; 0: None, >0: Number of ties, Max: 15)

    * CntBps => Banker Pair status. (0: None, >0: Number of pairs, Max: 15)

    * CntPps => Player Pair status. (0: None, >0: Number of pairs, Max: 15)

    > c# example for extract values of (CntFties&0xf)<<12 | (CntTies&0xf)<<8 | (CntBps&0xf)<<4 | (CntPps & 0xf))

    ```
        int CntPps = 256 & 0xf
        int CntBps = (256 >> 4) & 0xf
        int CntTies = (256 >> 8) & 0xf
        int CntFties = (256 >> 12) & 0xf
    ```
  * 0 => always 0

```json

{
    "rt1":"0,0,2,0,0;1,0,2,0,0;2,0,2,0,0;3,0,2,0,0;4,0,2,0,0;5,0,2,0,0;5,1,2,0,0;5,2,2,0,0;5,3,2,0,0;5,4,2,0,0;5,5,2,0,0;5,6,2,0,0;5,7,2,0,0;5,8,2,0,0;5,9,2,0,0;5,10,2,0,0;5,11,2,0,0;5,12,2,0,0;0,1,1,0,0;1,1,1,0,0;2,1,1,0,0;3,1,1,0,0;4,1,1,0,0;4,2,1,0,0;4,3,1,0,0;4,4,1,0,0;4,5,1,0,0;4,6,1,0,0;4,7,1,0,0;4,8,1,0,0;4,9,1,0,0;4,10,1,0,0;4,11,1,0,0;4,12,1,0,0;0,2,2,0,0;1,2,2,0,0;2,2,2,0,0;3,2,2,0,0;3,3,2,0,0;3,4,2,0,0;3,5,2,0,0;3,6,2,0,0;3,7,2,0,0;3,8,2,0,0;3,9,2,0,0;3,10,2,0,0;3,11,2,0,0;3,12,2,0,0;0,3,1,0,0;1,3,1,0,0;2,3,1,0,0;2,4,1,0,0;2,5,1,0,0;2,6,1,0,0;2,7,1,0,0;2,8,1,0,0;2,9,1,0,0;2,10,1,0,0;2,11,1,0,0;2,12,1,0,0;0,4,2,0,0;1,4,2,0,0;1,5,2,0,0;1,6,2,0,0;1,7,2,0,0;1,8,2,0,0;1,9,2,0,0;1,10,2,0,0;1,11,2,0,0;1,12,2,0,0;0,5,1,0,0;0,6,1,0,0;0,7,1,0,0;0,8,1,0,0;0,9,1,0,0;0,10,1,0,0;0,11,1,0,0;0,12,1,0,0;0,13,1,0,0;0,14,1,0,0;0,15,1,0,0;0,16,1,0,0;0,17,1,0,0;0,18,2,0,0;1,18,2,0,0;2,18,2,0,0;3,18,2,0,0;4,18,2,0,0;5,18,2,0,0;5,19,2,0,0;5,20,2,0,0;5,21,2,0,0"
}

```


---

# Agent Instructions: 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:

```
GET https://docs.pkg333.app/en/enum/enum-roadmap-zjh.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.