2.5.8-ALPHA.4
Compatibility
Changes
v2.5.8
This pull request introduces improvements to the vanish command logic and updates the configuration management system. The most significant changes include refactoring how player visibility is toggled and adding support for a new default configuration file.
Vanish command logic improvements
- Refactored the
hidePlayerandshowPlayermethods into a singlehidePlayer(Player, Boolean)method, which now takes a boolean to determine whether to hide or show the player, simplifying the code and reducing duplication. - Updated the logic in
toggleVanishandsetVanishto use the newhidePlayermethod with an explicit boolean parameter, ensuring clearer intent and consistent behavior.
Configuration management enhancements
- Added a new
defaultGeneralconfiguration (YamlConfig) to theConfigsclass, providing support for a default general configuration file. - Initialized the new
defaultGeneralconfiguration in theConfigsconstructor, loading from#defaults/config.yml.
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:mXLxDDZ3:BDddOkMZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mXLxDDZ3:BDddOkMZ"
}

