> For the complete documentation index, see [llms.txt](https://captain-tsubasa-rivals.gitbook.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captain-tsubasa-rivals.gitbook.io/en/pvp-mode/rival-piece.md).

# Reward: Rival Cards

## Rewards: Rival Pieces

* If the user wins a PvP match, the winner will receive the target Rival Piece, while the loser will lose the target Rival Piece.
* If the user loses the match, the rival pieces cannot be taken away and the rival piece of the winning opponent remains the same.

### Rival Cards/Pieces

Each of the six divided Rival Cards is a Rival piece.

Once you complete a Rival Card out of 6 Rival Pieces of the same type, you can take part in a Gacha for rewards.

The rewards obtained as a result of the Gacha depend on the type of rival card:

* PvP Only Player NFT
* Player NFT
* Support Character 
* MintCountDown Item
* Point Reset Item 
* Command Card Reset Item 
* Proficiency Level Reset Item 
* Proficiency Level Upper Limit Breakthrough Item 
* PvP Buff Ticket 
* Mint Scroll
* Proficiency     etc.


---

# 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://captain-tsubasa-rivals.gitbook.io/en/pvp-mode/rival-piece.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.