Tags
Creators
Details
All versions
4.9.1
Release
MultiblockEngine 4.9.13 months ago 19
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.4
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Breaking changes:
- Refactored service implementations and extracted core tool contracts (
ToolModeExecutionService,ToolModeMetricsService,ToolSessionService) into the public API (dev.darkblade.mbe.api.tool.*). - Relocated
UIRuntimeRegistrytodev.darkblade.mbe.api.ui.runtimeand updated UI service implementation references across core and addon modules.
Internal changes:
- Introduced
AddonContext#registerMultiblockDirectoryallowing addons to dynamically inject custom multiblock directory paths into the core structure catalog. - Added
PanelDirectoryRegistryandPanelMappingRegistrytodev.darkblade.mbe.api.uifor dynamic panel directory management and mapping resolution. - Enhanced structure preview and blueprint placement system with
Rotationsupport,DisplayEntityRendererupdates,PreviewPlacementControllercontrols, andPacketEventsRendererBridgeintegration. - Refactored
PdcItemStackBridgefor improved item persistent data container (PDC) operations. - Added CodeMC Maven repositories (
maven-releasesandmaven-snapshots) to the root build configuration. - Standardized project documentation, agent skills, and
AGENTS.mdto English.
Bug fixes:
- Fixed a premature dependency check execution in
AddonRuntimeLifecycleServiceduring addon initialization. - Resolved API dependency resolution across subprojects by enforcing project-level dependency references.
Changes made by: @DarkBladeDev
Full Changelog: 4.8.5...4.9.1
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:WrloxyPT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tO8GLlyZ:WrloxyPT"
}

