> 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/configuration.md).

# Configuration

SkinStatues works with its default settings. Restart the server after editing the configuration; there is no built-in reload command.

### Paper configuration

Paper stores its settings in:

```
plugins/SkinStatues/config.yml
```

The default file is:

```yaml
max-scale: 4
blocks-per-tick: 2500
outer-layer: true
skin-cache-minutes: 60

palette:
  excluded: []
  extra: {}
```

Missing keys are restored from the packaged defaults without overwriting values you changed.

### Fabric configuration

Fabric stores its settings in:

```
config/skinstatues.json
```

The default file is:

```json
{
  "maxScale": 4,
  "blocksPerTick": 2500,
  "outerLayer": true,
  "skinCacheMinutes": 60,
  "palette": {
    "excluded": [],
    "extra": {}
  }
}
```

If the JSON file cannot be parsed, SkinStatues reports the problem in the server log and uses built-in defaults for that startup. It leaves the malformed file unchanged so you can correct it.

### Settings

#### Maximum scale

Paper: `max-scale`\
Fabric: `maxScale`

Sets the largest value accepted by `/statue <name> <scale>`.

* Default: `4`
* Allowed range: `1` to `16`

Values outside the range are limited to the nearest valid value. Scale increases the size of every skin pixel in all three dimensions, so raise this limit cautiously.

#### Blocks per tick

Paper: `blocks-per-tick`\
Fabric: `blocksPerTick`

Sets the maximum number of block snapshots processed during each server tick while building or undoing.

* Default: `2500`
* Allowed range: `1` to `50000`

Lower the value if large statues cause noticeable tick delays. Raise it if you prefer faster builds and your server can handle more world changes per tick.

#### Outer layer

Paper: `outer-layer`\
Fabric: `outerLayer`

Controls rendering of hats, jackets, sleeves, and pants.

* Default: `true`
* `true`: render a thin outer shell
* `false`: build only the base skin layer

#### Skin cache lifetime

Paper: `skin-cache-minutes`\
Fabric: `skinCacheMinutes`

Controls how long a successfully resolved skin remains in memory.

* Default: `60` minutes
* Allowed range: `0` to `1440` minutes
* `0`: disable normal success caching

Failed lookups are always remembered for one minute to prevent repeated requests from command spam. The cache is cleared when SkinStatues stops.

#### Palette

The `palette.excluded` and `palette.extra` settings control which blocks may be chosen for skin colors. See Palette customization.

### Applying changes

1. Stop the server.
2. Edit the correct file for your platform.
3. Start the server.
4. Review the startup log for ignored materials, invalid colors, or malformed settings.
5. Build a scale-1 test statue in a safe area.


---

# 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/configuration.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.