2.1.0+26.1
Compatibility
Required content
Changes
BeaCraft 2.1.0+26.1
For Minecraft 26.1, and only 26.1.
The game packet says what she is wearing
The inventory in the game packet stopped at slot 35. Armour lives past that, so the moment a chestplate went on it left the packet entirely: an agent reading its own state found no chestplate, concluded it had none, and equipped one again. The same blind spot hid whatever was in the off hand, which is where a shield goes.
inventory.armor now carries the four worn pieces, head to feet, in the same
shape as every other slot. inventory.hand_off was already being sent and is
unchanged.
This is additive: a client that does not read the new field sees exactly the packet it saw before.
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:px0NmIO6:c8ixZ4NZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:px0NmIO6:c8ixZ4NZ"
}

