> For the complete documentation index, see [llms.txt](https://docs.remonster.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remonster.world/play-guide/open-beta/pvp/rnked-match.md).
# Rnked Match
The battle will be a Ranked Match where players can earn Cycle Score and Daily Score by battling.
Battle Counts of Monsters in the party are consumed during battles, but they do not affect the training parameters.
The score will increase even if the player loses the battle, but it will decrease significantly compared to the score when the player wins. In addition, the score earned will rise or fall depending on the cycle score of the opponent and the difference in the party's total overall ability.
1. Current cycle
2. Period of the current cycle
3. Current cycle's Ranked Match Score and Ranking
4. This week's Ranked Match Rankings and Daily Score Earned
5. Previous Ranked Match results (including prize Ranked Matches)
6. Your last 6 Ranked Match results
7. Rank selection for Ranked Match\
-Higher ranks are released according to the current player rank.\
-In addition, basic parameters and skill cost will be capped according to the rank set.
8. Start matching
---
# 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://docs.remonster.world/play-guide/open-beta/pvp/rnked-match.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.