Tags
Creators
Details
Licensed ARR
Published 3 years ago
All versions
1.2.11a-neoforge-mc1.21.6
Release
Fusion 1.2.11a10 months ago 9,601
Compatibility
Minecraft: Java Edition
1.21.6–1.21.8
Platform
NeoForge
Supported environments
Client-side
Changes
Fusion 1.2.11a
- Fixed Fusion's
pack.mcmetadata not getting loaded for mod resources
Fusion 1.2.11
- Added
show_breaking_overlayoption to block model modifiers to not show the breaking overlay for appended models - Fixed crash when modded model bakeries do not contain model modifiers' target models
Fusion 1.2.10
- Fixed all Fusion models loaded after any Fusion model has an error being broken
Fusion 1.2.9a
- Fixed crash when using model modifiers with mods using Puzzles Lib installed
Fusion 1.2.9
- Fixed
piecedlayout when a quads' uv does not cover the entire sprite - Fixed connecting textures using connections for the wrong direction for rotated quads with mirrored uv in some cases
Fusion 1.2.8
- Added Hungarian translations (thanks to bayi!)
- Ambient occlusion is now disabled for emissive quads
- Fixed quads with different render types being ordered randomly for
baseandconnectingmodels when rendered as items - Fixed inverted vertical tile ordering for
continuoustextures - Fixed
DefaultConnectionPredicates#isFaceVisiblereturningis_same_blockpredicate - Fixed
NotConnectionPredicateserialization being invalid - Fixed
pane_culling_fixdiscarding render type and ambient occlusion properties - Fixed crash when evaluating
biomeanddimensionentity predicate - Fixed
randomtexture seed always being 0 for bottom side - Fixed overrides folder not working for resource packs which use vanilla resource overlays
- Fixed entity model modifiers using model for incorrect layer when targeting entities with multiple vanilla layers
Fusion 1.2.7
- Initial release of Fusion for Minecraft 1.21.6 & 1.21.7
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:p19vrgc2:lXhJSTZX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:p19vrgc2:lXhJSTZX"
}

