> For the complete documentation index, see [llms.txt](https://docs.studio.uzu-app.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.studio.uzu-app.com/en/basic-features/phase/basic/timeline.md).
# Game flow display phase
The game flow display phase illustrates the **entire scenario flow**, including an opening, character text loading, discussions, moving to voting, and the ending. It also helps players understand where they are in the game and what phase will come next.
In version 1, the game flow was automatically displayed between all phases, but in version 2, you can choose where to display it. You can proceed without inserting it between phases where you do not want to interrupt the flow.
\\
The game flow phase can be configured from the detailed screen of each game's flow phase.
### Basic Items
The basic items are "Phase Name," "Phase Description," and "Duration of Phase."
Each is displayed as follows.
### Corresponding Phases (Mandatory)
Choose the phases that correspond to each game flow from the timeline-unset phases.
You can set **multiple phases** in one display. The order of the phases can be changed, but the order does not matter.
### Display Conditions (Optional)
You can set when specific items will be **hidden** and from when they will be displayed.
This is effective, for example, if there is a secret phase that only appears after a certain ending, or if there are additional discussions that are not revealed at the beginning of the game.
You do not need to set this for phases where there is no need to hide anything, such as the opening, character text loading, and regular discussions.
---
# 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://docs.studio.uzu-app.com/en/basic-features/phase/basic/timeline.md?ask=&goal=
```
`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.