Tags
Creators
Details
All versions
2.4.0-1.21.1-fabric
Release
Truly-Modular-miapi-fabric-2.4.0-1.21.15 hours ago 5
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
v2.4.0 (1.21)
Additions
- added compat for LambDynamicLights
- added new Keybind to show stats on modular item (default is I)
- added new Keybind to show stats to compare to currently equiped item (default is C)
- added internal raycast logic to normal models
- added new Commands to show/compare stats on modular items
- /miapi stat mainhand -> prints mainhand stats into chat
- /miapi stat compareHands -> compares stats from mainhand to offhand
- /miapi stat compareHandsOnlyDiff -> compares mainhand to offhand but prints only differences.
- made modules clickable in the preview renderer to select them
- added passive potion effect
Changes
- changed developer mode to support ALL, ADMIN and NONE
- rewrote internal stat api
- groups now exist
- emojis are mostly added by groups instead of the stats now, helping users understand the usage of a stat faster
- existing groups are Melee, MeleeModifier, Projectile Weapon, Projectile, Throw, Enchantments On-Hit(applies melee and ranges), Mining, Armor and misc
- made diamond and netherite armor textures more accurate in color
Fixes
- fixed bug where material effects could apply twice
- fixed bug where Potion effects would not correctly merge
- fixed bug where explosion range and max damage where accidentally swapped
- fixed issue where merging material keys wouldnt work correctly.
- fixed minor enchantment bugs where certain enchantments weren't detected correctly
- improved issue where items would render far too dark on neoforge
- fixed loot functions not working
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:c4Uf1TKc:zNs8dDAY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c4Uf1TKc:zNs8dDAY"
}

