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

# 🌈 Elements

Each of the 11 distinctive [Archetypes](broken://pages/gecoiYTCfIzCPc7YafZj) thrives within six distinct elemental domains, infusing depth into your monster collection and battles. The elemental forces that govern these realms are as follows:

🔥 Fire 💧 Water 🍃 Nature ⚡️ Electric 🔮 Mental ☠️ Toxic

As you embark on your journey, you'll encounter the intricate web of elemental strengths and weaknesses, carefully woven to follow a strategic **Rock-Paper-Scissors** mechanic. Mastery of these elemental dynamics becomes pivotal for your triumphs in the Polyverse.

🔻 Elemental Weaknesses:

* 🔥 Fire: Vulnerable to 💧 Water | 🔮 Mental
* 💧 Water: Vulnerable to 🍃 Nature | ⚡️ Electric
* 🍃 Nature: Vulnerable to 🔥 Fire | ☠️ Toxic
* ⚡️ Electric: Vulnerable to ☠️ Toxic | 🍃 Nature
* 🔮 Mental: Vulnerable to ⚡️ Electric | 💧 Water
* ☠️ Toxic: Vulnerable to 🔮 Mental | 🔥 Fire

🔺 Elemental Strengths:

* 🔥 Fire: Dominant over 🍃 Nature | ☠️ Toxic
* 💧 Water: Dominant over 🔥 Fire | 🔮 Mental
* 🍃 Nature: Dominant over 💧 Water | ⚡️ Electric
* ⚡️ Electric: Dominant over 🔮 Mental | 💧 Water
* 🔮 Mental: Dominant over ☠️ Toxic | 🔥 Fire
* ☠️ Toxic: Dominant over ⚡️ Electric | 🍃 Nature

🌀 Element Effectiveness:

* 🟢 2.0x for strong elements (e.g., 🔥 vs. 🍃)
* 🟠 1.0x for neutral elements (e.g., 🔥 vs. ⚡)
* 🔴 0.5x for weak elements (e.g., 🔥 vs. 💧)

The game intricately weaves each element with two inherent weaknesses, meticulously ensuring a balanced power structure among elemental types. The design philosophy prohibits mutual strengths between elements, nurturing a strategic hierarchy in battles. By avoiding circular advantages, the game creates an environment that fosters engaging and tactical gameplay. In each encounter, players strategically leverage their knowledge of elemental dynamics, seizing the opportunity to gain a decisive upper hand on the battlefield.

For a comprehensive overview, consult the table below and let the journey through the elemental realms begin!<br>

| <p>DEF 👉<br>ATK👇</p> | 🔥 Fire | 🍃 Nature | 💧 Water | ⚡️ Electric | 🔮 Mental | ☠️ Toxic |
| ---------------------- | ------- | --------- | -------- | ----------- | --------- | -------- |
| 🔥 Fire                | 1.0x    | 2.0x      | 0.5x     | 1.0x        | 0.5x      | 2.0x     |
| 🍃 Nature              | 0.5x    | 1.0x      | 2.0x     | 2.0x        | 1.0x      | 0.5x     |
| 💧 Water               | 2.0x    | 0.5x      | 1.0x     | 0.5x        | 2.0x      | 1.0x     |
| ⚡️ Electric            | 1.0x    | 0.5x      | 2.0x     | 1.0x        | 2.0x      | 0.5x     |
| 🔮 Mental              | 2.0x    | 1.0x      | 0.5x     | 0.5x        | 1.0x      | 2.0x     |
| ☠️ Toxic               | 0.5x    | 2.0x      | 1.0x     | 2.0x        | 0.5x      | 1.0x     |


---

# 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://battle-docs.polychainmonsters.com/monsters/elements.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.