Tags
Creators
Details
1.0.1+1.21.2
Compatibility
Changes
1.0.1+1.21.2 Update
Compatible with Minecraft 1.21.2-1.21.3
-
Updated to Minecraft 1.21.2+ syntax
-
Migrated all models from CMD to the new item_model component, enhancing compatibility and ease of development.
-
Removed integration with CIT as it's now longer required
- Due to this, CIT Resewn is no longer a required dependence for modded version
-
Added an update system that will upgrade all items and outdimensional blocks from CMD to item_model component system automatically
-
As there are no mods that implement CTM feature on 1.21.2-1.21.3 Neoforge (previously it was implemented by Continuity with Sinytra Connector), system for displaying textures of indimension blocks on Neoforge was migrated from CTM to Polytone's Biome Variant Textures
- Due to this Continuity and Sinytra Connector is no longer required dependences for Neoforge version, while Polytone became mandatory
- Note, that Polytone's Biome Variant Textures is less functional and several indimension blocks cannot obtain unique textures with it. It also described as experimental, more resource-intensive and less compatible with other mods by Polytone's author.
- Because of that, migration to this system is temporal, and will be reverted when CTM mods for Neoforge become available
-
Added
trailparticles to mini boss teleportations to help players locate their teleportation destinations more easily -
Fixed a desync (caused by MC-197855) with Watchling's special attack on loaded servers (thanks to
/rotate) -
Updated
player_motionlibrary to 1.4.2 version -
All features from 1.0.1+1.21
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| DeformationDimension-rp-v1.0.1+1.21.2.zip | Required resource pack | 1.19 MiB |
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:snWw7IUi:8TBWR52y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:snWw7IUi:8TBWR52y"
}

