Tags
Creators
Details
2.10.0
Compatibility
Changes
š What's new
MagicCobblestoneGenerator 2.10.0 teaches your generators a new trick: they can now drop custom blocks from ItemsAdder, CraftEngine, Oraxen and Nexo, not just vanilla materials. Add a diamond-encrusted ItemsAdder ore or a CraftEngine gem to a generator tier and it will roll into the weighted-random mix alongside everything else. All plugin access is routed through BentoBox core hooks, so the addon never depends on those plugins directly ā if a custom block isn't available on your server, the generator degrades gracefully to its vanilla fallback and tells you why.
This release also bumps the BentoBox API target to 3.17.0, fixes a long-standing admin panel bug around treasure chances, and cleans up a batch of SonarCloud findings.
⨠Highlights
šŗ Custom block support via BentoBox hooks (#165)
- Generator tiers can now produce blocks from ItemsAdder, CraftEngine, Oraxen and Nexo, addressing #103.
- Blocks are stored as string IDs ā vanilla names like
COBBLESTONE, or provider-prefixed IDs likeitemsadder:namespace:id,craftengine:namespace:id,oraxen:id,nexo:id. Existing databases load unchanged. - The admin edit panel gains an Add Custom Block button (chat input, validated against the hook registry), and panels render custom blocks with the provider's own texture and display name.
MagicGeneratorvalidates the picked block at generation time; an unavailable custom block falls back to the vanilla block with a/whyreport rather than failing silently.- Provider status: ItemsAdder ā and CraftEngine ā generate today; Oraxen ā³ and Nexo ā³ are wired up and will generate once the matching BentoBox core hooks ship (BentoBox#3020, BentoBox#3025).
š Fixes
- Editing a treasure's chance in the admin panel wrote the block list into the deprecated
treasureChanceMapinstead of updatingtreasureItemChanceMapā treasure chance edits now save correctly (#165). - Resolved a batch of SonarCloud code-quality findings raised on PR #165 (#165).
š§ Platform
- Requires BentoBox 3.19.1 or newer ā the custom block hook functionality this release depends on is only available from 3.19.1. The addon will not load on older cores.
āļø Compatibility
āļø BentoBox API 3.19.1+ āļø Minecraft 1.21.5 ā 26.2 āļø Java 21
šŗ Updating ā important notes
šŗ Requires BentoBox 3.19.1 or newer. Update BentoBox before dropping in this jar. The custom block hook functionality this release calls is only available from 3.19.1 ā on an older core the addon will refuse to load rather than fail at runtime.
āļø Custom blocks in templates. generatorTemplate.yml now accepts quoted, provider-prefixed block keys. Unregistered custom blocks import with a warning so templates stay portable across servers ā no config action is required for existing setups.
š” Locale updates. New locale keys were added to en-US.yml for the custom block UI. Update your translated locale files if you maintain custom ones.
š„ How to update
- Stop the server
- Back up your BentoBox folder
- Ensure BentoBox 3.19.1+ is installed
- Drop the new jar into the addons folder and remove the old one
- Start the server
Legend
- š” locale files may need to be regenerated or updated
- āļø config options have been removed, renamed, or added
- šŗ special attention needed
What's Changed
- šŗ Add custom block support via BentoBox hooks (ItemsAdder, CraftEngine, Oraxen, Nexo) by @tastybento in https://github.com/BentoBoxWorld/MagicCobblestoneGenerator/pull/165
Full Changelog: https://github.com/BentoBoxWorld/MagicCobblestoneGenerator/compare/2.9.0...2.10.0
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:NnkaZPqQ:8OzXOF0Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NnkaZPqQ:8OzXOF0Q"
}

