Tags
Creators
Details
All versions
5.0.4
Release
Big Globe-5.0.4-MC1.20.1last year 2,154
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
For normal users:
- Updated to MC 1.21.6 and 1.21.7.
- Fixed LODs rendering in front of terrain in dimensions which don't have translucent blocks as part of worldgen (nether and end).
- Waypoint renderer is now more glowy.
- Added another end fractal structure.
- Fixed bamboo spawning in lakes and rivers.
- Powder snow now spawns in frozen caves.
- Voidmetal armor can now have trims applied to it.
- Fixed bonemeal not producing flowers in big globe worlds.
- Abandoned cities now contain copper bulbs, in addition to redstone lamps.
- The small puddles of water that spawn in swamps now place mud around and below themselves.
- Fixed obelisks rarely getting cut off at chunk boundaries.
- Satin is no longer required for waypoint or hyperspace effects in old MC versions.
- Temporarily disabled worldgen integration for Voxy 0.2.x, as integration with Voxy 0.2.x was always bad and broken and made Voxy very unhappy.
- Worldgen integration will be re-added if/when Voxy gets an API for this.
- Worldgen integration still works fine with Voxy 0.1.5 in MC 1.20.4.
For data pack users:
- Fixed world traits failing to apply on world creation.
For data pack developers:
- Added perlin grids (derivative perlin grids are not yet implemented, but are planned).
- Added rotation and mirror fields for StructurePiece instances.
- Mega trees can now be moved by structure overriders.
- Inline layer definitions are back to being unsupported again.
- This is because inline definitions do not have an ID associated with them, but LOD rendering syncs them to the client as a registry, which requires an ID.
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:xsng1aJf:ky8ln4TV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xsng1aJf:ky8ln4TV"
}



