> 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/game-dev-studio/fanbase.md).

# Fanbase

The Fanbase of your Game Dev Studio has an impact of the sales (rewards per round) of your games. The higher the Fanbase, the higher the $PXL rewards.

Similarly to [Reputation](/gameplay/game-dev-studio/reputation.md), the quality of the games you release has a direct impact on the size of the Fanbase of your studio. Fanbase is also affected by the number of bugs found in your game.

### Bugs

As the size and complexity of your projects increase your chance of releasing a game with some bugs goes up.

A good team and careful allocation of your task points can greatly reduce the chance of introducing bugs in your code. If you release games with too many bugs your fanbase will be upset and over time you will lose fans.

{% hint style="warning" %}
Note: The current UI does not display your Fanbase—it is a 'hidden' stat for now.
{% endhint %}


---

# 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/game-dev-studio/fanbase.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.