# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.1.0 A release about the stack itself: how tall it is allowed to be, what happens when it doesn't fit, and what you can find out from the log when your terrain looks wrong. Everything here came from player reports — thank you. ## The world can be taller now `stacking.worldHeight` in `config/codxlib.onedimension.json` picks one of three sizes: | Value | Room below the Overworld band | Room above it | |---|---|---| | `"normal"` *(default, unchanged)* | 256 blocks | 960 blocks | | `"tall"` | 960 blocks | 1712 blocks | | `"extreme"` | 1968 blocks | 1712 blocks | That is the answer to **"my End won't go higher than about y 1000"** and to **stacking more than one dimension on a side**: `"normal"` has exactly enough room for one vanilla Nether below and one vanilla End above, and nothing was ever going to fit past it. Set this **before** you generate the world — a taller world costs memory, and changing it later leaves the chunks you already made where they are. Your client's setting is ignored when you join a server; the server's height wins, so a `"tall"` client can still join a `"normal"` server. ## When the stack doesn't fit, the gaps go first Previously a layout that was too tall either refused to load or was quietly trimmed — and trimming cuts terrain off the top of a band. Now the **empty space between bands is spent first** (largest gap first), so every band keeps its full terrain, and a warning in the log names exactly what changed and tells you which `worldHeight` would have avoided it. ## Fixes - **Only the band directly under the Overworld generated correctly** when you stacked two or more dimensions below it — the ones further down took the band above's biomes and mobs. Bands are now matched outward from the Overworld, so every band answers for itself. - **A modded band above the Overworld got the End's starless sky** — the Aether, for example. Only the End band and the empty gaps between bands use that sky now; a modded band keeps a normal one. (Its own custom sky is still on the list.) - **Removed a misleading warning** about `minecraft:overworld` "no longer being a separate dimension". ## New settings - **`stacking.barrierThickness`** — how thick the obsidian floor under the Overworld is. `0` (default) is the ragged vanilla-shaped layer you have now; `1` or more lays a flat obsidian slab that many blocks thick. - **`blockBuildingAboveOverworld`** — off by default. Turn it on and nothing can be *placed* at or above the top of the Overworld band, so nobody can tower up through the Void Gate into the band above. Breaking is untouched, so it can't strand anyone. Also `/onedimension buildceiling <true|false>` and a toggle in `/onedimension menu`. ## If your terrain looks wrong, the log now says why Every world load prints the layout it actually built: ``` One Dimension bands, bottom to top: minecraft:the_nether -192..-65 via …[minecraft:nether, MultiNoiseBiomeSource], minecraft:overworld -64..319 (anchor) via …[minecraft:overworld, MultiNoiseBiomeSource], … ``` Every band, its exact heights, and which generator and biome source ended up running it — including when a datapack or another mod replaced one. **If you are reporting bad generation, please include that line and any warning next to it.** Two open reports about a missing Overworld are waiting on exactly this. Requires **CodxLib 1.3.6** or newer.