Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated 5 months ago
All versions
0.4.0
Beta
Better World Options 0.4.08 months ago 417
Uploaded by
Compatibility
Minecraft: Java Edition
b1.7.3
Platforms
Babric
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Worlds from version 0.3.x need to be converted to 0.4.0
Additions
- Amplified world type
- New options system with general and world type options
- World converter for worlds from versions 0.2.x and 0.3.x to 0.4.0
- Single Biome and Finite World options for all overworld world types
- New finite world types: LCE and Island
- LCE world sizes: Classic, Small, Medium, and Large
- Configurable finite world width and length
- Farlands option
- Options to configure Farlands shape and distance
- 1:1 Indev world generation
- Finite world boundaries now push entities back, like in Indev
- Config option to disable old textures and sky when Old Features are enabled
- Old stars and disabled sunrise/sunset colors in Alpha, Infdev, and Indev when Old Features are enabled
- Sky dimension option for Skylands
- Config option to fix terrain generation above height 128 in the Default world type
Changes
- Skylands is now an overworld world type
- Farlands is now an option instead of a world type
- Increased flower density in the Paradise theme
- Improved Classic player walking animation
- "Infinite World" renamed to "Finite World"
- Cave Fix and Beach Fix are now disabled by default
- Renamed option "Allow generation of these features with Old Features enabled" to "Ravine generation with Old Features"
Fixes
- Players no longer spawn outside finite worlds when switching dimensions
- Modded decorations no longer generate on flat worlds or outside finite world boundaries
- Various bug fixes
Optional dependencies
Any compatible 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:wnvWjnSe:bvCosFiB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wnvWjnSe:bvCosFiB"
}

