> For the complete documentation index, see [llms.txt](https://codyfight.gitbook.io/white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codyfight.gitbook.io/white-paper/gameplay/metagame/casual-gaming.md).

# Casual gaming

While players can engage in the competition of Codyfight, there are other options available outside of such space. Casual gaming is free to play and does not require any special conditions. There is different modes available, as players can play with random users or friends.

Casual gaming is linked to the game builder aspect of Codyfight, meaning that as the game further develops, the free-to-play modes are customizable and personalized for players. Also, casual gaming carries an important role in the community as it offers the opportunity to bond with others and engage in mini-games with rewards and prizes.

An example is an in-game challenge where [Codyfighters](/white-paper/gameplay/in-game-assets/codyfighter.md) have to catch Legendary Llama, getting big rewards if they can capture her. There will be more mini-games as such, featuring new [Special Agents](/white-paper/gameplay/metagame/npcs.md) and other conditions.


---

# 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://codyfight.gitbook.io/white-paper/gameplay/metagame/casual-gaming.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.