> For the complete documentation index, see [llms.txt](https://rulebook.riseofthepixels.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rulebook.riseofthepixels.com/gameplay/games/game-rating.md).
# Game Rating
Each game receive a rating based on two separate criteria.
**Game Rating Engine** (up to 90% of the final score)
* How well the selected genre/theme fit together and how successful those types of games are for the selected platform
* Development task points allocation (number of available points depends on team total speed and selected project duration)
* Skill of your team and how they fit the specific game type. Remember that some [Roles](/team-and-accessories/your-team/roles.md)are better suited for some development tasks
* Boosts from research used to create the game.
**AI Rating** (up to 10% of the final score)
* Game title and description are analyzed by our AI and a score is assigned based on how well those fit your game.
*NOTE*: There is a system in place to avoid abuse and studios working on the same game type over and over. It is recommended to rotate the type of games you create to maximize your ratings and rewards.
---
# 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://rulebook.riseofthepixels.com/gameplay/games/game-rating.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.