---
description: >-
  The following properties are utilized by the plugin engine during generation
  and world-saving.
---

# Common generator properties

## Default generator file

```yaml
generator.default-gen: eden.yml
```

Specify the name of the default generator YAML file if no one is specified.

***

## Cache size

```yaml
generator.cache-size: 8192
```

Specify, the maximum size of the chunks' cache that will be kept in memory.

<table data-view="cards"><thead><tr><th></th><th>Value</th><th>Memory usage</th></tr></thead><tbody><tr><td><mark style="color:green;"><strong>Default value</strong></mark></td><td>8192</td><td>~1.5 GB of RAM</td></tr><tr><td><mark style="color:yellow;"><strong>Minimum value</strong></mark></td><td>256</td><td>less ram possible</td></tr><tr><td><mark style="color:red;"><strong>Maximum value</strong></mark></td><td>No limits</td><td>depending on your value</td></tr></tbody></table>

{% hint style="info" %}
The larger this value, the faster the generation will be and there will be a limited amount of disk I/O.
{% endhint %}

{% hint style="info" %}
Performing an intensive chunk generation using Chunky, WorldBorder, or similar plugins can result in a cache overload. This implies that during extensive generation, approximately 6 GB or more of RAM might be utilized, leading to significant disk I/O. If your system doesn't have sufficient RAM, consider lowering the generation speed.
{% endhint %}

***

## Async placer

```yaml
generator.async-placer.enabled: true
```

Enable or disable the async chunks placer. This feature cleans the database by placing stored chunks from the world's database.

{% hint style="info" %}
It is beneficial with large worlds that require much time to load.
{% endhint %}

### Chunks

```yaml
generator.async-placer.chunks: 50
```

The number of stored chunks that can be placed to the generated chunks.

<table data-view="cards"><thead><tr><th></th><th>Value</th></tr></thead><tbody><tr><td><mark style="color:green;"><strong>Default value</strong></mark></td><td>50</td></tr><tr><td><mark style="color:yellow;"><strong>Minimum value</strong></mark></td><td>1</td></tr><tr><td><mark style="color:red;"><strong>Maximum value</strong></mark></td><td>1000</td></tr></tbody></table>

{% hint style="info" %}
Enabling an aggressive chunk placement can lead to server overload. If this value exceeds 100 (depending on your hardware), it may result in increased usage of RAM and CPU resources.
{% endhint %}

### Forced

```yaml
generator.async-placer.forced: false
```

If false, the async placer will be executed when there are no online players.

{% hint style="info" %}
If you wish to set this property to true, ensure that you assign a very low number of chunks to be placed. Otherwise, it could lead to server overhead and lag. For example, you might consider doing this during the server's development phase when lag is not a critical concern.
{% endhint %}
