Tags
Creators
Details
All versions
1.0.2+1.21.4
Release
[DATAPACK] Deformation Dimension v1.0.2 ~ 1.21.42 years ago 499
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4
Platform
Data Pack
Changes
1.0.2+1.21.4 Update
Compatible with Minecraft 1.21.4
- Minecraft 1.21.4 Specific
- Updated to 1.21.4 itemstate format
- Updated custom_model_data to 1.21.4 format
- Added Resin Brick as supported trim material for Transgression Armor Trim
- Added some new blocks from Pale Garden game drop to the necessary block tags
- Trail particles updated to 1.21.4 format; their appearance was made more beautiful
- Added the concept of patch_list to the updater function. This will help maintain changes that require manual update in more convenient way
- Datapack 1.0.2 Specific
- Some tags were migrated from mmdp.deformation to mmdp general namespace
- Added some generic block tags to mmdp namespace
- Added version_glossary.txt to help link semantic version of the pack with pack_version value in the scoreboard
- Were made attempts to fix and improve Ukrainian and Polish translations
- Tweaked some probabilities in treasure_chest and usual_spawner loot tables. Getting treasure loot is now more feasible
- Trail particles spreading now works properly in the central room
- Custom items are now added to creative tabs for users of the datapack version as well. Previously, this feature was available by default only for mod players. In both cases, this requires Polytone mod on client side.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| DeformationDimension-rp-v1.0.2+1.21.4.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:ylX9enpl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:snWw7IUi:ylX9enpl"
}

