Tags
Creators
Details
Licensed Unlicense
Published 4 years ago
Updated 4 months ago
All versions
0.2.20
Release
FZMM 0.2.2010 months ago 2,435
Compatibility
Minecraft: Java Edition
1.21.9–1.21.10
Platform
Fabric
Supported environments
Client-side
Required content
Changes
Known bugs
- In Head Generator, the lighting of the heads is inconsistent compared to previous versions
Highlights
- Update to 1.21.9 and 1.21.10
- [1.21.6+] Update Fabric API version requirement to >=0.131.0
- Discontinue support for:
- 1.21.5
- 1.21.4
- 1.21 to 1.21.1
- Fixes incompatibility with
supplementariesmod which caused a crash when opening the inventory - Optimizes the preview of Imagetext
- change preview update delay from 200ms to 20ms
- Fixes incompatibility issue with
clientcommandsmod that reduced the character limit
Additions
- Add petrified oak slab to item operator utilities (#71)
- Add Converters icon (by Jamiscus)
Changes
- Redesign the main screen
- The History button will appear disabled if it is empty
- Improves compatibility when modifying tooltips
- Improves compatibility when canceling block place of automatic placer
- The component used for the tabs has been changed, so now they look a little different
Fixes
- Fix a command in the invisible entity warning (Imagetext, Player Statue)
- Fixes crash when opening Imagetext Copy
- Damage tag was not working in
/fzmm old_givewhen specified 1.12.1 and 1.12.2 - Fixes warning when loading item groups when entering a world
- Fixes character split errors in Imagetext Sign
- Fix that NBT can't be copied from
/fzmm nbton very rare occasions (if it contains an incomplete/unpaired multibyte character) - Fix rare error when loading an online player's skin
- Fix possible crash in the Useful Block States item group due to unregistered tag
Removed
- Remove modifications to the social interactions menu
- This is because:
- most users probably didn't know where the change came from, also because the readme didn't document it
- it wasn't very useful
- it was annoying to test and often broke with updates
- This is because:
Optional dependencies
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:tAvlhiZW:hlehALsB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tAvlhiZW:hlehALsB"
}




