Tags
Creators
Details
0.3.5
Compatibility
Changes
Changes Since Last Changelog
Features Added:
-
Deep-Slate Ore Support:
- Added support for detecting deep-slate variants of ores (e.g.,
DEEPSLATE_DIAMOND_ORE). - Updated the
isDetectedOremethod to handle both standard ores and deep-slate variants.
- Added support for detecting deep-slate variants of ores (e.g.,
-
New Methods:
- Introduced
isOreVariantto identify if a given material is a variant of a detected ore.
- Introduced
-
Enhanced Ore Naming:
- Improved
formatOreNameto handle names for both standard and deep-slate ores, ensuring consistent messaging.
- Improved
-
Improved Vein Detection:
- Modified vein detection logic to include all 26 neighboring blocks, including diagonal directions.
-
Message Sending Optimization:
- Added a
processedBlocksset to track processed blocks within a vein to avoid duplicate messages. - Implemented checks to ensure messages are sent only once per group of connected ores.
- Added a
Bug Fixes:
-
Message Duplication:
- Fixed an issue where multiple messages were sent for subsequent mining actions within the same vein.
-
Ore Detection Consistency:
- Resolved issues with ore detection for blocks replaced in an already found vein.
Other Improvements:
- Performance Enhancements:
- Optimized vein detection and message sending logic for better performance.
Additional Updates
-
Enhanced
/killallCommand:- Added tab completion support and integrated better argument suggestions.
- Ensured the
KillAllCommandclass implementsCommandExecutorandTabCompleterproperly.
-
Deprecated Method Replacements:
- Updated deprecated methods related to player list names and scoreboard team prefixes.
-
Command Registration:
- Fixed command registration issues and ensured proper integration of commands with updated API methods.
-
Configuration Updates:
- Added detailed command descriptions and usage information in the plugin configuration.
Summary of All Updates Since Last Changelog
-
New Features:
- Deep-slate ore support.
- New methods for ore variant detection.
- Enhanced ore naming consistency.
- Improved vein detection logic.
- Optimized message sending.
-
Bug Fixes:
- Fixed issues with duplicate messages and ore detection in veins.
-
Other Improvements:
- Performance optimization and deprecated method updates.
- Enhanced command handling and configuration updates.
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:TrJIjXGg:sIlgproP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TrJIjXGg:sIlgproP"
}

