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

# Shadow Pokémons

In the mysterious world of Cobblemon, **Shadow Pokémon** are a rare and intriguing phenomenon. These shadowy creatures possess unique traits and behaviors that set them apart from their regular counterparts.

* **Rare Encounters:** They have a significantly lower chance of spawning in the wild. 
* **Signature Move:** Frustration
* **Unique Stat Modifications**: Shadow Pokémon have distinct stat changes that reflect their mysterious nature: `+10% Attack, +10% Sp. Attack, -10% Defense, -10% Sp. Defense`
* **Non-Breedable:** Shadow Pokémon are unable to breed, ensuring their encounters are a special event.
* **How to purify a Shadow Pokémon?** Can be purify through raising their **friendship** level to **200**, trainers can restore these Pokémon to their normal state, removing their shadow traits.


---

# 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://wiki.cobbletwo.com/pokemons/shadow-pokemons.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.