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

# Base Pixelmon Changes

### External Damage

Pokémon will not take damage from external sources such as suffocating, drowning, lava, fire, or any other source of damage other than being in-battle (or falling into the void). We have done this so that you will not run into situations for example where a Legendary Pokémon that spawned near you ends up wandering into the ocean and drowning before you have a chance to catch it, or a Pokémon spawns in a cave and runs into a lava pool.

### Pokédex

Owned Pokémon will only count towards your Pokédex if you are the Original Trainer ("OT"). This means that Pokémon obtained via trading will not count towards your Pokédex completion percentage.

## Raids

The generation of base Pixelmon Raid Dens has been disabled; you will not encounter raid dens in the wild. Our own implementation of Raids will be coming in a future content update.


---

# 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.thenodemc.com/pixelmon/pixelmon-breeding.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.