> For the complete documentation index, see [llms.txt](https://docs.codersky.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codersky.net/customanvils/features/custom-repair-costs.md).

# Custom repair costs

Since 1.0.0

While the name of this feature is custom **repair** costs, the limitations actually apply to every xp level cost that anvils may require such as adding new enchantments to an item or changing its name, not only item repairs. This may be the most confusing feature of the plugin to the user because of how the client decides to display the "<mark style="color:red;">Too expensive!</mark>" message to the player. The client will do this whenever a repair cost goes over 40 xp levels, no matter if the server allows the repair to actually be done, the actual cost however will be displayed without issues on creative mode. CustomAnvils provides two different approaches to fix this issue with the following configuration values:

```yaml
repairCost:
  max: 40
  limit: -1
```

<mark style="color:purple;">**max**</mark> represents the maximum xp level cost that the server will allow, Minecraft has this set to 40 by default, however you can go over that by setting this value to let's say 50, this will allow players to do actions on the anvil that would cost for example 45 levels, however, keep in mind that the client will still display the "<mark style="color:red;">Too expensive!</mark>" message, even though the action will be allowed. <mark style="color:purple;">**limit**</mark> on the other hand actually limits the maximum cost of the anvil so it can't go over a certain amount of xp levels, so if you set it to let's say 40, the anvil will **NEVER** ask for more than 40 xp levels, period. No matter how many times you modify an item, -1 will prevent the plugin from limiting costs.