> For the complete documentation index, see [llms.txt](https://wiki.cobblemonislands.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.cobblemonislands.com/outbreaks.md).

# Outbreaks

<details>

<summary>What are the outbreaks?</summary>

**Outbreaks** are in-game events in which a large number of wild Pokémon of a single species spawn in a randomly selected area. **These events significantly increase the chances of encountering that species**, making it easier for players to catch, battle, or shiny hunt specific Pokémon. Compared to normal gameplay, more Pokémon appear during an outbreak.

</details>

<details>

<summary>What is the purpose?</summary>

Outbreaks are especially useful for **shiny hunting**. The increased number of encounters raises the chances of finding a shiny Pokémon. As players catch more Pokémon within an outbreak, a "shiny chain" can build up, further improving shiny odds.

</details>

<details>

<summary>Will I get a shiny from this?</summary>

In very rare occasions, a shiny outbreak can happen!

</details>

<details>

<summary>Do I need to do them, or can I ignore them?</summary>

You can simply ignore them if you don't care about the outbreak of that specific Pokémon. Some outbreaks might contain aggressive Pokémon, so it's better to watch out!

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.cobblemonislands.com/outbreaks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.