Links
Tags
Creators
Details
1.6.1+mc26.3
Compatibility
Required content
Changes
Meshelium now runs on Minecraft 26.3 as well as 26.2, on Fabric and on NeoForge. Download the file for your game version; they are all the same mod, and everything below applies to both.
Minecraft 26.3 changed how it draws the world - terrain and everything else now share one render pass, and "Improved Transparency" became a new order-independent method - and Meshelium follows both without you doing anything. With Improved Transparency on, Meshelium draws the water and glass itself and Minecraft's own transparency pass is skipped for terrain, so the picture is the same as with the setting off.
NeoForge on 26.3: no loading-screen workaround needed. NeoForge for 26.3 currently ships with its early loading screen switched off (its loader ignores the setting), so the Vulkan start-up problem Meshelium works around on 26.2 cannot happen there. Meshelium leaves it alone and says so in the log. On 26.2 the workaround stays exactly as it was.
If your launcher skips a Java setting, Meshelium now tells you.
Sodium 0.9.2 is a release now, on both game versions.
Use Sodium 0.9.2 for your game version - the release, not the newer 0.9.3 alpha. On 26.2, Sodium 0.9.2-beta.1 is the same build with a different version number, and Meshelium treats it as the same Sodium instead of warning about it.
Fixed: a memory-copy the graphics driver was not asked permission for.
When Meshelium's terrain records grew for the first time, they were copied out of a buffer that had not been created for copying. AMD's driver allowed it; the Vulkan rules do not, and a stricter driver could have refused. Both game versions have the fix.
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:7AQRR6lD:x9RmpHW3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7AQRR6lD:x9RmpHW3"
}

