Overview
World settings allow you to customize world-level properties during conversion. This includes game rules, difficulty, spawn points, and other world metadata that gets embedded in the level.dat or equivalent file.Configuration File
World settings are defined inworld_settings.chunker.json or passed via the -s flag (CLI.java:163-182).
File Structure
World settings are stored as a JSON object containing key-value pairs (CLI.java:177):world_settings.chunker.json
World settings are applied directly to the world data structure. The available fields depend on the output edition and version.
Common Settings
While the exact fields available depend on the target edition, here are commonly used settings:World Name
Difficulty
0: Peaceful1: Easy2: Normal3: Hard
Game Mode
0: Survival1: Creative2: Adventure3: Spectator
Hardcore Mode (Java)
Spawn Position
Time
0: Dawn6000: Noon12000: Dusk18000: Midnight
Game Rules
Game rules can also be configured:Game rule values must be strings (
"true" or "false"), not booleans.Complete Examples
Peaceful Creative World
world_settings.chunker.json
Hardcore Survival
world_settings.chunker.json
Adventure Map
world_settings.chunker.json
Skyblock Setup
world_settings.chunker.json
Usage
Java vs Bedrock Differences
Java Edition Specific
Bedrock Edition Specific
Universal Settings
Field Format
World settings use the underlying NBT format field names:- Field names are case-sensitive
- Integer values: Use numbers (
2, not"2") - Boolean values: Use booleans (
true, not"true") - Game rules: Use strings (
"true", nottrue)
Common Game Rules
| Rule | Description | Default |
|---|---|---|
keepInventory | Keep items on death | false |
doDaylightCycle | Sun and moon move | true |
doWeatherCycle | Weather changes | true |
doMobSpawning | Mobs spawn naturally | true |
mobGriefing | Mobs can destroy blocks | true |
naturalRegeneration | Health regenerates | true |
commandBlockOutput | Show command block output | true |
doFireTick | Fire spreads | true |
showDeathMessages | Show death messages | true |
announceAdvancements | Announce advancements | true |
Game rule availability varies by edition and version. Some rules only exist in Java or Bedrock.
Validation
Chunker applies world settings during conversion (CLI.java:175-181):- Valid settings are applied to the output world
- Invalid or unknown fields are typically ignored
- Type mismatches may cause errors
Discovering Available Settings
To find available settings for your target version:- Create a world in the target edition/version
- Use NBT editors like NBTExplorer or Amulet
- Examine the level.dat file structure
- Use those field names in your world_settings.chunker.json
Exporting Settings
Generate world settings from the web UI:- Visit chunker.app
- Go to Advanced Settings → Converter Settings
- Configure world properties
- Export the
world_settings.chunker.jsonfile
Partial Updates
You only need to specify settings you want to change:Overriding Original Settings
World settings override values from the input world:- Input world has
Difficulty: 2 - Settings file has
Difficulty: 0 - Output world will have
Difficulty: 0
Best Practices
- Test on copies before applying to production worlds
- Use minimal settings - only change what you need
- Document your settings for future reference
- Check edition compatibility - some settings are edition-specific
- Validate field names using NBT editors
Common Use Cases
Reset Difficulty
Change world difficulty after conversion
Fix Spawn Point
Set correct spawn coordinates
Rename World
Give converted world a new name
Configure Rules
Set game rules for maps or servers
Troubleshooting
Settings not applying
Settings not applying
- Check JSON syntax is valid
- Verify field names are spelled correctly (case-sensitive)
- Ensure value types match expected format
- Check that the setting is supported by target edition
Conversion fails with settings error
Conversion fails with settings error
- Validate JSON structure
- Remove invalid or unknown fields
- Check for type mismatches (number vs string)
- Test with minimal settings first
Game rules not working
Game rules not working
- Ensure game rule values are strings:
"true"nottrue - Check game rule name spelling
- Verify the rule exists in target edition/version
World name unchanged
World name unchanged
- Ensure using
LevelNamenotlevelName(case matters) - Check file is being loaded (use
-sflag to verify) - Try setting in web UI and exporting configuration
Advanced Settings
World Generation
World Border
Version Info
Advanced settings should be used with caution. Incorrect values can cause world corruption or loading issues.
Related
Configuration Overview
Learn about all configuration options
Converter Settings
Control conversion behavior
Dimension Mapping
Map dimensions between editions