Configuration Guide

Customize LilChunks to perfectly fit your server’s needs with our comprehensive configuration options.

Configuration File Location

The main configuration file is located at:
plugins/LilChunks/config.yml
After making changes to the configuration, use /lilchunks reload to apply them without restarting the server.

Default Configuration

Here’s the complete default configuration with explanations:
# LilChunks Configuration

# Debug mode - enables additional logging
debug: false

# Chunk generation settings
chunk-generation:
  # Maximum chunks to generate per tick
  chunks-per-tick: 4
  
  # Whether to use async chunk generation (1.17+)
  use-async: true
  
  # Whether to generate structures
  generate-structures: true
  
  # Whether to generate caves
  generate-caves: true
  
  # Whether to generate features (trees, ores, etc.)
  generate-features: true

# World settings
world-settings:
  # Default world height (1.17+)
  min-height: -64
  max-height: 320
  
  # Whether to respect world-specific height settings
  respect-world-height: true

# Performance settings
performance:
  # Maximum memory usage in MB (0 for unlimited)
  max-memory-usage: 0
  
  # Whether to use parallel chunk generation
  use-parallel: true
  
  # Number of threads to use for chunk generation (0 for auto)
  thread-count: 0

# Logging settings
logging:
  # Whether to log chunk generation progress
  log-progress: true
  
  # Progress update interval in seconds
  progress-interval: 5
  
  # Whether to log detailed chunk information
  detailed-logs: false

Configuration Sections

Debug Settings

Chunk Generation Settings

World Settings

Performance Settings

Logging Settings

Performance Profiles

Here are pre-configured profiles for different server types:

High-Performance Server

For powerful dedicated servers:
chunk-generation:
  chunks-per-tick: 8
  use-async: true
  generate-structures: true
  generate-caves: true
  generate-features: true

performance:
  max-memory-usage: 0
  use-parallel: true
  thread-count: 0

logging:
  log-progress: true
  progress-interval: 3
  detailed-logs: false

Balanced Server

For most shared hosting and VPS:
chunk-generation:
  chunks-per-tick: 4
  use-async: true
  generate-structures: true
  generate-caves: true
  generate-features: true

performance:
  max-memory-usage: 2048
  use-parallel: true
  thread-count: 0

logging:
  log-progress: true
  progress-interval: 5
  detailed-logs: false

Low-Resource Server

For budget hosting or limited resources:
chunk-generation:
  chunks-per-tick: 2
  use-async: true
  generate-structures: true
  generate-caves: true
  generate-features: true

performance:
  max-memory-usage: 1024
  use-parallel: false
  thread-count: 1

logging:
  log-progress: true
  progress-interval: 10
  detailed-logs: false

Speed-Optimized

For fastest generation (may cause lag):
chunk-generation:
  chunks-per-tick: 12
  use-async: true
  generate-structures: false
  generate-caves: false
  generate-features: false

performance:
  max-memory-usage: 0
  use-parallel: true
  thread-count: 0

logging:
  log-progress: true
  progress-interval: 2
  detailed-logs: false

Configuration Validation

LilChunks validates your configuration on startup and reload:

Valid Configuration

[LilChunks] Configuration loaded successfully
[LilChunks] Using 4 chunks per tick with async generation

Invalid Configuration

[LilChunks] WARNING: Invalid chunks-per-tick value: 25 (max: 20)
[LilChunks] Using default value: 4

Advanced Configuration

Environment-Specific Settings

You can create different configurations for different environments:
debug: true
chunk-generation:
  chunks-per-tick: 1
logging:
  detailed-logs: true
  progress-interval: 1

Configuration Management

1

Backup Configuration

Always backup your configuration before making changes:
cp plugins/LilChunks/config.yml plugins/LilChunks/config.yml.backup
2

Test Changes

Test configuration changes on a development server first.
3

Apply Changes

Use the reload command to apply changes:
/lilchunks reload
4

Monitor Performance

Watch server performance after configuration changes.

Troubleshooting Configuration

Configuration Best Practices

Start Conservative

Begin with lower performance settings and gradually increase based on server capacity.

Monitor Resources

Watch CPU, memory, and TPS during generation to find optimal settings.

Test Changes

Always test configuration changes on a development server first.

Document Settings

Keep notes about what settings work best for your server setup.

Next Steps