Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 3 months ago
All versions
1.0.3
Release
Void One Block 1.0.34 months ago 90
Compatibility
Minecraft: Java Edition
1.16.5
Platform
Forge
Supported environments
Client and server
Changes
Changelog
Changed
- Structure generation is now permanently disabled in all void dimensions (Overworld one-block, void Nether, void End). Previously configurable via
generateStructures(defaulttrue), this option has been removed entirely.OneBlockChunkGeneratorandVoidDimensionChunkGeneratornow always construct withnew DimensionStructuresSettings(false), hardcoding structures off regardless of config.- Old world-gen constructors that accepted a
generateStructuresboolean are kept for save-compatibility only — the flag is accepted but ignored, so existing worlds/configs still decode without crashing. - Reason: structure placement logic (height sampling, surface checks, stronghold ring search, modded structure preconditions) assumes normal terrain exists. In a void world these assumptions break in inconsistent, hard-to-track ways across different mods — strongholds partially generating, structures floating or sinking, silent placement failures. Disabling structures outright removes an entire class of these bugs.
- End-specific content (obsidian spikes, exit podium, gateways, dragon fight) is unaffected — these are placed directly by dedicated handlers (
EndPodiumHandler,EndGatewayHandler,DragonFogHandler) andVoidDimensionChunkGenerator#placeEndSpikes, not through the generic structure system.
Removed
generateStructuresconfig option (Void1BlockConfig). No replacement — behavior is now fixed.
Documentation
- Updated README to remove references to structure generation/preservation and reflect the new structure-free behavior.
Optional dependencies
Unavailable version
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:OIQ2P6NI:pQBOyDWv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OIQ2P6NI:pQBOyDWv"
}

