All versions
1.2.0
Release
1.2.0 - Server-side opt-inlast month 41
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Any compatible version
Changes
Server-side opt-in for the see-through feature, per Modrinth Content Rules section 3 (seeing through opaque blocks requires a server-side opt-in).
- Singleplayer / your own world: works exactly as before.
- Multiplayer: disabled by default. A server enables it by installing the mod on the server side and setting allowSeeThrough=true in config/block-unrenderer-server.json; the server then sends an opt-in handshake to clients on join.
- On vanilla servers (or any that have not opted in) the feature stays disabled.
- ModMenu is now optional. The mod can load on dedicated servers only to send the opt-in handshake, and never changes world or block data.
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:9fQJdnIj:SLA7MdyX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9fQJdnIj:SLA7MdyX"
}

