Tags
Creators
Details
All versions
0.2.1-beta
Beta
MultiblockEngine 0.2.1-beta10 months ago 25
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Paper
Purpur
Changes
π Changelog β MultiBlockEngine
0.2.1-beta
Changed
- Project version updated to 0.2.1-beta.
- Internal adjustments to stabilize the API and addon system.
0.2.0-beta
β¨ Added
- Addon system with namespaces and multiblock capabilities.
- Public multiblock API ready for external extensions.
- Advanced conditional actions system with variable support.
- Conditions system with player context.
- Rotation and state support for multiblock structures.
- Actions with target selection.
- Display names for multiblocks.
- Debug system for structure validation.
/multiblock debugcommand with tab completion.- PlaceholderAPI integration.
- Instance validation before spawning holograms.
β»οΈ Refactored
- Centralized placeholder parsing.
- Fixed duplicated event execution.
- Refactored MultiblockManager, isolating tick cancellation logic.
- General security improvements for actions and addon handling.
βοΈ Changed
- Gson moved from implementation to compileOnly.
- Adjustments to the actions system for improved robustness.
- Improved multiblock validation and execution flow.
π Fixed
- Issues with multiple event executions.
- Edge cases in multiblock instance validation.
- Potential errors in misconfigured actions.
0.1.x β Initial versions
β¨ Added
- MultiBlockEngine core.
- Base engine for detecting and managing multiblock structures.
- Basic actions and states for multiblocks.
- Initial variables system.
- Early rotation support.
- Controller blocks syntax.
- Initial documentation and project roadmap.
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:lYjJ4BJl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tO8GLlyZ:lYjJ4BJl"
}

