> For the complete documentation index, see [llms.txt](https://dejvokep.gitbook.io/chatgames/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dejvokep.gitbook.io/chatgames/customizing-the-games/game-customization-guide.md).

# Game customization guide

## Enabling/disabling

Each game provides you with a boolean switch `enabled` that controls whether the game will be enabled or disabled. When disabled, the game's status will be shown as an ❌  in the diagnostics command.

## Filtering databases

Games derive their prompts (questions) from random entries from a database (term/sentence/trivia).

That's why all, except Trivia and Type Random games, provide a `words` range, which will filter the database used by the game to only contain entries which have amount of words contained within the range.

You can learn more about ranges [here](/chatgames/customizing-the-games/ranges.md).

## Answer verification

There are 4 switches available throughout the games configuration which can alter and customize how answers sent by players are verified:

* `trim`: determines if to allow redundant spaces before and after the answer (e.g. allow `" 42"` when `"42"` is the answer). Recommended to have enabled to avoid rejecting correct answers with typo-ed spaces.
* `case-sensitive`: if answers must match the exact capitalization (e.g. don't allow `"A"` when `"a"` is the answer). Recommended to have enabled only for Type and Reverse games.
* `missing-only`: if to allow only the completed letters as answers, or also the whole filled term (Fill In The Blanks and Complete Term games only).
* `ignore-spaces`: if to ignore spaces between digits in the answer (Solve Math game only). Recommended to have enabled to avoid rejecting correct answers with typo-ed spaces.


---

# 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://dejvokep.gitbook.io/chatgames/customizing-the-games/game-customization-guide.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.