-
Notifications
You must be signed in to change notification settings - Fork 4
Configuration
Chunk By Chunk's configuration can be found in 2 places:
defaultconfigs/chunkbychunk.toml
- this is the location of the config that will be applied to any new worlds that are created. This is also the configuration modified in game through the mods menu (in forge, or in fabric with the Mod Menu mod installed).
[world]/serverconfig/chunkbychunk.toml
- this is where world specific configuration is stored for each world or save. This cannot be modified in game, as changing some settings will result in unpredictable results.
In both cases the configuration has the same format - it is a toml (Tom's Obvious Minimal Language) with the following sections and options.
enabled
- true | false - if false, entirely disables the sky/sealed generation of Chunk By Chunk. Probably mostly useful either if wanting to have both normal and Chunk By Chunk worlds in the same Minecraft install, or for mod packs wanting to use the World Scanner and nothing else.
seal_world
- true | false - if true, the overworld will be generated as a bedrock heightmap. Otherwise the overworld will be generated as an empty skyworld.
synch_nether_chunk_spawn
- true | false - if true, the nether will spawn chunks synchronized with those being spawned in the overworld. That is, whenever an overworld chunk is spawned the overworld chunk that it would connect to in the nether will be spawned if missing. If false then then the nether will be empty and needs to be built out with chunk spawners.
spawn_new_chunk_chest
- true | false - if true, enables the spawning of a chest at the bottom of chunks containing items as configured below.
spawn_chest_in_initial_chunk_only
- true | false - if true, the chest will only spawn in the first chunk spawned in the overworld.
use_bedrock_chest
- true | false - if true, the chest will be a special bedrock chest that can only be opened if the number of blocks above it in the chunk is below a desired amount (configured below in the BedrockChest section).
chest_contents
- ChunkSpawner | WorldCore | WorldCrystal | WorldForge | UnstableChunkSpawner - The item that will be found in the chest.
chest_quantity
- 1 to 64 - the quantity of the item that will be found in the chest.
min_chest_spawn_depth
- -64 to 128 - the minimum (lowest) depth the chest can be found at.
max_chest_spawn_depth
- -64 to 128 - the maximum (highest) depth the chest can be found at.
initial_chunks
- 1 to 9 - how many chunks will initially be spawned in the overworld.
block_placement_allowed_outside_spawned_chunks
- true | false - are players able to place blocks outside of spawned chunks?
start_in_village
- true | false - if true will attempt to move spawn to a village and produce the initial chunks there. Final spawn may not be in the village itself if the village cannot support desired initial chunk conditions (a tree and other minimum material requirements for a chunk spawner).
starting_biome
- A tag or name of a preferred biome for the initial chunk(s). Ignored if start_in_village is true. Tags must start with a hash (e.g. #minecraft:is_forest
).
production_rate
- 1 to 256 - The rate at which the world forge processes consumed blocks, in fuel per tick.
soil_fuel_value
- 0 to 256 - The fuel provided by dirt and equivalently tagged blocks.
stone_fuel_value
- 0 to 256 - The fuel provided by stone and equivalently tagged blocks.
strong_fuel_value
- 0 to 256 - The fuel provided by strong fuel tagged blocks. There aren't any by default, this is provided to support modpacks.
fragment_fuel_cost
- 1 to 256 - How much fuel is required to generate a world fragment.
fuel_per_fragment
- 1 to 512 - How much scanning fuel is provided by a world fragment. World shards, crystals and cores provide 4, 16 and 256 times as much fuel respectively.
fuel_required_per_chunk
- 1 to 65534 - How much fuel is required to scan each chunk.
fuel_consumed_per_tick
- 1 to 65534 - How much fuel is consumed per tick (20 ticks per second). Together with fuel required per chunk this determines how long it takes to scan each chunk.
bedrock_chest_unlock_at_blocks_remaining
- 0 to 65534 - How few blocks can remain in the chunk above the bedrock chest before it can be opened.