Creators
Details
Licensed LGPL-3.0-only
Published 5 months ago
Updated 5 days ago
All versions
26.3.0.2
Release
CTM-26.3.0.25 days ago 48
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
[26.3.0.2]
Added
- Added the
CTMBlockOffsetsAPI for per-block texture offsets and bounded updates across face-connected blocks of the same type in loaded chunks. - Added persistent per-dimension offsets, synchronization for tracking players, and offset snapshots when players enter affected chunks.
- Added regression tests for deferred baking, caching, material snapshots, and packet batching.
Changed
- Deferred eligible CTM model baking and standalone Standard geometry until needed to reduce upfront baking work and memory use.
- Replaced post-bake quad deduplication with reload-scoped bake caching and shared quads.
- Adapted deferred material snapshots and render-section refreshes to Minecraft 26.3.
- Retained standalone-texture requirements for all CTM models.
Fixed
- Updated Eldritch geometry caching to follow changes in the underlying connected texture geometry instead of reusing parts solely by block position.
- Corrected release game-version metadata and included the changelog on Modrinth.
[26.3.0.1]
- Updated CTM for Minecraft 26.3 and NeoForge 26.3.0.95.
[26.2.0.2]
Removed
- Removed all APIs marked
@Deprecated(forRemoval = true), including legacy model templates, texture-sheet slots, UV remapping, and texture-sheet baking fallbacks. - Resource packs using the removed sheet layouts must supply standalone state textures. See Model JSON Format and Data Generation.
Changed
- Converted bundled glass and obsidian models to standalone state textures.
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:QWVAzrUc:qjPw6sE3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QWVAzrUc:qjPw6sE3"
}

