Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 years ago
All versions
2.0.4-prelease
Beta
HTGLoggers (Public API) 2.0.4-prelease2 years ago 52
Compatibility
Minecraft: Java Edition
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog for version 2.0.4
Fixed:
-
API Initialization:
- Added additional validation during API initialization.
HTGLoggersAPInow checks if it has already been initialized and throws anIllegalStateExceptionin case of a reinitialization attempt. Instead of a warning logged in the console, improper reinitialization now results in an exception.
- Added additional validation during API initialization.
-
Handling Empty Plugin Names:
- Fixed an issue where empty or null plugin names could be passed to the
createLogFilemethod. The method now validates thepluginNameparameter and logs an error if the name is invalid.
- Fixed an issue where empty or null plugin names could be passed to the
Added:
-
Enhanced Exception Handling:
- Implemented detailed exception handling when creating log files. Any errors related to folder or file creation are now logged at the
SEVERElevel, including the full stack trace.
- Implemented detailed exception handling when creating log files. Any errors related to folder or file creation are now logged at the
-
Expanded Parameter Validation:
- Added validation for the plugin name in the
createLogFilemethod. The method now checks if the plugin name is neither empty nor null before attempting to create a log file.
- Added validation for the plugin name in the
Removed:
- Unnecessary API Reinitialization Warning:
- Removed the logic that warned about API reinitialization and replaced it with an exception. This prevents potential errors in the future.
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:qpx0uAhr:i8G59DoL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qpx0uAhr:i8G59DoL"
}

