Tags
Creators
Details
Licensed MIT
Published 2 years ago
All versions
2.0.0-beta.35
Beta
2.0.0-beta.35 for 1.21.14 months ago 1,376
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- Reworked inventory interactions. (@enjarai)
- Added storage fragments.
- Storage fragments represent an entire container.
- They can be interacted with in much the same way as slot fragments.
- Slot fragments are now made from storage fragments.
- Storage fragments have a fluid variant for interacting with fluid containers.
- Both slot and storage fragments should support any modded storage block.
- Added storage fragments.
- Added color fragments. (@BlueMoonJune)
- Color fragments can be created using dyes and mixed to create arbitrary colors.
- They can be used in certain ploys to apply colors.
- Added Infused Ceramic. (@BlueMoonJune)
- This block can be crafted and dyed any arbitrary color using color fragments.
- Added more options to some flecks that can be applied after creating them. (@BlueMoonJune)
- This includes support for rotating, scaling, and painting (via color fragments).
- Added the Torment on a Chain. (@aurakle)
- This necklace will persistently cast any spell inscribed onto it while worn by a player.
- Added a left click action to wands. (@AshAxolotl)
- The spell cast by a wand will receive a boolean argument to indicate if it was left or right clicked.
- Added a light level option for conjured lights. (@AshAxolotl)
- Added a few new tricks for: (@AshAxolotl)
- Revealing to actionbar explicitly.
- Getting entity equipment.
- And exact position raycasting.
- Many misc tome improvements. (@AshAxolotl and @enjarai)
- Many misc bugfixes and general improvements. (@Master-Bw3, @AshAxolotl, @BlueMoonJune and @enjarai)
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:ZdEfcqro:rLfJa4cg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZdEfcqro:rLfJa4cg"
}






