Links
Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 2 days ago
All versions
1.2.1+26.3
Beta
1.2.1+26.32 days ago 7
Uploaded by
Compatibility
Minecraft: Java Edition
26.3-snapshot-7
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Fixed
LivingEntity.swing(InteractionHand, boolean)is GONE at 26.3-snapshot-7 -- a hard compile break in the auto-block mixin, which swings the shield hand as block feedback. Both the 1-arg and 2-arg overloads were removed; the only remaining form isswing(hand, SwingAnimation, sendToSwingingEntity). Now emitted per version by the codegen (compat.swing_anim,>= 26.3): 26.3+ passes the shield's owngetInteractAnimation()-- a block is a use-path action, which is the animation vanilla threads through its own interact sites -- and every earlier cell keeps the plain 2-arg call. ThesendToSwingingEntityflag staystrueeither way: this mixin runs server-side and the blocking player should see their own swing.
Changed
- Fabric 26.3 cell moved to MC 26.3-snapshot-7 (from snapshot-6): fabric-api
0.156.1+26.3->0.156.2+26.3, resourcepack_format94->95(bumped in_codegen/compat.pyresource_format, the mod's single source for that value), exclusive window[26.3-alpha.6, 26.3-alpha.7)->[26.3-alpha.7, 26.3-alpha.8). Every 26.3 snapshot bumps pack_format by one, so each jar stays snapshot-exclusive. ModMenu stays on21.0.0-alpha.1(still the 26.3-line major). No other cell changed.
Notes
- The other snapshot-7 breaking surfaces do not touch ASR: the trailing
Predictionargument onLivingEntity.drop(ItemStack, boolean)/Inventory.placeItemBackInInventory(ASR neither drops nor returns items), the client-sideLocalPlayer.drop(boolean)return-type change, theInteractionResult.SwingSourceCLIENT/SERVER->PREDICTED/SERVER_ONLYrename (ASR uses only the plainInteractionResultconstants), and the 32 new concrete slab/stair blocks plus the filled-map colour component removals.
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:AlTj0HVt:O6S7WpwN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AlTj0HVt:O6S7WpwN"
}

