> For the complete documentation index, see [llms.txt](https://docs.cheddah-development.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheddah-development.net/plugin-documentaion/skin-statues/commands-and-permissions.md).

# Commands and Permissions

Commands must be run by an in-game player. The console cannot create or undo a statue because placement depends on the player's location and facing direction.

### Commands

<table><thead><tr><th width="225.6910400390625">Command</th><th>Description</th></tr></thead><tbody><tr><td><code>/statue &#x3C;name> &#x3C;scale></code></td><td>Creates a statue from the named Minecraft player's skin</td></tr><tr><td><code>/statue undo</code></td><td>Restores the blocks replaced by your latest completed statue</td></tr></tbody></table>

The scale must be a whole number between `1` and the configured maximum. The default maximum is `4`.

### Paper permission

Both commands require:

```
skinstatues.use
```

This permission is granted to server operators by default. A permissions plugin can grant it to another trusted player or staff group.

{% hint style="warning" %}
The same permission allows both creation and undo. SkinStatues does not provide separate permissions for different scales or worlds.
{% endhint %}

### Fabric permission

Both commands require vanilla game-master permission level 2. Fabric does not use the `skinstatues.use` Bukkit permission.

### Protection plugins and claims

SkinStatues does not integrate with region, claim, or protection plugins. Its own command permission is the access boundary. Only grant access to players you trust to replace blocks in the areas where they stand.


---

# 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.cheddah-development.net/plugin-documentaion/skin-statues/commands-and-permissions.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.