Tags
Creators
Details
1.0.1
Compatibility
Required content
Changes
๐งฑ PacketBlocks v1.0.1 โ Compatibility & Stability Update
๐ Whatโs Changed
-
Refactored internal package structure
ThePacketBlockManagerand related classes have been moved from
net.bitbylogic.packetblocks.managerโnet.bitbylogic.packetblocks.block.
This improves organization and clarity within the codebase. -
Minor performance improvements during fake block updates and chunk handling.
โ ๏ธ Developer Notice
If you encounter:
NoSuchMethodError: net.bitbylogic.packetblocks.PacketBlocks.getBlockManager()
you are running an outdated version of PacketBlocks.
Please update your serverโs JAR to this release and rebuild any dependent plugins against it.
๐ก Recommended Action
- โ Replace old PacketBlocks JAR with this one on your server.
- ๐ Rebuild dependent plugins (if you use the API).
- ๐งฉ Confirm
allow-flight=trueinserver.propertiesto avoid player kicks on fake blocks.
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:2ZnPwkRV:o66kwbaA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2ZnPwkRV:o66kwbaA"
}

