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

# 💰 Rachats

💰 Revendez certaines de vos ressources et gagnez des CobbleDollars pour développer votre aventure sur CobbleRealm !

### 💰 Le Rachat

Sur CobbleRealm, certains objets peuvent être revendus afin de gagner des CobbleDollars. 🪙

### 📍 Où vendre vos objets ?

Un seul PNJ « RACHATS » est disponible sur le serveur.

Vous pouvez le retrouver au Spawn. 🏠

Approchez-vous du PNJ « RACHATS » et interagissez avec lui pour ouvrir le menu de vente.

### 💰 Comment vendre ?

1. Rendez-vous au PNJ « RACHATS » au Spawn.
2. Interagissez avec le PNJ.
3. Consultez les objets pouvant être revendus.
4. Vendez vos objets pour recevoir des CobbleDollars. 🪙

### 🛒 Objets actuellement rachetés

Le PNJ « RACHATS » vous permet actuellement de revendre les objets suivants :

• Poké Ball — 10 CobbleDollars

• Rappel — 25 CobbleDollars

• Rappel Max — 60 CobbleDollars 

• Potion — 10 CobbleDollars 

• Super Potion — 10 CobbleDollars 

• Hyper Potion — 10 CobbleDollars

💡 Bon à savoir

Les objets disponibles au rachat ainsi que leurs prix peuvent évoluer au fil des mises à jour de CobbleRealm. ⚡


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cobblerealm.gitbook.io/cobblerealm-docs/rachats/rachats.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.