> For the complete documentation index, see [llms.txt](https://webingate.gitbook.io/webingate-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://webingate.gitbook.io/webingate-docs/basics/markdown/playhub/games.md).

# Games

The **Games** section allows users to view and manage all created games. Games are categorized into different tabs based on their status.

### Games Screen

The **Games** screen displays a list of games and allows users to filter them by their status.

#### Tabs

At the top of the screen, the following tabs are available:

* **Today's** – Displays games scheduled for the current day.
* **Future** – Displays upcoming games.
* **Past** – Displays games that have already occurred.
* **Completed** – Displays games that have been completed.

#### Game Card

Each game is displayed as a card containing the following information:

* **Game Name** – Title of the game.
* **Game Date** – Date when the game was scheduled.
* **Participant Avatars** – Profile icons of the players participating in the game.
* **Privacy Status** – Indicates whether the game is **Private** or Public.
* **Country Flag** – Displays the country associated with the game.

#### Navigation

When a user **taps on any game card**, the application **navigates to the Game Details screen**, where full information about the selected game is displayed.

## Game Details Screen

The **Game Details** screen provides comprehensive information about a specific game, including players, scores, and administrative details.

### Game Header

The header section includes:

* **Game Name** – The title of the game.
* **Chat Button** – Opens the chat related to the game.
* **Record Button** – Allows recording of the game session.
* **Status Indicator** – Displays the current status of the game (e.g., **Completed**).

***

### Game Information

This section shows key details about the game:

* **Date and Time** – When the game took place.
* **Game-Time Decision** – Indicates decisions related to game scheduling or location.

***

### Score & Players

This section displays the competing players and their scores.

#### Home (Serve)

* Shows the **Home player**.
* Displays the **score** achieved by the home player.
* Indicates the player’s **rating badge**.

#### Away (Receive)

* Shows the **Away player**.
* Displays the **score** achieved by the away player.
* Indicates the player’s **rating badge**.

#### Result

At the bottom of the score section, the **match result** is displayed.

Example:

```
Away Team Won by 1 Point
```

***

### Organizers / Admins

This section lists the users responsible for organizing or managing the game.

Information displayed includes:

* **Organizer Name**
* **Admin Indicator (Crown Icon)**

***

### Privacy Indicator

The game privacy status is shown as:

* **Private** – The game is only visible to invited participants.

{% columns %}
{% column %}

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

{% column %}

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

<figure><img src="/files/XeFTBjvSYFotVHetk5B6" alt="" width="375"><figcaption></figcaption></figure>


---

# 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://webingate.gitbook.io/webingate-docs/basics/markdown/playhub/games.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.