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

# Catching

In Chainmonsters, creatures are examined and captured through the Replicator device. This stellar piece of technology comes in many variations and utilizes Shard-Energy to function.

Every time you attempt to capture, a bit of Replicator-Energy is consumed. The success rate greatly depends on the moment of time you are attempting to capture a wild Chainmon, as it is influenced by the following criteria:

#### Capture Success Determinator <a href="#catching-capturesuccessdeterminator" id="catching-capturesuccessdeterminator"></a>

* remaining Health left of opposing Chainmon
* level difference between your squad and opposing Chainmon
* current Replicator tier/level and bonus affixed against opposing Chainmon
* any currently active negative status effects applied to opposing Chainmon

Strategic selection of your battle style as well as taking close attention to the current circumstances are key to master the capturing of wild Chainmons and therefore optimizing your capture-success-rate.

After you have successfully captured a wild Chainmon it is added to your Squad or Storage and can further be trainer, upgraded or utilized.


---

# 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.chainmonsters.com/game-mechanics/catching.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.