ВЕРСИИ (452)

# 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.

# 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.

# 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.

# 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.

# 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.

# 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.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.1 Two fixes, both from player reports. - **Sable / Create: Aeronautics — you couldn't place blocks on a sub-level.** Assembling a ship and flying it around worked, but every block and bucket was refused. Sable keeps a sub-level's blocks in a reserved area far outside the world, at a height that One Dimension's build limit read as "outside the bands" — so it blocked the placement. Building on a sub-level now works, and the build limit still applies everywhere it should. This also covers other mods that move blocks into their own space. - **Water placed with `/fill` or `/setblock` in the Nether band stayed frozen** (the `/onedimension water commands true` option added in 3.0.0). The pool survived, as intended — but it never spread, never flowed downhill, and never filled anything. Those pools now behave like water anywhere else. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 3.0.0 **You choose which dimensions are stacked, and in what order.** The stack used to be fixed — Nether, Overworld, End. Now it is a list in the config file, and any dimension can be in it, including one added by another mod. ## Building your own stack `config/codxlib.onedimension.json` gains a `stacking` section, written for you on first run: ```json "stacking": { "bands": [ { "dimension": "minecraft:the_nether", "gap": 0 }, { "dimension": "minecraft:overworld", "gap": 0 }, { "dimension": "minecraft:the_end", "gap": 688 } ] } ``` Bottom band first. `gap` is the empty space left underneath that band — the End's 688 is the void you have to cross to reach it. Drop a line to leave that dimension out of the stack and it goes back to being a normal, separate dimension with its own portal. Add a line — say `the_undergarden:undergarden` — and that dimension becomes a band of the stack instead. Rules: the Overworld must be in the list (everything else is stacked around it), no dimension twice, and the whole stack has to fit the space above and below the Overworld. If a layout can't work the world loads with the one it already had and says why in the log — it is never quietly trimmed, because a trimmed band would overlap its neighbour and wreck the terrain. **Set this before you create a world.** It is read when the world loads, but terrain that already generated does not move, so changing the layout of a world you have been playing will not end well. Existing worlds are untouched and keep the stack they were made with. The two data packs from 2.2.0 still work and are the easy way to do the common case — they simply remove the Nether or the End from whatever your list says. ## Also new - **Water in the Nether band**, if you want it — `/onedimension water nether true`, or the toggle in `/onedimension menu`. Buckets empty, ice melts, sponges stay wet, and water flowing down from the Overworld is left where it lands. - **Command-placed water** — a narrower option that lets water from `/fill`, `/setblock` and structures survive in the Nether band while poured water still fizzes: `/onedimension water commands true`. ## Fixes - **Wandering traders and pillager patrols no longer appear on the End islands.** Minecraft attaches both to the Overworld and nowhere else — which here is the whole stacked world — and both picked the highest block in the column, so a spot under an End island put them up on the island. They are kept in the Overworld band now; `/onedimension spawners false` turns that off. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.2.0 You can now split the Nether or the End back out of the stack. ## Separate the Nether or the End Two data packs ship inside the mod. Turning one on takes that dimension **out of the stacked world** and gives it back as its own normal dimension, reached through its normal portal: - **One Dimension: Separate End** — nothing generates in the End band any more, and `the_end` becomes a real, separate dimension again. Use this if you only wanted a stacked Nether and Overworld. - **One Dimension: Separate Nether** — the same, for the Nether band. Turn either one on (or both) in the **Data Packs** screen while you are creating the world; on a server, add it to `initial-enabled-packs` in `server.properties`. On Fabric the pack is called `onedimension:unstack_the_end` / `onedimension:unstack_the_nether`; on Forge and NeoForge it is `unstack_the_end` / `unstack_the_nether`. Everything else keeps working around whichever bands are left: portals, the dragon fight, the void gate, the world's build limits and the maps and shader compatibility all follow the layout you picked. Existing worlds are untouched — a world you already have loads exactly as before, and a 2.2.0 world opened in an older build still works. Removing a pack again brings the band back on the next load, with whatever terrain was already generated still on disk. ## Fixes - **Snow and ice no longer settle on the End islands.** Weather ticks were picking the highest block in the column, which is the End island whenever there is one overhead, and up at that height every biome counts as freezing. - **Flowing water no longer survives in the Nether band.** Poured water already evaporated, but water that flowed in through a hole dug down from the Overworld stayed. It now fizzes away on its first tick, exactly like a bucket does. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.

# OneDimension 2.1.1 A small fix release. - **Fixed End crystals sometimes not spawning on the obsidian pillars.** Re-summoning the Ender Dragon ran the whole respawn ritual at the End's original height instead of in the End band, so the pillars were rebuilt without their crystals — and the ritual's explosions went off down in the Overworld. Both are fixed. Requires **CodxLib 1.3.6** or newer.