Skip to main content

​
Overview

All configuration settings are defined in the ConfigData class (Config.java:51-59). Each setting controls a specific aspect of chunk generation behavior, performance, or visual features.

​
General Settings

​
enabled

​
enabled
boolean
default:"true"
Master toggle for the entire mod. When set to false, Voxy World Gen V2 will not generate any chunks.Use case: Temporarily disable chunk generation without uninstalling the mod.Implementation: Checked in the worker loop (ChunkGenerationManager.java:163) before processing any generation tasks.
{
  "enabled": true
}

​
showF3MenuStats

​
showF3MenuStats
boolean
default:"true"
Controls whether generation statistics are displayed in the F3 debug menu.Statistics shown:
  • Active generation tasks
  • Chunks remaining in radius
  • Generation rate (chunks/second)
  • Queue statistics
  • Throttle status
Use case: Hide debug information for cleaner screenshots or reduce visual clutter.
{
  "showF3MenuStats": true
}

​
Generation Settings

​
generationRadius

​
generationRadius
integer
default:"128"
The radius (in chunks) around each player where LOD chunks will be generated.Range: 1-512 chunks (ModMenuIntegration.java:34)Calculation: The total generation area is a square with side length 2 * generationRadius + 1.Example: A radius of 128 generates a 257x257 chunk area (65,536 total chunks).Special behavior: When using Tellus integration, the minimum radius is automatically enforced to 128 chunks, even if you set a lower value (ChunkGenerationManager.java:185, 201).
{
  "generationRadius": 128
}
Larger radius values exponentially increase the number of chunks to generate. A radius of 256 generates 4x more chunks than radius 128.

​
update_interval

​
update_interval
integer
default:"20"
Legacy compatibility field preserved for backwards compatibility.Status: This setting is no longer actively used by the current generation system but is retained to prevent config parsing errors when upgrading from older versions.Range: 1-200 (ModMenuIntegration.java:40)Note: You can safely ignore this setting. It has no effect on current mod behavior.
{
  "update_interval": 20
}
This field will be removed in a future major version. It’s safe to leave at the default value.

​
Performance Settings

​
maxQueueSize

​
maxQueueSize
integer
default:"20000"
Maximum number of chunks that can be queued for generation.Purpose: Prevents unbounded memory growth by limiting the generation queue size.Behavior: When the queue is full, new generation requests are deferred until space becomes available.Memory impact: Higher values increase memory usage but allow smoother generation when moving quickly.Recommended range: 10,000-50,000 depending on available RAM.
{
  "maxQueueSize": 20000
}

​
maxActiveTasks

​
maxActiveTasks
integer
default:"20"
Maximum number of concurrent chunk generation tasks.Range: 1-128 (ModMenuIntegration.java:52)Purpose: Controls CPU utilization by limiting parallel generation.Implementation: Uses a Semaphore to throttle concurrent tasks (ChunkGenerationManager.java:69, 109).Auto-configuration: Set to 20 by default during first-run hardware detection (Config.java:26).Performance impact:
  • Higher values: Faster generation, higher CPU usage
  • Lower values: Slower generation, lower CPU usage
Recommended values:
  • 4-8 cores: 15-25 tasks
  • 8-16 cores: 25-50 tasks
  • 16+ cores: 50-100 tasks
{
  "maxActiveTasks": 20
}
Setting maxActiveTasks too high can cause lag or stuttering. Monitor your TPS (ticks per second) and adjust accordingly.

​
Storage Settings

​
saveNormalChunks

​
saveNormalChunks
boolean
default:"true"
Controls whether LOD chunks are saved to disk like normal Minecraft chunks.When enabled (true):
  • LOD chunks are saved to the world’s region files
  • Chunks persist across world reloads
  • Increased disk space usage
  • Faster loading on subsequent plays
When disabled (false):
  • LOD chunks are marked as unsaved (ChunkGenerationManager.java:326)
  • Chunks are tracked internally via LodChunkTracker
  • Minimal disk space usage
  • Chunks regenerate on world reload
  • Increment skipped chunk counter (ChunkGenerationManager.java:327)
Disk space impact: Disabling can save several gigabytes for large generation radii.Use case: Disable for temporary preview worlds or when disk space is limited.
{
  "saveNormalChunks": true
}
When saveNormalChunks is false, all generated LOD chunks will be lost when you reload the world. They must be regenerated, which takes time.
For long-term survival worlds, keep saveNormalChunks enabled. For temporary exploration or preview worlds, disable it to save disk space.

​
Complete Configuration Example

{
  "enabled": true,
  "showF3MenuStats": true,
  "generationRadius": 128,
  "update_interval": 20,
  "maxQueueSize": 20000,
  "maxActiveTasks": 20,
  "saveNormalChunks": true
}

Configuration Overview

Learn about the config system and ModMenu integration

Advanced Configuration

Hardware tuning and performance optimization strategies

Build docs developers (and LLMs) love

Get started for freeTalk to us