All Mods Resource Packs Data Packs Shaders Modpacks Plugins
One Dimension

One Dimension

by Unknown • Downloads: 0 • Followers: 0
Description
Gallery
Changelog
Versions

Buy me a coffee

OneDimension

The Nether, the Overworld and the End — stacked into a single dimension.

OneDimension adds one new world type. Select "One Dimension" when creating a world and you get all three vanilla realms fused into one literal dimension, stacked by height. No portals to separate dimensions — dig down far enough and you punch through into the Nether; build up high enough and you reach the End. It's all one continuous world.

How it's stacked

From bottom to top, in a single 1536-block-tall dimension:

Band Where What
The End near the world ceiling Floating islands, the dragon fight, End cities
The Void Gate high above the surface A dark, damaging stretch you must cross to reach the End (lifted once the dragon falls)
Overworld normal Y (−64…319) Your familiar world — unchanged coordinates
Obsidian floor beneath the surface The one mineable barrier; the Nether ceiling sits flush right under it
Nether far below Native Nether terrain, biomes, fortresses, fast-flowing lava — on a solid bedrock world floor

The Overworld keeps its exact vanilla coordinates, so everything you know still works at the heights you expect.

What you get

  • A real stacked world — genuine Nether, Overworld and End terrain, each generated by vanilla worldgen, in one dimension.
  • Per-band biomes, mobs, features and structures — End cities and Nether fortresses generate in their bands and /locate finds them. Nether basalt/fire/ fungus and End chorus all grow where they should.
  • The full dragon fight — the bedrock fountain and all ten spikes build high in the End band, the dragon spawns, fights and dies as normal, and the end credits roll when you enter the exit portal.
  • In-world portals — End and Nether portals warp you within the stacked dimension (up to the End platform, down to the Nether) instead of to a separate one.
  • The Void Gate — an escalating-damage band (with a hard death zone) between the surface and the End, so reaching the top is a real journey — lifted for good once you defeat the dragon, opening a walk-up route to the End.
  • Real Nether lava — flows fast and far in the Nether band, just like a normal Nether; Overworld lava stays slow.
  • Vanilla-accurate dimension quirks — beds explode in the Nether and End bands (but work in the Overworld), and the Overworld band has a normal day/night cycle and working clocks.
  • A dig path to the Nether — break through the mineable obsidian floor to descend.
  • Correct atmospherics per band — Overworld lighting, sky, fog and rain; the End has its proper dark sky and fog with a full view distance; an ominous near-black fog in the Void Gate between; no clouds up top; a brighter Nether. The dragon only shows once you're up in the void zone or the End.

Admin controls

OPs can tune the Void Gate's hazards on the fly:

  • /onedimension menu — a chest-menu panel (works on a vanilla client) with toggles for the void damage and the instant-death band.
  • /onedimension voidgate damage|deathband <true|false> — toggle each hazard independently from the command line. Both are also editable in the config file.

Known issues

  • It's a tall dimension, so it's heavier than a normal world. Allocating more RAM (4 GB+) is recommended, especially at high render distances.

Starting a server

Make sure to set the level-type to onedimension:one_dimension and delete the existing world, start the server and it should generate a one dimension world.

How to Install One Dimension (Mod)

One Dimension by Unknown is verified for Fabric, Forge, Neoforge across Minecraft versions 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1 (latest release: 3.1.0+26.2-neoforge, file size: 196 KB). Follow the steps below to install it safely from ModCraft.tv:

  1. Click the Download button above and select your Minecraft version (1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6, 1.21, 1.21.1) and platform (Fabric, Forge, Neoforge).
  2. Make sure you have the compatible loader or environment installed for Fabric, Forge, Neoforge.
  3. Move the downloaded One Dimension file into your Minecraft .minecraft/mods folder and launch the game.

All Versions

+ Add Version
Name Game version Platforms Published Downloads Actions
26.2
Neoforge
2mo ago 1
26.2
Forge
2mo ago 1
26.1.2
Neoforge
2mo ago 1
26.1.2
Forge
2mo ago 1
26.1.2
Fabric
2mo ago 1
26.1.1
Neoforge
2mo ago 1
26.1.1
Forge
2mo ago 1
26.1.1
Fabric
2mo ago 1
26.1
Neoforge
2mo ago 1
26.1
Forge
2mo ago 1
26.1
Fabric
2mo ago 1
1.21.11
Neoforge
2mo ago 1
1.21.11
Forge
2mo ago 1
1.21.11
Fabric
2mo ago 1
1.21.10
Neoforge
2mo ago 1
1.21.10
Forge
2mo ago 1
1.21.10
Fabric
2mo ago 1
1.21.9
Neoforge
2mo ago 1
1.21.9
Forge
2mo ago 1
1.21.9
Fabric
2mo ago 1
1.21.8
Neoforge
2mo ago 1
1.21.8
Forge
2mo ago 1
1.21.8
Fabric
2mo ago 1
1.21.7
Neoforge
2mo ago 1
1.21.7
Forge
2mo ago 1
1.21.7
Fabric
2mo ago 1
1.21.6
Neoforge
2mo ago 1
1.21.6
Forge
2mo ago 1
1.21.6
Fabric
2mo ago 1
1.21.5
Neoforge
2mo ago 1
1.21.5
Forge
2mo ago 1
1.21.5
Fabric
2mo ago 1
1.21.4
Neoforge
2mo ago 1
1.21.4
Forge
2mo ago 1
1.21.4
Fabric
2mo ago 1
1.21.3
Neoforge
2mo ago 1
1.21.3
Forge
2mo ago 1
1.21.3
Fabric
2mo ago 1
1.21.2
Neoforge
2mo ago 1
1.21.2
Fabric
2mo ago 1
1.21.1
Neoforge
2mo ago 1
1.21.1
Forge
2mo ago 1
1.21.1
Fabric
2mo ago 1
1.21
Neoforge
2mo ago 1
1.21
Forge
2mo ago 1
1.21
Fabric
2mo ago 1
1.20.6
Neoforge
2mo ago 1
1.20.6
Forge
2mo ago 1
1.20.6
Fabric
2mo ago 1
1.20.5
Fabric
2mo ago 1
1.20.4
Neoforge
2mo ago 1
1.20.4
Forge
2mo ago 1
1.20.4
Fabric
2mo ago 1
1.20.3
Fabric
2mo ago 1
1.20.2
Fabric
2mo ago 1
1.20.1
Forge
2mo ago 1
1.20.1
Fabric
2mo ago 1
26.2
Fabric
2mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.2
Neoforge
3mo ago 1
26.1.2
Forge
3mo ago 1
26.1.2
Fabric
3mo ago 1
26.1.1
Neoforge
3mo ago 1
26.1.1
Forge
3mo ago 1
26.1.1
Fabric
3mo ago 1
26.1
Neoforge
3mo ago 1
26.1
Forge
3mo ago 1
26.1
Fabric
3mo ago 1
1.21.11
Neoforge
3mo ago 1
1.21.11
Forge
3mo ago 1
1.21.11
Fabric
3mo ago 1
1.21.10
Neoforge
3mo ago 1
1.21.10
Forge
3mo ago 1
1.21.10
Fabric
3mo ago 1
1.21.9
Neoforge
3mo ago 1
1.21.9
Forge
3mo ago 1
1.21.9
Fabric
3mo ago 1
1.21.8
Neoforge
3mo ago 1
1.21.8
Forge
3mo ago 1
1.21.8
Fabric
3mo ago 1
1.21.7
Neoforge
3mo ago 1
1.21.7
Forge
3mo ago 1
1.21.7
Fabric
3mo ago 1
1.21.6
Neoforge
3mo ago 1
1.21.6
Forge
3mo ago 1
1.21.6
Fabric
3mo ago 1
1.21.5
Neoforge
3mo ago 1
1.21.5
Forge
3mo ago 1
1.21.5
Fabric
3mo ago 1
1.21.4
Neoforge
3mo ago 1
1.21.4
Forge
3mo ago 1
1.21.4
Fabric
3mo ago 1
1.21.3
Neoforge
3mo ago 1
1.21.3
Forge
3mo ago 1
1.21.3
Fabric
3mo ago 1
1.21.2
Neoforge
3mo ago 1
1.21.2
Fabric
3mo ago 1
1.21.1
Neoforge
3mo ago 1
1.21.1
Forge
3mo ago 1
1.21.1
Fabric
3mo ago 1
1.21
Neoforge
3mo ago 1
1.21
Forge
3mo ago 1
1.21
Fabric
3mo ago 1
1.20.6
Neoforge
3mo ago 1
1.20.6
Forge
3mo ago 1
1.20.6
Fabric
3mo ago 1
1.20.5
Fabric
3mo ago 1
1.20.4
Neoforge
3mo ago 1
1.20.4
Forge
3mo ago 1
1.20.4
Fabric
3mo ago 1
1.20.3
Fabric
3mo ago 1
1.20.2
Fabric
3mo ago 1
1.20.1
Forge
3mo ago 1
1.20.1
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.2
Neoforge
3mo ago 1
26.1.2
Forge
3mo ago 1
26.1.2
Fabric
3mo ago 1
26.1.1
Neoforge
3mo ago 1
26.1.1
Forge
3mo ago 1
26.1.1
Fabric
3mo ago 1
26.1
Neoforge
3mo ago 1
26.1
Forge
3mo ago 1
26.1
Fabric
3mo ago 1
1.21.11
Neoforge
3mo ago 1
1.21.11
Forge
3mo ago 1
1.21.11
Fabric
3mo ago 1
1.21.10
Neoforge
3mo ago 1
1.21.10
Forge
3mo ago 1
1.21.10
Fabric
3mo ago 1
1.21.9
Neoforge
3mo ago 1
1.21.9
Forge
3mo ago 1
1.21.9
Fabric
3mo ago 1
1.21.8
Neoforge
3mo ago 1
1.21.8
Forge
3mo ago 1
1.21.8
Fabric
3mo ago 1
1.21.7
Neoforge
3mo ago 1
1.21.7
Forge
3mo ago 1
1.21.7
Fabric
3mo ago 1
1.21.6
Neoforge
3mo ago 1
1.21.6
Forge
3mo ago 1
1.21.6
Fabric
3mo ago 1
1.21.5
Neoforge
3mo ago 1
1.21.5
Forge
3mo ago 1
1.21.5
Fabric
3mo ago 1
1.21.4
Neoforge
3mo ago 1
1.21.4
Forge
3mo ago 1
1.21.4
Fabric
3mo ago 1
1.21.3
Neoforge
3mo ago 1
1.21.3
Forge
3mo ago 1
1.21.3
Fabric
3mo ago 1
1.21.2
Neoforge
3mo ago 1
1.21.2
Fabric
3mo ago 1
1.21.1
Neoforge
3mo ago 1
1.21.1
Forge
3mo ago 1
1.21.1
Fabric
3mo ago 1
1.21
Neoforge
3mo ago 1
1.21
Forge
3mo ago 1
1.21
Fabric
3mo ago 1
1.20.6
Neoforge
3mo ago 1
1.20.6
Forge
3mo ago 1
1.20.6
Fabric
3mo ago 1
1.20.5
Fabric
3mo ago 1
1.20.4
Neoforge
3mo ago 1
1.20.4
Forge
3mo ago 1
1.20.4
Fabric
3mo ago 1
1.20.3
Fabric
3mo ago 1
1.20.2
Fabric
3mo ago 1
1.20.1
Forge
3mo ago 1
1.20.1
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.2
Neoforge
3mo ago 1
26.1.2
Forge
3mo ago 1
26.1.2
Fabric
3mo ago 1
26.1.1
Neoforge
3mo ago 1
26.1.1
Forge
3mo ago 1
26.1.1
Fabric
3mo ago 1
26.1
Neoforge
3mo ago 1
26.1
Forge
3mo ago 1
26.1
Fabric
3mo ago 1
1.21.11
Neoforge
3mo ago 1
1.21.11
Forge
3mo ago 1
1.21.11
Fabric
3mo ago 1
1.21.10
Neoforge
3mo ago 1
1.21.10
Forge
3mo ago 1
1.21.10
Fabric
3mo ago 1
1.21.9
Neoforge
3mo ago 1
1.21.9
Forge
3mo ago 1
1.21.9
Fabric
3mo ago 1
1.21.8
Neoforge
3mo ago 1
1.21.8
Forge
3mo ago 1
1.21.8
Fabric
3mo ago 1
1.21.7
Neoforge
3mo ago 1
1.21.7
Forge
3mo ago 1
1.21.7
Fabric
3mo ago 1
1.21.6
Neoforge
3mo ago 1
1.21.6
Forge
3mo ago 1
1.21.6
Fabric
3mo ago 1
1.21.5
Neoforge
3mo ago 1
1.21.5
Forge
3mo ago 1
1.21.5
Fabric
3mo ago 1
1.21.4
Neoforge
3mo ago 1
1.21.4
Forge
3mo ago 1
1.21.4
Fabric
3mo ago 1
1.21.3
Neoforge
3mo ago 1
1.21.3
Forge
3mo ago 1
1.21.3
Fabric
3mo ago 1
1.21.2
Neoforge
3mo ago 1
1.21.2
Fabric
3mo ago 1
1.21.1
Neoforge
3mo ago 1
1.21.1
Forge
3mo ago 1
1.21.1
Fabric
3mo ago 1
1.21
Neoforge
3mo ago 1
1.21
Forge
3mo ago 1
1.21
Fabric
3mo ago 1
1.20.6
Neoforge
3mo ago 1
1.20.6
Forge
3mo ago 1
1.20.6
Fabric
3mo ago 1
1.20.5
Fabric
3mo ago 1
1.20.4
Neoforge
3mo ago 1
1.20.4
Forge
3mo ago 1
1.20.4
Fabric
3mo ago 1
1.20.3
Fabric
3mo ago 1
1.20.2
Fabric
3mo ago 1
1.20.1
Forge
3mo ago 1
1.20.1
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.2
Neoforge
3mo ago 1
26.1.2
Forge
3mo ago 1
26.1.2
Fabric
3mo ago 1
26.1.1
Neoforge
3mo ago 1
26.1.1
Forge
3mo ago 1
26.1.1
Fabric
3mo ago 1
26.1
Neoforge
3mo ago 1
26.1
Forge
3mo ago 1
26.1
Fabric
3mo ago 1
1.21.11
Neoforge
3mo ago 1
1.21.11
Forge
3mo ago 1
1.21.11
Fabric
3mo ago 1
1.21.10
Neoforge
3mo ago 1
1.21.10
Forge
3mo ago 1
1.21.10
Fabric
3mo ago 1
1.21.9
Neoforge
3mo ago 1
1.21.9
Forge
3mo ago 1
1.21.9
Fabric
3mo ago 1
1.21.8
Neoforge
3mo ago 1
1.21.8
Forge
3mo ago 1
1.21.8
Fabric
3mo ago 1
1.21.7
Neoforge
3mo ago 1
1.21.7
Forge
3mo ago 1
1.21.7
Fabric
3mo ago 1
1.21.6
Neoforge
3mo ago 1
1.21.6
Forge
3mo ago 1
1.21.6
Fabric
3mo ago 1
1.21.5
Neoforge
3mo ago 1
1.21.5
Forge
3mo ago 1
1.21.5
Fabric
3mo ago 1
1.21.4
Neoforge
3mo ago 1
1.21.4
Forge
3mo ago 1
1.21.4
Fabric
3mo ago 1
1.21.3
Neoforge
3mo ago 1
1.21.3
Forge
3mo ago 1
1.21.3
Fabric
3mo ago 1
1.21.2
Neoforge
3mo ago 1
1.21.2
Fabric
3mo ago 1
1.21.1
Neoforge
3mo ago 1
1.21.1
Forge
3mo ago 1
1.21.1
Fabric
3mo ago 1
1.21
Neoforge
3mo ago 1
1.21
Forge
3mo ago 1
1.21
Fabric
3mo ago 1
1.20.6
Neoforge
3mo ago 1
1.20.6
Forge
3mo ago 1
1.20.6
Fabric
3mo ago 1
1.20.5
Fabric
3mo ago 1
1.20.4
Neoforge
3mo ago 1
1.20.4
Forge
3mo ago 1
1.20.4
Fabric
3mo ago 1
1.20.3
Fabric
3mo ago 1
1.20.2
Fabric
3mo ago 1
1.20.1
Forge
3mo ago 1
1.20.1
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.2
Neoforge
3mo ago 1
26.1.2
Forge
3mo ago 1
26.1.2
Fabric
3mo ago 1
26.1.1
Neoforge
3mo ago 1
26.1.1
Forge
3mo ago 1
26.1.1
Fabric
3mo ago 1
26.1
Neoforge
3mo ago 1
26.1
Forge
3mo ago 1
26.1
Fabric
3mo ago 1
1.21.11
Neoforge
3mo ago 1
1.21.11
Forge
3mo ago 1
1.21.11
Fabric
3mo ago 1
1.21.10
Neoforge
3mo ago 1
1.21.10
Forge
3mo ago 1
1.21.10
Fabric
3mo ago 1
1.21.9
Neoforge
3mo ago 1
1.21.9
Forge
3mo ago 1
1.21.9
Fabric
3mo ago 1
1.21.8
Neoforge
3mo ago 1
1.21.8
Forge
3mo ago 1
1.21.8
Fabric
3mo ago 1
1.21.7
Neoforge
3mo ago 1
1.21.7
Forge
3mo ago 1
1.21.7
Fabric
3mo ago 1
1.21.6
Neoforge
3mo ago 1
1.21.6
Forge
3mo ago 1
1.21.6
Fabric
3mo ago 1
1.21.5
Neoforge
3mo ago 1
1.21.5
Forge
3mo ago 1
1.21.5
Fabric
3mo ago 1
1.21.4
Neoforge
3mo ago 1
1.21.4
Forge
3mo ago 1
1.21.4
Fabric
3mo ago 1
1.21.3
Neoforge
3mo ago 1
1.21.3
Forge
3mo ago 1
1.21.3
Fabric
3mo ago 1
1.21.2
Neoforge
3mo ago 1
1.21.2
Fabric
3mo ago 1
1.21.1
Neoforge
3mo ago 1
1.21.1
Forge
3mo ago 1
1.21.1
Fabric
3mo ago 1
1.21
Neoforge
3mo ago 1
1.21
Forge
3mo ago 1
1.21
Fabric
3mo ago 1
1.20.6
Neoforge
3mo ago 1
1.20.6
Forge
3mo ago 1
1.20.6
Fabric
3mo ago 1
1.20.5
Fabric
3mo ago 1
1.20.4
Neoforge
3mo ago 1
1.20.4
Forge
3mo ago 1
1.20.4
Fabric
3mo ago 1
1.20.3
Fabric
3mo ago 1
1.20.2
Fabric
3mo ago 1
1.20.1
Forge
3mo ago 1
1.20.1
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.2
Neoforge
3mo ago 1
26.1.2
Forge
3mo ago 1
26.1.2
Fabric
3mo ago 1
26.1.1
Neoforge
3mo ago 1
26.1.1
Forge
3mo ago 1
26.1.1
Fabric
3mo ago 1
26.1
Neoforge
3mo ago 1
26.1
Forge
3mo ago 1
26.1
Fabric
3mo ago 1
1.21.11
Neoforge
3mo ago 1
1.21.11
Forge
3mo ago 1
1.21.11
Fabric
3mo ago 1
1.21.10
Neoforge
3mo ago 1
1.21.10
Forge
3mo ago 1
1.21.10
Fabric
3mo ago 1
1.21.9
Neoforge
3mo ago 1
1.21.9
Forge
3mo ago 1
1.21.9
Fabric
3mo ago 1
1.21.8
Neoforge
3mo ago 1
1.21.8
Forge
3mo ago 1
1.21.8
Fabric
3mo ago 1
1.21.7
Neoforge
3mo ago 1
1.21.7
Forge
3mo ago 1
1.21.7
Fabric
3mo ago 1
1.21.6
Neoforge
3mo ago 1
1.21.6
Forge
3mo ago 1
1.21.6
Fabric
3mo ago 1
1.21.5
Neoforge
3mo ago 1
1.21.5
Forge
3mo ago 1
1.21.5
Fabric
3mo ago 1
1.21.4
Neoforge
3mo ago 1
1.21.4
Forge
3mo ago 1
1.21.4
Fabric
3mo ago 1
1.21.3
Neoforge
3mo ago 1
1.21.3
Forge
3mo ago 1
1.21.3
Fabric
3mo ago 1
1.21.2
Neoforge
3mo ago 1
1.21.2
Fabric
3mo ago 1
1.21.1
Neoforge
3mo ago 1
1.21.1
Forge
3mo ago 1
1.21.1
Fabric
3mo ago 1
1.21
Neoforge
3mo ago 1
1.21
Forge
3mo ago 1
1.21
Fabric
3mo ago 1
1.20.6
Neoforge
3mo ago 1
1.20.6
Forge
3mo ago 1
1.20.6
Fabric
3mo ago 1
1.20.5
Fabric
3mo ago 1
1.20.4
Neoforge
3mo ago 1
1.20.4
Forge
3mo ago 1
1.20.4
Fabric
3mo ago 1
1.20.3
Fabric
3mo ago 1
1.20.2
Fabric
3mo ago 1
1.20.1
Forge
3mo ago 1
1.20.1
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.2
Fabric
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.1.x
Forge
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.1.x
Forge
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.2
Fabric
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.1.x
Forge
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.2
Neoforge
3mo ago 1
26.2
Forge
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.1.x
Forge
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.2
Fabric
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.2
Forge
3mo ago 1
26.1.x
Forge
3mo ago 1
26.2
Neoforge
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.2
Fabric
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.2
Forge
3mo ago 1
26.1.x
Forge
3mo ago 1
26.2
Neoforge
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.2
Fabric
3mo ago 1
26.1.x
Fabric
3mo ago 1
26.1.x
Forge
3mo ago 1
26.1.x
Neoforge
3mo ago 1
26.1.x
Fabric
4mo ago 1
26.1.x
Forge
4mo ago 1
26.1.x
Neoforge
4mo ago 1
26.1.x
Fabric
5mo ago 1
26.1.x
Forge
5mo ago 1
26.1.x
Neoforge
5mo ago 1
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
# 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
...
One Dimension Icon
Download One Dimension
Select game version
Select platform