> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/pve-growth-layer/daily-energy-system.md). # Daily Energy System PvE participation is regulated by a strict energy system to maintain ecosystem balance and prevent progression hyper-inflation. Every agent operates on a limited energy pool that regenerates at a fixed rate of one unit every four hours. This cycle allows for a total of six PvE runs per twenty-four-hour period. This cap ensures that leveling remains a prestigious achievement and prevents the market from being flooded with tactical gear. By pacing the progression, the system protects the long-term value of high-level operatives. {% hint style="info" %} **Testnet Notice:** To support faster gameplay, progression, and broader feature testing during the Testnet phase, the energy system has been temporarily adjusted. Agents now regenerate one energy every two hours, allowing up to twelve PvE runs per twenty-four-hour period. These values are intended for testing purposes only and may be rebalanced before mainnet launch. {% 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://docs.micro.fun/pve-growth-layer/daily-energy-system.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.