> For the complete documentation index, see [llms.txt](https://gamebyts.gitbook.io/gamebyts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamebyts.gitbook.io/gamebyts/deep-dive/earning-module/byt-earning.md).

# BYT Earning

In GameByts, users are equipped with Computers that generate tokens through gameplay. Depending on their setup and strategy, users can earn both BYT and GBS.

Token earnings per minute are influenced by four primary factors:

1\. Type of Computer

Each Computer type has its own base BYT earning rate.

2\. Efficiency Attribute

A higher Efficiency stat increases BYT earnings per minute.

* From Level 0 to Level 29, users can earn BYT only.
* At Level 30, users unlock the ability to switch freely between BYT and GBS earning modes.<br>

3\. Gaming Consistency

Earnings are optimized when users maintain their gaming consistency within an optimal range.

* Not being consistent in your gaming activity, or any unnatural movement in the game, reduces token earnings by up to 90%, depending on the degree of deviation.\
  \ <br>

Once Power is fully depleted, token generation stops. Users can continue their activity or exit the session by clicking the Stop button.

<br>


---

# 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://gamebyts.gitbook.io/gamebyts/deep-dive/earning-module/byt-earning.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.