> For the complete documentation index, see [llms.txt](https://admin-233.gitbook.io/tawalk-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://admin-233.gitbook.io/tawalk-whitepaper/earning-cap-mechanics.md). # Earning Cap/Mechanics ### Solo Mode Earning Cap Solo Mode has both a **Daily Energy Cap** and **Daily Token Cap**. These limits restrict the amount of Energy and tokens that users can have per day. #### **Daily Energy Cap** Users start the game with 2/2 Energy. Max Energy Caps at 20/20. Users can increase their Energy by getting more or higher quality Sneakers (Refer to Energy System above) #### **Daily Token Cap** Users start the game with a 5/5 Daily TAW Cap. The Daily Token Cap maxes out at 30 TAW. Users can increase their Daily Token Cap by leveling up their Sneakers. User can further permanently increase the TAW cap beyond 30/30 by by burning some TAW. This option will only become visible when you reach 90% of your current Daily Cap. There is **NO** earning cap for TAS. ### Solo Mode Earning Mechanics #### TAW ![](/files/TmesrT3Grrw8EjsSVEm5) ![](/files/YfTcLwIv9gb0UDcQxICd) --- # 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://admin-233.gitbook.io/tawalk-whitepaper/earning-cap-mechanics.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.