Tags
Creators
Details
1.0.1
Compatibility
Changes
Void One Block
Void One Block is a Minecraft Forge 1.16.5 world-generation mod that creates a nearly empty world with only one starting block beneath the player.
Start in the void, break your block, build your platform, gather resources, and progress through Minecraft in a completely different way.
Features
- Adds a Void One Block world type.
- Creates an empty Overworld with one configurable spawn block.
- Default spawn block:
random_item_generator_resurrected:item_block
-
Falls back to
minecraft:bedrockwhen Random Item Generator Resurrected is not installed. -
Supports custom spawn blocks through the config file.
-
Keeps normal vanilla and modded biome generation active.
-
Optional void generation for the Nether and End.
-
Keeps structures enabled for progression, including:
- Strongholds
- Nether Fortresses
- Bastions
- End Cities
- Modded structures
-
Preserves End pillars, dragon fight behavior, gateways, and the End exit fountain.
-
Removes normal terrain while allowing biome IDs and structure placement to remain active.
-
The spawn block only regenerates when its position contains normal Minecraft air, so player-placed blocks are not overwritten.
Configuration
generateStructures = true
voidNether = true
voidEnd = true
spawnBlock = "random_item_generator_resurrected:item_block"
Optional Dependency
Random Item Generator Resurrected is optional.
When installed, Void One Block uses its Random Item Block as the default starting block.
Without it, Void One Block safely uses:
minecraft:bedrock
Important
Create a new world after installing or updating the mod.
World-generation settings are saved separately for each world. Existing worlds may keep their previous terrain or generation settings even after the mod is updated.
Optional dependencies
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:DDl2ylww"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OIQ2P6NI:DDl2ylww"
}

