EzMine

Fixed

• Null pointer exception in vein mining - VeinMineUtil.findVein() now gracefully handles null origin block
• Null pointer exception in area mining - AreaMineUtil.mine3x3() now validates center block and world before use
• Locale-sensitive string comparison - AllowedActions.isAllowed() now uses toLowerCase(Locale.ROOT) for consistent behavior
• Redundant validation - Removed redundant shopCost < 0 check in CustomToolDefinition.validate() (constructor already clamps)
• Inconsistent action matching - CustomToolListener.onItemHeld() now uses case-insensitive action matching consistent with onPlayerInteract()

Added

• Unit tests - Added test coverage for bug fixes in AllowedActions, VeinMineUtil, and CustomToolDefinition

---

Documentation · Modrinth

Breaking changes

• Java 25 required. The minimum supported Java version has been raised from 8 to 25.
• Parent POM removed. EzMine is now fully standalone - the com.skyblockexp:EzTree-parent parent POM dependency has been eliminated. All repositories and build properties are defined directly in pom.xml.
• EzSkills 2.0+ required. The reflection-based EzSkills adapter has been removed. EzMine now depends on the ezskills-api artifact from JitPack and calls EzSkillsAPI directly. Servers running EzSkills 1.x must upgrade to EzSkills 2.0+ before upgrading EzMine.

Added

• Vein miner action - New vein-miner custom tool action. When active, mining any tracked block automatically mines the entire connected vein of the same material in one swing. Uses a BFS flood-fill across the six face-connected neighbours.
  • Configurable via settings.actions.vein-miner: enabled flag and max-blocks (default 64, hard cap 512).
  • Fully compatible with area mining, auto-smelt, ore-searcher, all rank drop/XP multipliers, and WorldGuard region checks.
  • Built-in vein-mining action group and vein-pickaxe example tool added to tools.yml.
  • prison-master combo action group now includes vein-mining by default.
• GitHub Actions CI - build verification on every push and pull request to main.
• Code quality workflow - Checkstyle enforced on every push and pull request.
• Documentation site - new Jekyll/GitHub Pages docs at docs/.
• Docs CI workflow - markdownlint and Javadoc verification on pull requests.
• Publish workflow - automated release to GitHub Packages and Modrinth on version tags.
• checkstyle.xml - Checkstyle configuration aligned with project code style.
• .markdownlint.yml - Markdown lint configuration for all documentation files.
• .gitignore - comprehensive ignore rules for Maven and IDE artifacts.

Changed

• EzSkillsIntegration replaced reflection with direct EzSkillsAPI calls.
• pom.xml updated to version 2.0.0; maven.compiler.release set to 25.
• Spigot API version updated to 1.21.4-R0.1-SNAPSHOT.

---

---

Documentation · Modrinth

Improved configuration validation

When EzMine loads custom-tools it performs sanity checks and reports problems in the server log. Fatal errors (such as a missing or unknown material, or duplicate tool IDs after normalization) will disable custom-tools until you fix them.

Watch for these common messages and how to fix them:

• Missing material for custom tool <id> — add a valid Spigot Material name (e.g. NETHERITE_PICKAXE).
• Unknown material <name> for custom tool <id> — correct the material name or use a supported material.
• Duplicate custom tool id after normalization: <id> — ensure tool keys are unique when lowercased.
• Unknown action '<action>' for custom tool <id> — use a built-in action (e.g. 3x3, auto-smelt, ore-searcher) or define it in the actions section.
• custom-model-data must be zero or positive for custom tool <id> — use a non-negative integer for custom-model-data.
• shop.slot out of range for custom tool <id> — choose a slot between 0 and rows*9 - 1.

If you see warnings (non-fatal issues), EzMine will still load the tool but the behaviour may differ. After fixing the YAML, run /ezmine reload to re-apply the configuration.