Tags
Creators
Details
All versions
6.4.0
Release
Big Globe-6.4.0-MC26.2last week 698
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
- Ported to MC 26.2.
- Removed sulfur block (the one that used to be crafted with 9x sulfur items (the items that drop from nether sulfur ore)).
- Convert all your sulfur blocks back into sulfur items before updating!
- Fixed surface blocks not spawning in the nether.
- Dunes and desert cracks from V4 have made a return in the islands world preset.
- Some nether ores now spawn more commonly and in more biomes.
- Expanded the spawn range of lapis ore.
- Reduced the amount of dirt in the overworld.
- Fixed caves and other dark areas being pitch black. Their brightness should now match vanilla instead.
- Copper tools can now be found in surface mineshaft chests.
- granite, diorite, andesite, dripstone blocks, tuff, and calcite can now be used in most recipes as a substitute for cobblestone.
- Ores will now only mimic stone, without falling back on whatever other blocks are adjacent.
- Several issues with underground LODs (when carving is enabled) have now been fixed.
- Worldgen performance has been improved in the nether (only improves normal terrain, not LOD terrain).
- Evaluate command is now slightly more useful.
New content exclusive to MC 26.2:
- Cinnabar ore: Drops cinnabar items. Spawns in the nether.
- Cinnabar item: Craftable into vanilla cinnabar block. Can also be crafted from sulfur items and redstone dust.
- Cinnabar spike: Just like the vanilla sulfur spike.
- Sulfur biome: A new biome for the nether. Covered in vanilla sulfur/cinnabar blocks, and decorated with sulfur/cinnabar spikes.
Optional dependencies
Any compatible version
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:xsng1aJf:PHrHD2D4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xsng1aJf:PHrHD2D4"
}

