# Reclaim

Many servers wish to offer a /reclaim option for ranked players to gain back previously bought keys and in gam items from the past purchase. You can do this with the reclaim section of the plugin 

```
  reclaim:
    Enabled: true
    BeginAtIndex: 6 # Display Output
    permissions:
      'group_dragon':
      - 'bundle give %player% DragonReclaim 1'
      'group_king': 
      - 'bundle give %player% KingReclaim 1'  
      'group_wizard':
      - 'bundle give %player% WizardReclaim 1'
      'group_goblin':
      - 'bundle give %player% GoblinReclaim 1' 
```

{% tabs %}
{% tab title="Permissions" %}
Given YAML files use the "." key as permissions, it is not possible to use this within the configuration.

To combat this, change the period character to an underscore when placing your variables as the keys. This allows you to use default permissions which groups already have. 

In the example above, all Dragon rank members would have the group.dragon permission. To use this with our reclaim, it becomes "group\_dragon". ServerTools will correctly swap the underscore back to a period as needed.
{% endtab %}

{% tab title="BeginAtIndex" %}
This is the index at which the command will print the values of the Reclaim prize based on the permission**.** 

As seen above, "**group\_**dragon" - we do not want to show this to the user upon claiming. By beinging the index at 6 we skip the "group\_" value and only show DRAGON to them.

It is advised to leave this at 6 if you are using Luckperms group permissions. If not, change to 0 and increase as needed

![Reclaim Bundle](/files/-MlVp-ZlxaMSWMNlG_eN)
{% endtab %}
{% endtabs %}

 


---

# Agent Instructions: 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:

```
GET https://servertools.reece.sh/configurations/how-to/reclaim.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.