All versions
1.1
Release
fresh block animations 1.12 months ago 367
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client-side
Changes
Fresh Blocks Animation 1.1
This update focuses on smoother animations, improved compatibility, and better customization.
Added
- Added Throw Placement animation
- Added Two Hands option
- Added animation render distance setting
- Added throw distance setting
- Added throw speed setting
- Added scroll support for the config screen
- Added more customization options
Improved
- Improved overall animation smoothness
- Improved animation timing and transitions
- Improved handling of connected blocks
- Improved fence placement animations
- Improved compatibility with special block types
- Improved configuration menu layout
- Improved overall stability
Fixed
- Fixed liquids behaving like solid blocks on the client
- Fixed water physics issues caused by placement animations
- Fixed MLG water / water drop issues
- Fixed plants and crops getting incorrect collision
- Fixed rails, buttons, pressure plates, torches, ladders, signs, and similar thin blocks receiving incorrect collision
- Fixed redstone dust, repeaters, comparators, and other thin redstone components using incorrect collision behavior
- Fixed coral fans and plant-like corals being handled like full blocks
- Fixed animations not playing when placing blocks over replaceable blocks such as grass, snow, water, or lava
- Fixed fences sometimes losing their animation when connecting to nearby fences or blocks
- Fixed several visual overlap issues with original block textures
- Fixed some secondary block states not updating correctly during animation
- Fixed config buttons not fitting on smaller screens
Notes
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:Arva0REJ:fLiA6JDK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Arva0REJ:fLiA6JDK"
}

