> For the complete documentation index, see [llms.txt](https://riventide.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://riventide.gitbook.io/whitepaper/gameplay/core-concepts.md).
# Core Concepts
DISCLAIMER: All content here in is subject to change as the meta evolves through development, testing, and community feedback. No part of the Whitepaper is to be copied
#### Elements
Each Monster is associated with either two Elements, or the Wild Element. These determine which Actions a Monster can learn. Elements in Riventide do not have any weaknesses or strengths like in other games.
#### Riven
Riven is the resource used to take Actions. Riven is generated at the beginning of each turn, or through various Traits and Actions.
#### Types
Each Monster is associated with three different Types. These types define what roles the Monster plays in battle as well as what Traits are available for them.
#### Skills
Each Monster learns a new Skill every Level. These are either Traits or Actions that affect what they can do in combat. Each Monster also has their own unique Signature Trait.
#### Poise
Each enemy Monster has what is referred to as Poise. Breaking a Monster's Poise will Stagger them, which can be useful for blocking attacks.
#### Corruption
During combat, if the player's Monster gets hit and takes damage, it will gain some Corruption. Accumulated Corruption will reduce the starting health of the Monster at the beginning of the next battle.
---
# 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://riventide.gitbook.io/whitepaper/gameplay/core-concepts.md?ask=&goal=
```
`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.
