Overview
Converter settings control the behavior of the conversion process, allowing you to enable or disable specific features, optimize performance, and customize how different game elements are processed.Configuration File
Converter settings are defined inconverter_settings.chunker.json or passed via the -c flag (CLI.java:234-271).
Available Settings
All settings are optional and have sensible defaults:converter_settings.chunker.json
Settings Reference
Map Conversion
Process and convert map items during conversion (CLI.java:251, 260)When disabled:
- Map items are not converted
- Map data is not processed
- Faster conversion if your world has many maps
Disabling map conversion can significantly speed up conversion for worlds with many map items.
Loot Table Conversion
Process and convert loot tables in chests, spawners, etc. (CLI.java:252, 261)When disabled:
- Loot table data is not converted
- Chest contents may not convert properly
- Spawner configurations may not transfer correctly
Item Conversion
Process and convert items in inventories, item frames, etc. (CLI.java:253, 262)When disabled:
- Items in player inventories are not converted
- Items in containers are not converted
- Item frames and other item entities are not converted
Block Connections
Process block connections and states (fences, walls, glass panes, etc.) (CLI.java:254, 263)When disabled:
- Connecting blocks may not connect properly
- Block states may be incorrect
- Faster conversion but lower visual quality
Disabling block connections improves performance but may result in fences, walls, and similar blocks not connecting properly.
Enable Compact (Bedrock)
Compact LevelDB database after conversion (Bedrock output only) (CLI.java:255, 264)When enabled:
- Bedrock worlds are compacted after conversion
- Reduces file size
- Takes additional time after conversion
- Skips compaction step
- Faster conversion completion
- Larger output file size
Compaction only applies when converting to Bedrock Edition. Java Edition conversions ignore this setting.
Discard Empty Chunks
Skip writing chunks that are completely empty (CLI.java:256, 265)When enabled:
- Empty chunks are not written to output
- Reduces output file size
- May affect world generation boundaries
- All chunks are written, even if empty
- Preserves exact world boundaries
Prevent Y Biome Blending (Java)
Prevent biomes from blending vertically (Java output only) (CLI.java:257, 266)When enabled:
- Biomes don’t blend on the Y axis
- More defined biome boundaries vertically
- May look less natural
- Natural vertical biome blending
- Smoother transitions
This setting only applies when converting to Java Edition. Bedrock conversions ignore this setting.
Complete Examples
Performance Optimized
Maximize conversion speed:converter_settings.chunker.json
Quality Focused
Maximize conversion accuracy:converter_settings.chunker.json
Minimal Conversion
Just blocks, no extras:converter_settings.chunker.json
Usage
Default Behavior
When no converter settings are provided (CLI.java:251-257):mapConversion: truelootTableConversion: trueitemConversion: trueblockConnections: trueenableCompact: truediscardEmptyChunks: falsepreventYBiomeBlending: false
You only need to specify settings you want to change from defaults.
Edition-Specific Settings
Bedrock Only
enableCompact: Only affects Bedrock output
Java Only
preventYBiomeBlending: Only affects Java output
Universal
mapConversionlootTableConversionitemConversionblockConnectionsdiscardEmptyChunks
Performance Impact
| Setting | Speed Impact | Quality Impact |
|---|---|---|
mapConversion: false | +10-20% faster | Lost map data |
lootTableConversion: false | +5-10% faster | Incorrect loot |
itemConversion: false | +15-25% faster | No items |
blockConnections: false | +20-30% faster | Incorrect connections |
enableCompact: false | +5-15% faster | Larger file size |
discardEmptyChunks: true | +5-10% faster | Smaller output |
preventYBiomeBlending: true | Minimal | Different biomes |
Performance impacts are approximate and vary based on world content.
Exporting Settings
Generate converter settings from the web UI:- Visit chunker.app
- Go to Advanced Settings → Converter Settings
- Configure your preferences
- Export the
converter_settings.chunker.jsonfile
Validation
Chunker validates converter settings during startup (CLI.java:246-270):- Unknown fields are ignored
- Invalid values fall back to defaults
- Missing settings use defaults
Combining with Other Settings
Converter settings work alongside:- Block mappings: Custom block conversions
- Pruning: Region selection
- World settings: World property changes
- Dimension mappings: Dimension routing
Best Practices
- Start with defaults and only change what you need
- Test performance settings on copies before production use
- Document your choices for future conversions
- Enable quality settings for important worlds
- Use performance settings for test conversions
Common Configurations
Quick Test Conversion
Quick Test Conversion
Production Server
Production Server
Build Showcase
Build Showcase
Troubleshooting
Settings not applying
Settings not applying
- Check JSON syntax is valid
- Verify file name is
converter_settings.chunker.json - Ensure file is in world directory or specified with
-cflag
Compaction takes too long
Compaction takes too long
- Set
"enableCompact": falseto skip compaction - Compaction time varies with world size
- Monitor console for compaction progress
Missing items after conversion
Missing items after conversion
- Ensure
"itemConversion": true - Check
"lootTableConversion": true - Verify conversion completed successfully
Related
Configuration Overview
Learn about all configuration options
Block Mappings
Customize block conversions
Pruning
Optimize world size
World Settings
Customize world properties