Tags
Creators
Details
All versions
3.7.5+21
Release
MultiblockEngine 3.7.53 months ago 15
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.4
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Breaking changes:
- Command System: The main monolithic command (
MultiblockCommand) has been completely removed and refactored into separate commands using the Incendo command framework. This may affect administrators or third-party integrations if they relied on the old command structure or its specific permissions.
Internal changes:
- Command System: Complete refactoring of commands into a modular structure based on Cloud (
BlueprintCommand,DebugCommand,ExportCommand,MiscCommand), which facilitates scalability and maintenance. - Architecture: The core
MultiBlockEngineclass was introduced to centrally initialize the application’s infrastructure and services. - Architecture: Architectural issues related to excessive coupling of the
EventBusand the service loading system were resolved. - Event System: The base interface
MBEEventand theEventBusServicewere added to standardize and improve the handling of internal events. - Lifecycle: The
MultiblockListenerclass was refactored, delegating its business logic to the newMultiblockLifecycleServiceto maintain separation of concerns. - Platform API: The
MBEItemStackabstraction was introduced into the API (along with its implementation,BukkitMBEItemStack) for better cross-platform item handling.
Bug fixes:
- WorldEdit Compatibility: Fixed a bug in the
MultiblockListenerthat caused interaction issues when using WorldEdit’s selection tool (wand).
Changes made by: @DarkBladeDev
Full Changelog: 2.7.5...3.7.5
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:tO8GLlyZ:vl9BEzGQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tO8GLlyZ:vl9BEzGQ"
}

