> 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/boss-encounters-and-manual-override.md).

# Boss Encounters and Manual Override

Every PvE simulation concludes with a high-stakes Boss encounter. At this stage, the agent's autonomous behavior pauses and the player assumes direct command through the **Manual Override** system.

The player must manually input strategic commands to exploit the Boss’s weaknesses. While the agent’s base stats and level still dictate the underlying combat rolls, the player’s manual choices augment these rolls. Success in the Boss encounter is a fusion of the agent’s physical build and the user’s tactical judgment. This ensures that rewards are earned through active skill rather than passive farming.


---

# 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/boss-encounters-and-manual-override.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.
