> For the complete documentation index, see [llms.txt](https://docs.pixudi.com/pixudi-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixudi.com/pixudi-manual/gameplay/game-process.md). # Game Process Pixudi game process is based on the mechanics of classic board games but also has advantages provided by the blockchain. This is a step-by-step instruction: 1. After logging in, a user chooses to create their own game or to join one of the existing rooms.

Creating your own game

List of active games

2. When all players joined the game, the story starts. The first player to make a move rolls the dice. Their character moves on the board according to the number that came up.

Game process

3. The board that users play on represent a map with 70-100 reference points - a path that users need to overcome to get to the finish line. About 30% of those points are complicated by events. When a player reaches a 'blank' point (not complicated by an event), the turn goes to the next player. However, if a player reaches a complicated point, some scenario event happens resulting in a positive or a negative outcome for the player.

Map example (day version)

Map example (night version)

4. Players can use special power-ups (items) to overcome bad events such as curses or just get closer to victory. 5. Players roll the die turn by turn until they run out of moves. When this happens, the game ends and players receive experience points, event points (if they played on the seasonal event board), and a prize pool (if any). --- # 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.pixudi.com/pixudi-manual/gameplay/game-process.md?ask=&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.